Problems with category labels in ArcGIS Dashboards after June 2026 update

[ShaneBradt]

I frequently use category labels in my ArcGIS Dashboards and it seems that the June 2026 update has created a situation where some of those labels are ignored. 

In this dashboard https://epa.maps.arcgis.com/apps/dashboards/ac7397d07f66410bb39890ce8d791512 I have two similar tables (they are single field, single record, so they look like one cell) that are set up in the exact same way as each other, one using the delta field of this data layer (A - https://www.arcgis.com/home/item.html?id=0c0090b13a404d018bd883064bc11ef2#overview) the other uses the Approve for public release? field of this data layer (B - https://www.arcgis.com/home/item.html?id=4c31038c1a00490e807ad59ec79a0ed7#overview).

The recent update caused the discrepancy, since both tables were acting the same up until late last week. I also used to have category selectors in this dashboard (got rid of them due to different dynamics introduced by the new update) and the same exact thing happened to them - the selector based on layer A continued to respect the label I entered, while the selector based on layer B did not.

I'm not sure why one is respected and the other isn't. I tried recreating the table and it didn't see to have any effect. Perhaps there is something I can tweak to fix the problem, but It seems like perhaps I have to wait until there is an update. If that's the case, I definitely need to redesign the dashboard.

Looking for any idea out there about a fix - thanks in advance!

[StephanieW]

Hi @ShaneBradt This could benefit from a case with Esri Support so we can take a closer look at the configuration to isolate the issue. https://support.esri.com/en-us/contact

[ShaneBradt]

Thanks @StephanieW. I may wind up doing that in the end.

However, the issue is not isolated to just this dashboard. Similar things are happening in other dashboards as well (with completely unrelated data). Another dashboard I built years ago (inside a different Org) is experiencing a similar situation.

https://unhcoopext.maps.arcgis.com/apps/dashboards/fa3bd81fb20442c6842483a223df7a2f#

The label text is not being respected, in this case in only one of several bars on a graph. In this case, the custom series color is not being respected as well. Neither of these things were true before the recent update.

So... seems more like a pervasive issue with the new version of ArcGIS Dashboards rather than with something specific to my configuration settings. However, I could still submit a ticket if it would be helpful to communicate the idea to the right people.

[ShaneBradt]

@StephanieW - I was able to figure out the reason that the label text in this dashboard (https://epa.maps.arcgis.com/apps/dashboards/ac7397d07f66410bb39890ce8d791512#) was not working as it should.

When clicking on Load categories (now and before the update), the category label options that populate were/are drawn from the Label (displayed value) of that field in the data layer (Approve for public release? field in https://unhcoopext.maps.arcgis.com/home/item.html?id=4c31038c1a00490e807ad59ec79a0ed7&dataTabView=fi...). However, after the update, the dashboard seems to be referencing the Code (stored value) when determining how to apply the custom text in the category labels, not the Label (displayed value) as it had done previously.

I fixed the issue by using the +Override option to add a new category which reflects the Code (yes) instead of relying on the Label (Yes) that was loaded by the dashboard when I used the Load categories button. The dashboard now appropriately displays the text I want it to in the location it should.

The problem is now fixed in this dashboard (which is great) and I'm now in the process of trying to figure out if a similar approach will fix similar issues in other dashboards.

However, this is still a problem that needs to / should be fixed with the code base of ArcGIS Dashboards. If Load categories presents you with options based on the Label, it should apply the text based on the label. If it needs to use the code value, that is what it should present at the option. 

(Hi @MartinCopping - thought I'd bring this thread to your attention, since others may be having similar issues...)