Experience Builder Query Widget - all layers option on spatial filter

[JohnFannon]

The Experience Builder Query Widget currently allows for specifying a spatial filter using "Selected features from Data Source", which then requires pre-defined layers to be selected for the filter. This has to be done for each query configured and can be very painful where there are multiple layers in the map.

An obvious solution to this would be to have an "All layers in map" option (preferably default), which would allow all layers from the specified map to be used in the spatial filter, rather than specifying the specific layers to use (see images).

This would be very similar to how the Web App Builder Query Widget works, which does not require the specific layers to be selected for use in the spatial filter and therefore allows all suitable layers in the map to be used.

[Tiff]

Hi @CameronLacelle, unfortunately no! It seemed like a strange issue/bug with the choices not showing up, and so the functionality wasn't totally there to be used by staff. So that app has not been widely shared or worked on in a while. Definitely hoping to revisit it with some new features that have come out for ExB but this is a strange one!

[CameronLacelle]

@Tiff that's too bad. I've put this in Experience Builder Questions and thinking about putting a ticket in with Esri as well. This is super problematic if our team wants to build an app our end users can rely on. I've found that in the ExB map, if you click on a feature to display the pop-up (any feature) then go to the Spatial Filter Query widget, all the options will display properly. Just don't quite understand the cause of this in the first place. Thanks for your reply anyhow.

[JesseCloutier]

Hi @Tiff, @CameronLacelle, and @JohnFannon, we appreciate you sharing a potential bug with the broader Esri Community; however, Esri does not actively track software defects posted here. The official channel for investigating and validating bugs is Esri Technical Support. All customers experiencing a potential software bug should leverage technical support to report and investigate the issue.

By reporting bugs through technical support, Esri can better track the scope and impact of the issue across all our customers and better prioritize it with our product teams. Our teams can also investigate the issue more thoroughly to see if there is a solution, workaround, or patch to get you back up and running as soon as possible.

As a reminder, Esri Community is primarily a self-service support platform where Esri users can ask or answer each other’s questions, share feature requests, and collaborate to solve problems with GIS.

*Note that this is a scripted message prompted when posts allude to a potential product bug.

[JohnFannon]

@JesseCloutier- Note the original post is not a bug, but an idea/enhancement request.

[JesseCloutier]

Much appreciation for pointing that out, @JohnFannon!