Setting up layer for offline sync whose data gets truncated daily from another database

Question

I currently have a non-editable polygon layer whose data runs a nightly SQL script, pulling data from our CAMA system onto our enterprise database connection. The current workflow is to run a nightly job that TRUNCATE the table and then INSERTs the data from CAMA into our database.

However, I am hoping to add the capability to take the data offline on field maps. When taking the layer offline, on the database , new fields are added to the table:

* GDB_ARCHIVE_OID
* GlobalID
* GDB_FROM_DATE
* GDB_TO_DATE
* GDB_ROW_CREATE_REPLICA_GUID
* GDB_ROW_EXPIRE_REPLICA_GUID

With this, the current SQL Script syncing with our CAMA system becomes detrimental to maintaining offline capability on field maps. Because I am unsure how the offline data collection process works on the database side of things. I am wondering what would be best practice on how to approach creating a new SQL Script.

jcarlson · Answer

It's a method on the GeoAccessor, Esri's version of a spatial dataframe.

https://developers.arcgis.com/python/api-reference/arcgis.features.toc.html#geoaccessor

You can also use pandas.DataFrame.compare() to compare two dataframes, but it operates differently.

KL_MSB · Answer

Could I get some further detail as to what the "Compare Function" is? A geoprocessing tool, SQL statement or a python function?

jcarlson · Answer

Given that it would edit your features in place, it would work quite well. Some of our layers we update this way are used in an offline capacity, and there is no issue. When the source data has adds or deletes, those are made, everything else is simply edited in place or left alone, so any internal fields used to link features to the offline copy would still be in place.