I have a dashboard that contains one large-ish polygon feature class (20,000 records). I have a filter for year and another filter for another element.
The filters have an action on the features so they reduce the number the map has to display. No matter how few features there are, the map always refuses to show all features at the full extent. It is acting as if there is a series of scale dependencies or too many features to display, neither of which is the case.
It gets a bit weirder. If I filter the features in the web map that feeds the dashboard for a particular year, ALL FEATURES FOR THAT YEAR WILL DISPLAY AT FULL EXTENT IN THE DASHBOARD (pardon the all caps).
If I do not filter in the web map, but apply a filter in the dashboard, only a subset of features displays at full extent, with more features appearing as you zoom in.
I have set maximum number of records to return on the service at 100,000.
This appears to be a bug.
Has anyone experienced this? I would very much appreciate some advice as we are currently stuck.