topic Re: Minimum enterprise geodatabase table config for sync to support distributed collaboration in ArcGIS Enterprise Questions

Minimum enterprise geodatabase table config for sync to support distributed collaboration

Jay_Gregory — Thu, 13 Jul 2023 14:26:50 GMT

We currently have a collaboration setup between Enterprise and AGOL, to support replicating enterprise data to our AGOL users. That is currently the only requirement - no disconnected or multi user editing needed. Just copying our data to AGOL easily.

To enable sync for a feature service, my understanding is I had to enable Global IDs on table, as well as versioning (I use traditional versioning, create a replica for each map). Then I can publish the service with sync enabled, and share the feature layer to the collaboration group and voila.

However, now I cannot use the TruncateTable operation on my table, which breaks a lot of my ETL functionality.

Is there a different way to do this, or do I have to change TruncateTable to the much slower DeleteRows in order to keep my sync capability?

Re: Minimum enterprise geodatabase table config for sync to support distributed collaboration

MarceloMarques — Fri, 14 Jul 2023 16:39:13 GMT

Truncate Table (Data Management)—ArcGIS Pro | Documentation

Versioned data is not supported as input. Data must be unregistered as versioned before the tool will run successfully.

These other links might also help.
Configure a map service—ArcGIS Pro | Documentation
Prepare data for use in offline feature services—ArcGIS Pro | Documentation
Enable layers for offline mapping—Portal for ArcGIS | Documentation for ArcGIS Enterprise

Support Services: Feature Service Sync | Esri Training Web Course

Support Services: Perform a Feature Service Sync Manually Via the REST Endpoint | Esri Training Document

Support Services: Deploying and Using ArcGIS Enterprise Services | Esri Training Web Course

Re: Minimum enterprise geodatabase table config for sync to support distributed collaboration

A_Wyn_Jones — Mon, 17 Jul 2023 14:41:18 GMT

Considering you don't need multi-user editing, I'd suggest unregistering as versioned and enabling archiving. This is described in the following scenario on the ArcGIS Pro documentation:

https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/prepare-feature-layer-data-for-offline.htm#:~:text=Versioning%20is%20not%20required