I have a group filter on a region layer (and related layers). I defined the action trigger to zoom the map to the region layer with automatic zoom scale. However when I apply the filter, the map zooms the region to the top left of the screen, and the region is still small.
Using the map layers widget, I can zoom the layer successfully to the filtered region.
Any help?
@SandraCHayden Emm, that is interesting. Not sure if that's related to specific data. Do you have a sample app for us to take a look at?
Unfortunately, these are internal organization layers that I can't share.
I noticed that the zoom fails when I include a certain layer (DAT) in the group filter (first screenshot).
It is odd because the DAT layer is not in the zoom action trigger (second screenshot). So why does it make the zoom fail?
Hi @SandraCHayden,
Could you provide the steps to create a DAT layer? Is it Data layer? https://segment.com/blog/what-is-a-data-layer/
Thanks,
Ke
I am also having this same issue with 2 group filters (which is another issue - group filter widget not honoring the AND). The zoom to works in the regular filter??? The EB I'm working with is also not public but I could post screenshots.
A general comment regarding the filter widget is a really hard time formatting between single and multiple filter widgets vertically. I feel like we don't have much control and how it looks isn't appealing to the eye. Hopefully I'm missing something to that end, but probably a new post.
Hi!,
Just following up on something I learned regarding the Group Filter and Zoom after submitting a tech support case for a number of issues.
In the EB we have the Group Filter does not zoom on the map to the filtered data despite the configured actions WHEN there the group data layers includes a table??? Yup when we removed the table from the Group Filter data layers, the zoom and pan worked. It was a great observation from the tech support because there is another Group Filter included in the EB but there wasn't a table data source included in those layers. I'm not sure if a table could be causing your issue or not, but wanted to add our 'experience'.
Thanks,
Kathy