Hosted Feature Layer views can't be updated after overwriting underlying service w/2 new sublayers | The view could not be updated. Try again.

[SaraSiskavich]

Here is the AGOL service I have recently overwritten using Pro 3.5.3. I added two new layers (6) and (9), which are Road Centerlines and Buildings.

https://nashuarpc.maps.arcgis.com/home/item.html?id=bcb82806d92b4030b6098395ffc7cf63

I have 13 dependent views that I want to update to expose these two layers. Example:

https://nashuarpc.maps.arcgis.com/home/item.html?id=7b51e40b18ff44b8b4d04136cb0c0d21Here is the error when I try to update the view to turn on either layer 6 or 9. I can check on the layer, it draws, but then it won't apply when I press Update, returning the nonspecific error: 

The view layer could not be updated:  Try again.  

I am the admin of the org and owner of these items.

Things I've tried, to no avail: 

1. Renamed the view to remove the dash

2. Checked off visibility of all existing layers in view in favor of just the two new ones

3. Removed all filters on existing layers in view prior to checking on the new sublayers

4. Move the the view out of a folder into the root of my content, alongside the underlying feature service, prior to making edits. 

5.  Placed a ticket with ESRI support.  Technician who picked up the ticket promptly went out of the office, so I wait. 

Am I doomed to recreating my 13 views? I REALLLY don't want to to do that.  

[LindsayRaabe_FPCWA]

Have you considered/tried publishing a copy of the updated feature service, and then changing the data source of the views? 

[SaraSiskavich]

I published up a new feature service with a new item ID, then tried to swap the source.  I got an error that I could not swap the source.  When I try to preview the data, I get "Loading error.  The layer is broken or unavailable."   Now the view seems to be entirely corrupted.

[LindsayRaabe_FPCWA]

Ahhh not good. I've had mixed success with views and either updating them or swapping sources. It seems that the older they are, the less reliable the update process is. Could have something to do with how ArcGIS Online has changed over time, but I've never really got a straight answer from support when trying to troubleshoot. The outcome has almost always been the same - start from scratch. 

[SaraSiskavich]

Thank you for commiserating, if nothing else.  This isn't the first time I've been burned by AOL views, unfortunately.  They just don't seem robust.  I should have just rebuilt all of them and messaged out my audience when this happened a week ago.  Sucks that it's our Open Data portal that's affected.