Workflow for adding feature classes, editing fields, domains etc. of hosted layers?

[JDenham]

I'm working on a web map and ExB application for our department for recording asset locations across our many campus buildings.  We're using Enterprise 11.3 and collecting data with the Field Maps mobile app in conjunction with our indoors buildings layers.  As the field techs are collecting data, they are adding photos within the app as they go.  I also have an ExB web application where they can edit and reference the collected data from their workstations.  This is a 'working' web layer/web map for the techs.  They collect the data they need, and plan to use it as a time saving reference while servicing these assets in the future. 

As they have begun asset collection, they are realizing that their original list of asset types is incomplete, assets that I have separated in the data as different point feature classes.  I understand that there is not an easy way to add feature classes directly to web layers, so I need a workflow for pulling the web data back into a GDB in ArcGIS Pro, editing features/schema, and then safely overwriting the web layer with the changes.

The workflow that I'm currently testing is to download the FGDB from the portal and save it locally.  Open ArcGIS Pro and run the Feature Class to Geodatabase tool to populate the local project GDB from this downloaded FGDB.  This brings in all of the domains, attached photos, and their relationship classes.  I add them all to my project map, including the "...ATTACH" tables.  I can view the attribute data and photos in Pro, and all looks good.  I then edit to my heart's content, adding the needed feature classes and configuring domains and schema.

Testing the above, while analyzing before publishing (overwriting), I'm getting Error "24171: User assigned unique related ID's will not be honored" The error states that this is because I'm trying to share a web feature layer that copies all data.  Since this is actively used data, and this process is new to me, I'm a bit hesitant to let it fly.  I've aligned the feature class's unique numerical IDs to the hosted feature classes, but with the photos effectively all sharing the same name (photo 1.jpg), the stakes are high if something goes wrong.

Is there a better, more efficient way to carry out this type of "structural" edits to hosted data?  Our techs will likely bring future changes as well, and I need to find the most trustworthy and efficient workflow that both retains all of our most up to date data and allows the seamless continuation of collection (with attachments) for both existing and new features after re-publishing.  It would be even better if this can be done without having to do extensive downstream work (Field Maps and ExB).  I know there will be some work to adjust popups and forms etc., but I'd love to avoid re-configuring everything each time this is required.

Any help you folks can provide would be appreciated.  I'm far from a power user, so I may need fairly simplified instructions.  I can find my way around the portal and ArcGIS Pro basics, but JSON editing or Python use is likely going to be lost on me.  Thank you for your time.

-Jeremy

[MaximilienRIOT]

You can access your portal data from ArcGIS Pro directly from the catalog window. Then you can use the GP feature class to geodatabase without having to download your geodatabase as fgdb. Alternatively, you can directly modify the domains of your feature layer from ArcGIS Entreprise, by selecting your data and clicking on the data tab, then on the fields view, where you can edit the domains linked to your fields. Hope this helps.
Max

[JDenham]

You are right that I could save a step in pulling the data without downloading it first.  I'll most likely still download the FGDB nonetheless, purely as a data backup in case something goes wrong in overwriting the original web layer.  I've been down the path of lost data before and tend to want additional copies to fall back on if possible.  🙂 

My main question is one of best practice with regard to carrying out the replacement of a web layer (with attachments) after structural changes have been made.  In software like this where there may be 3-4 ways of doing something with varying levels of efficiency, it would be helpful to have an officially validated (trustworthy) step by step guide that avoids any pitfalls that a user may run into.

-Jeremy

[MaximilienRIOT]

Ok I understand better, in fact for me the simplest thing would be to publish your data as a web service with an sde base. You have access to your web services on arcgis server manager. Then, if you want to update your data, simply deactivate your service, modify your data in your sde base and reactivate your service in ArcGIS Server Manager and everything will be up to date. For data backups, you can always make copies of your sde database or export your sde feature layers to a backup gdb, for example.
Hope this helps 🙂
Max