filter action configured with query widget output data is not working

[KaraUtter2]

Hello, a bug was introduced with the last experience builder update. A data action called "Select Loaded" was introduced in the Data Action menu. This has caused an error to occur when configuring a Message Action with the query widget to Filter the map based on the query results (e.g. Output Data). The end user must now use a non-intuitive method of filtering the map view by the results of the query and this was not necessary prior to the last update. The beauty of configuring Message Actions is that you are automatically applying actions for your end user, so they don't have to. Can we fix this issue? Please see below screenshots.

TRIGGER/ACTION CONFIGURATION WITH OUTPUT DATA:

RESULTS FROM QUERY THAT SHOULD FILTER THE MAP BASED ON THE QUERY RESULTS, BUT IS NOT:

CLICKING ON DATA ACTIONS TO 'SELECT LOADED':

ONCE THE LOADED QUERY RESULTS ARE SELECTED, THE MAP FILTERS:

[TianWen]

Thanks for the post! The message you configured is 'record selection changes,' which means the filter action is only triggered when the selection changes. Based on this setup, the behavior you're seeing is expected.

[SteveMarkovick]

The "Select Loaded" action feels like a step backward in terms of user experience, especially for applications where the goal is to automate interactions as much as possible. It used to be so smooth having the map filter instantly from query results, and now having to rely on a manual selection step breaks that flow. Really hope Esri addresses this soon, or at least provides a clearer workaround.