Non-editable replicas

Question

I notice that while I can add un-editable layers into a FieldMaps map for offline use, when a user takes that map offline and creates a replica on the un-editable layer, the replica has the same drawbacks as replicas on editable datasets -- they ruin the ability to update the hosted layer while the replica persists.

For un-editable datasets when an append-type workflow is not feasible, why must a replica break the ability to update the layer? It's not like the user replica is going to feed back changes to the layer.

Is there a way that this can be modified or fixed? Anyone know of a workaround that doesn't involve changing the standard update workflow to the un-editable layer when there is a replica taken out on it?

For context: The un-editable layers that need to be updated are done so multiple times a week, and contain hundreds of thousands of records pushing into a million plus. The un-editable layers are used in offline maps with other editable layers. I have over a hundred users spread across Australia and North America at a dozen different sites, working in multiple time zones.

Anonymous User · Answer

Have a read of this threadHow to update sync data on ArcGIS Online as others are grappling with the same issue. Unfortunately there are no easy options.

SandraDalton · Answer

Hi rzufelt,

I appreciate your suggestion. For smaller layers that are not editable, the append process is sufficient to update layers while there are replicas out and it is not an issue. The datasets I am running into an issue with are large to the point that trying to append as the update mechanism is too slow to be feasible (the processing time is longer than the update periodicity -- for example it would take 3 days to append updates, but I need to update the layer every 2 days).

I like the idea of moving the data into a basemap, but having to then regenerate the basemaps and sideload them on all company devices at the layer update schedule is untenable.

SandraDalton · Answer

Hi Doug,

Thanks for that, yes I am aware of the ability to unregister replicas. Unfortunately it is not an option in this scenario as it will break the sync back process when users are trying to push their edits to the editable layers on the same offline map back up to AGOL.