Using Exp. Build. Dev. Ed 1.17. Created queryWidget1 on dataLayer1 in webMap1 of mapWidget1. In SQL Expression Builder, set "Select source type" set to "Unique" to list all unique values of streets. Spatial filter is disabled.
At full map extent, all street names are listed in queryWidget1. When I zoom in, the list of streets gets filtered to the map extent. I don't want this. I need it to list all street names at all times regardless of map extent.
Here's what I've tried (hope you can follow along):
- Created queryWidget2 and duplicated all the same settings found in queryWidget1 (dataLayer1 in webMap1 in mapWidget1) and got the same problem.
- Added dataLayer1 into mapWidget1 as a separate layer (not part of webMap1), created queryWidget3 and it works fine.
- Created mapWidget2, added webMap1 to mapWidget2, created queryWidget4 using dataLayer1 in mapWidget2 and it works fine
- Created new app. Added new map widget and added webMap1, added new query widget with all the same settings in queryWidget1 and it works fine.
What can we deduce from this (other than I'm hosed)? It's not the data layer. It's not the web map. It's not a bug in the query widget or map widget or app 1.17. It's just this combination of factors that is causing the queryWidget1 to filter street names when the map extent changes. It's as if there is a setting that is stuck somewhere in the deepest recesses of the Experience Builder that is forcing my attribute field to be filtered based on map extent.
Any and all suggestions are welcome.
