Data tab of Item Details not updating properly after June 2025 release

HollyTorpey_LSA

I don't have time to submit a help request to get this logged as a bug right now, but just want to document that the data tab of the Item Details page for feature services that include multiple layers is not reloading after adding a field.

In other words, if I open the Item Details page for a hosted feature service that has multiple layers, and I select one of the layers and then click the Fields option on the left and add a new field, the page doesn't reload properly after the new field is added. I can no longer select a layer and no fields are displayed. Clicking the Table option on the left also doesn't display anything. In fact, the only way to get the data to display again is to reload the browser tab. This is annoying and inefficient when I need to add several fields to the same layer. I have experienced this with two separate feature services since the June 2025 release.

Before adding a field: 

 

After adding a field:

Also, the data tab in general is very slow to load.

If anyone has figured out how to get around this besides reloading the tab, please share.

 

RTPL_AU

@HollyTorpey_LSA 
A quick check I use is to log in using a InPrivate window. Repeat the process and observe.
If you have another PC, preferably with another version of Windows or a Mac, do the same.

In the utmost minority of cases I have found an improvement; so could then troubleshoot my main session (clear out the cobwebs, etc.)

In this day & age it is entirely possible for developers to manage their session resources if you use a known good browser (Chrome no longer in that boat IMO).
The typical 'reboot, clear cookies, clear........' might work but some issues like the dramatic drop in performance when you start adding a few external web services to New Map Viewer is an Esri thing, not an Netscape cookie thing.

I had a quick look at some of my data with multiple layers per service and overall performance was not very good when swapping between layers.
Most datasets only had a few records (4 to ~60) so can imagine it getting much worse with a decent dataset.
No fields added as the data is being used in the bush at the moment 🙂

The vibe I get is that the team working on the Pro Attribute Table may have been involved here.

 

Wait - you're adding fields to a multi layer feature service? Bet you wished you published them individually so you can just manage them separately 🙂
The schema was signed off by every stakeholder and it was faster to just grab a bunch and share in one go when under the pump? 
Been there a few times. With my luck it will be an email two days later while people are offline in the bush and one goes 'Can you add a field to record a list of weeds; that we can select from a list; and also select multiple entries in one field'..........