Best practice for updating the schema of a Hosted Feature Layer without breaking Experience Builder connections

Question

We have a File Geodatabase created with ArcPy that is published to ArcGIS Online as a Hosted Feature Layer and used as a data source in ArcGIS Experience Builder.

Over time, the data model needs to evolve, for example by adding new feature classes, tables, fields, domains or relationships, while preserving the existing data.

Our main concern is that publishing a new Hosted Feature Layer or changing layer/table IDs can break existing data source connections and widget configurations in Experience Builder.

What is the recommended workflow to update or extend the schema of an existing Hosted Feature Layer while keeping Experience Builder connections intact?

Should this be handled through ArcPy, overwriting the service, or another approach?

Laura · Answer

I overwrite. As long as your layer IDs match was is already published it will be fine. In the newer version of ArcPro there is a compare button when overwriting that will compare the IDs for you. If you are updating the schema you might still have to reconnect or re add the layer in your maps to get that new field to show up say in the EXB editor widget.

JakeSkinner · Answer

Hi @trigo-amp, I would recommend overwriting the feature service if there are multiple layers within your service.  Here is an example script: https://community.esri.com/t5/arcgis-online-documents/overwrite-arcgis-online-feature-service-using/ta-p/1371248

If it's just on layer, you could also perform a truncate/append.  The following script will also accommodate for schema changes:  https://community.esri.com/t5/arcgis-online-documents/overwrite-arcgis-online-feature-service-using/ta-p/904457