Query widget to select data from feature layer instead of creating new layer

[lmurrayADOT]

The query widget in Experience Builder creates a temporary feature layer with the results of the query.  It would be helpful if the widget selected the records directly from the feature layer itself.

Currently, I have to explain to my end-users why there are two tables in the table widget, one showing all of the records for a feature layer and the other showing only the query results.  It would be much easier for them if the two were combined.  It would also potentially allow additional actions to be set in Experience Builder, such as selecting records from other feature layers that have a common field with the query layer.

[TianWen]

Thanks for the post! Query is one of those widgets that can generate data instead of only consume data.

In the scenario you described above, you can try to use Filter widget to work on the same data using different widgets.

[lmurrayADOT]

@TianWen Thank you for the response.  You're right, for what I described, your solution works.  I'm sorry but I neglected to mention for this app, the user needs to be able to select features based on a drawing, which the Query widget allows but the Filter widget doesn't.  Plus, my customers would prefer to still view surrounding features that weren't selected in case they want to expand their Query.