nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Roll back the June 2026 update?

Scott_Sambell

Serious question. Is there a possibility of rolling back the June 2026 update to dashboards? We need to make a decision soon about how we are going to tackle this. We have hundreds of dashboards deployed to at least 30 clients that need to be repaired. My inbox is full of complaints. I need to put staff onto this full time for the rest of the week at least but i don't want to begin this if there is a possibility it will be rolled back.

Trouver plus de publications taguées avec

Accepted answers

All comments

Nora-Schaak

A rollback would be great... but what has been lost will have to be redesigned, specifically in my scenario. The loss of HTML formatting in no data/selection element settings kneecapped what I had intentionally designed -- rich informational graphics that were clear and pleasant to the viewer. What appeared after the update was plain text versions of that same graphic. In addition, each list element contained glaring information (i) buttons which I reverted to the foreground color via advanced theme configuration.

CarlaSouza

I support a rollback. The June update has broken the survey 123 report generation too. We have a lot of issues with our dashboards and now we have an entire field inspection team complain about the report generation. This issue is having a significant impact on our operations.

dougbrowning

There is a great master list here now.
https://community.esri.com/t5/arcgis-online-questions/arcgis-online-june-2026-update-known-issues/m-p/1711370

GrantHoward1

Yes, I support a rollback as well. And not JUST for dashboards. A complete rollback. I have several issues hitting Field Maps, ExB maps, etc.

And going forward ESRI should not force the AGOL updates. In Pro we have the option to update if we want. Why not take that approach with AGOL?

Helen_Johnson

I support a rollback. The June update has broken selectors, tables, and editing in dashboards - possibly more. I am seriously let down with ESRI that this update made it live with so many critical issues in it.

Neal_t_k

Oh wow, AI is not going to have any clue on these issues.

KClarkDev_GIS

I'm sure there is one, but I highly doubt it's publicly available.

Update: I made my own post here

Side note, I did find it humorous that I received this automated email today, it could just be a coincidence since these type of marketing emails come out all the time, but I suspect they are getting flooded with support cases and really working overtime to correct their mess (as they should...)

Screenshot 2026-06-30 152517.jpg

Scott_Sambell

Does anyone know if there is an authoritative list somewhere will all the dashboard bugs introduced since the update? There are lots of discussions like this one but there must be a place where Esri can see the full extent of the chaos.

Neal_t_k

To add, series all apparently still exist somewhere but are missing from the configuration options, resulting in a broken, incomplete chart. Unacceptable to release an update with these issues, I shouldn't have to rebuild from the ground up!

Edit: Going from what @NicolásPignataro said, I just checked out the JSON for these two dashboards. and the series and filters etc. still exist in JSON but are not displaying correctly in the app.

Neal_t_k

I support a rollback. Loading seems slower but once loaded it seems some improvement on filtering/calculation changes. However that is small in comparison to the broken, inconsistent map filtering I am experiencing. Indicators work on some selections and not on others, And configured filters apparently still exist but are blank.

NicolásPignataro

I ran into the same issue after the update. Fortunately, I found a workaround by editing the dashboard JSON directly instead of changing the selector through the Dashboard editor. Before trying this, I strongly recommend working on a copy of your dashboard rather than your production version. Make a test copy first so you can verify everything works as expected before applying the changes to a live dashboard. For my selector, I changed the selection block from: "selection": { "operator": "equal", "type": "single", "requireDefault": true, "defaultSelection": "last" } to: "selection": { "operator": "is_in", "type": "multiple" } After saving the modified JSON and reopening the dashboard, the selector behaved as a multiple-selection filter without losing any of the existing filter actions. This saved me from having to reconfigure every widget connected to the selector. I only tested this in my own environment, so I can't guarantee it will work in every scenario, but it worked perfectly for my dashboard and saved me a lot of time. Hopefully it helps someone else

dougbrowning

Same tons of stuff broke and performance is terrible. We are in the middle of big projects and we are in trouble.

CMSchelde

I too was affected by the Date Filter Combo change. Does the ArcGIS Dashboard Team offer a Holistic Testing session like the Survey123 Team offers? I now have to change 30+ Dashboards. Just wondering if there was any input from users who actually have Dashboards in Production that this update affected.

LindsayRaabe_FPCWA

I recommend reaching out to Esri Support regarding this issue ASAP. Sounds serious enough to warrant close up inspection.

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.