I have a dashboard containing a number of layers. Most of them are responding fine to actions configured in category selectors in the sidebar. There is one layer however, which has stopped responding. Selecting the category now has no effect on the layer when previously it would apply a filter.
The layer still visually displays without issue, and also correctly feeds into an Indicator (which updates with spatial selection). I have tried creating a new copy of the layer, which I uploaded to AGOL, however this layer suffers from the same behaviour when referenced in the same dashboard. Both this 'new' layer, and the old one, have a blue flashing dot next to them in the Layers controller suggesting they are still loading, however this flashes continually even when all features are displaying. Is this 'hanging' behaviour responsible for the issue? How can I fix it?
When I create a fresh dashboard, the layers respond and filter correctly - however using 'Save As' to create a new instance of the existing dashboard does not fix the issue.
Filter not acting on the map (left) and blue loading dots (right)
Solved! Go to Solution.
Think I've figured this out and have recreated it with layers in the Living Atlas, so I believe it's a bug.
It seems that if you have a point layer in your map which is not set to be visible in the inital load and you have clustering on, then the category filter doesn't work in the Dashboard when you switch the layer on.
The visibility can be either from the initial zoom being outside the visibility range or the layer being toggled to not visible.
Turning the clustering off or making the layer visible in the initial dashboard load both provide a workaround to the problem, but don't allow for quite the same functionality (as I'd quite like to have both clustering and the layer off in this case).
You mention spatial selection in you description, If you have map actions and category selectors on the same layer, sometimes they interact in unexpected ways. Try turning the map actions off and see if the selectors work as expected. Then turn the map actions back on one by one and see where it breaks. I have found sometimes you have to weigh which action is going to be more functional for end users and go with that instead of trying to implement both.
Thanks for the reply Neal - yes definitely some unexpected interactions seem to pop up with these. In this case I managed to figure out the problem and think it's a general bug so will be reporting. Will post workaround below.
Think I've figured this out and have recreated it with layers in the Living Atlas, so I believe it's a bug.
It seems that if you have a point layer in your map which is not set to be visible in the inital load and you have clustering on, then the category filter doesn't work in the Dashboard when you switch the layer on.
The visibility can be either from the initial zoom being outside the visibility range or the layer being toggled to not visible.
Turning the clustering off or making the layer visible in the initial dashboard load both provide a workaround to the problem, but don't allow for quite the same functionality (as I'd quite like to have both clustering and the layer off in this case).