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; } } }

Corrupted View layers after an update to the parent layer

JoshNock1

I have noticed recently that when I make an update to a layer on ArcPro and overwrite the layer onto AGOL all linked View layers return with data errors.
I have tried using ArcGIS Online Assistant to copy over the JSON but the error still persists. Creating a new View layer works but it is not sustainable to keep on replacing layers in maps.

Has anyone else experienced this issue? and managed to find a solution or workaround?

Many thanks

Find more posts tagged with

Accepted answers

All comments

TiffMaps

Hi Josh, I have often had issues with overwriting layers so your comment is helpful to see. Do you have any suggestions on how to approach domain changes? You can create the domain in AGOL, but longer lists can be particularly challenging, and sorting is not supported in AGOL and can be buggy in Pro.

AndyWells

I was reading this post with interest. I have recurring need to overwrite a large parcel layer on a weekly basis. This layer has 30,000+ records, and is published from a local FGDB with a join to a database. So my usual workflow is to make edits to the local FGDB layer, with the join retrieving new attribute data. I export this to a combined local feature layer (polygons + joined attributes). When I am ready, I overwrite the online feature layer. I have tried to drop and add all the records in the online feature layer, to keep from overwriting, but it is extremely slow and not feasible. Is there another method I should be looking at? Like you, I hate overwriting services, but I can't see how to work around it.

HeatherBell

Hi @JoshNock1 , I have been experiencing issues after adding a new field to the hosted feature layer. It is unpredicatble whether the new field will be included in the hosted view layer. For this example, I do need to go into the visualisation settings to make sure that the new field is visible. However, the new field isn't always carried across to the view layer at all. This means that I have to recreate view layers every time I make a change like this to the hosted feature layer.

Best wishes,

Heather.

jcarlson

Can you clarify what you mean by that, though? Updating your data and completely overwriting a service are very different operations, and usually folks only need the former.

We were seeing this happen even a couple years ago, and the update process was able to execute without issue a number of times before "going bad".

JoshNock1

Thanks Josh. A lot of the time it is updating data that changes daily, weekly or monthly. So unfortunately it has to be updated.

Is this something that you have noticed recently?
We have had months of being able to update layers, but only recently we have experienced issues

jcarlson

We've seen this plenty of times ourselves, and it was issues like this that caused us to stop overwriting layers unless absolutely necessary. Our rule of thumb is that unless you're changing the number/order of the layers in the service or altering relationship classes, you ought to avoid overwrites.

Why do you need to overwrite your layer? Making simple schema changes or overwriting the features in a layer can be done without republishing the service itself. For the former, make any changes to your fields from AGOL itself. For the latter, you can use the truncate and append GP tools, or the Python API.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

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