We have deployed the Lead Service Line Inventory ArcGIS Solution v3.0. I've run into limitations using the workflow our consultant had recommended for batch updates to the ServiceLine hosted feature layer.
Our current workflow involves using the Download Map feature of ArcPro to download a local copy of ServiceLine_editing view and making updates to the data in ArcPro. There are 130,000+ features in the hosted feature layer and our edits can resulting in tens of thousands of changes to attribute data. The sync back to AGO is time-consuming and inconsistent to complete without failure, which creates a real problem for us as far as data management goes.
I'm weighing modifying our workflow to replace the Download Maps method with export to FGDB from the ServiceLine hosted feature layer, making the edits to the feature class, publishing the feature class and switching the source on all of the views in AGO to the new updated copy. I've done source switching before for smaller datasets, but never from an export, and never one with attachments enabled.
Has anyone else done this before? Currently, our data does not have any attachments. Can I disable attachments to ServiceLines before exporting, then enable them on the updated copy after it's published and expect the views to accept this as the same schema after the source switch? Or should I be able to export to FGDB and then publish the new version with the unaltered related attachment table without any problem? I'm going to test it out on my end, but I thought I'd ask to see if anybody else has work through this issue already.
