I have a gauge widget that behaves different from other widgets on the same dataset.
The Gauge should display a value.
I have a SOI that will only serve a portion of the data.
If user A opens the dashboard, the feature service will only contain rows 1-20 for user A, if user B opens the Dashboard, the feature service will only contain rows 21-40.
The gauge should only display the first value in the list for user A or user B.
The sort order is ascending and there is a filter to only display one feature.
I noticed that the Gauge widget is behaving differently from the other widgets.
In some cases, user B will not see anything in the Gauge, the widget is not rendered.
If I configure an Indicator instead on the same data and using the same logic, it shows the correct value.
If I remove the limit, to only show one feature (or increase the number), the Gauge is shown again.
I assume there is some kind of bug in the widget, but it is hard to grasp.
It may have something to do with response caching? Or the widget filtering requests?
The gauge seems to handle data a little bit differently than similar other widgets.
It is the only widget where this kind of issue occurs, so I am relatively sure it is not an issue of my SOI.
I found this post with a somewhat similar(?) topic here: Gauge Widget (and Text Widget) is not honoring dat... - Esri Community.
@Ke_Xu any ideas?
