Switch Source method for updating Lead Service Line Inventory: Pros/Cons

[TylerKiehle1]

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.

[TylerKiehle1]

UPDATE:

So, I tested the switch source method and had mixed results.

I updated the ServiceLine_editing view source with one that I published from ArcPro to our ArcGIS Online org.  The data source of the new source for the view was an export to file gdb from the original ServiceLine hosted feature layer.  The file gdb included the relation tables and everything.  I opened a new project in ArcPro and copied all the fc and tables from the downloaded file gdb to the default project gdb in the ArcPro project.  I didn't make any changes to the data itself.  Then, I created a new map with a new name, ServiceLine_SWAP_test, imported the symbology from the ServiceLine hosted feature layer, removed the base layers, save the changes to the project and published to a web layer.  Then the new hosted feature layer with attachments was given all the same settings as on AGOL as the ServiceLine hosted feature layer.

I reduced as many variables as possible.

Then I switched the ServiceLine_editing view source from ServiceLine to ServiceLine_SWAP_test.  The source switch claimed to be a success, but then when I opened the Lead Service Line Editor to see if the web app broke, sure enough the web app showed basic points, instead of the previous symbology for the different material types.  

Since the test failed, I thought surely I can switch the ServiceLine_editing view source back to ServiceLine and everything will work again as before.  Wrong.  The view switched sources successfully according to AGOL, but when I opened the Editor web app again, the material types appeared in the editing template, but the symbology was not completely restored.  Keep in mind, I only viewed the Editor web app after the test source switch, I did not open it in edit mode or save any configuration changes, so it should have been unaltered when I switched the source back to the ServiceLine hosted feature layer.

Needless to say, I'm not confident in the source switch method to update the ServiceLine_viewing view, since we have a public web app that utilizes this view.

I guess my next step will have to reach out to Esri Support to find out why the source switch method caused issues with the Editor web app.

[TylerKiehle1]

Update:

The problem I'm having appears to trace back to the failure of the complex symbology for the ServiceLine feature layer in the LSLI solution to come through to the new hosted feature layer I publish from ArcPro.  Even though I import the symbology directly from the original ServiceLine hosted feature layer in AGOL and everything in the symbology pane looks to be the same, the JSON in the new published hosted feature layer is basic.  Oddly enough, all the editing templates come through in the JSON, only the "drawingInfo" fails to come through.  I tired to update the JSON definition by copying the "drawingInfo" from the original ServiceLine JSON to the new hosted feature layer, but it failed to accept the updates.  I'm new to the REST admin tools, so I can't really troubleshoot that aspect of it.

Hopefully, somebody who's already been down this road comes across this post and can give me some ideas.  I'm looking at you, LSLI Solution developers.