Existing Feature Service (Layer) Does Not Have GlobalID So Cannot Create New S123 (also versioned so cannot sync)

Teresa-AZ

Problem:  Unable to create a new S123 that is created from an existing Feature Service and this error: "supportsApplyEditsWithGlobalID must be true"

Facts: 

- Feature Service/Layer does NOT have a GlobalID and is versioned (probably Traditional) and therefore unable to simply "Enable sync" in Feature Layer/Settings.  (Receive a 500 error)

- All suggests in this Esri Community (and such) have mentioned three (3) options if Unable to Sync and Versioned.  1) Unversion the Data (probably not viable), 2) Move to Branch versioning (this is why I think it is Traditional Versioning, even though Branch is recommended for ArcGIS Enterprise; and need a GlobalID, ugg, then publish, then sync) and 3) a Manual 'Force' (with GP Tools that will add a GlobalID, then index, then overwrite) --- OR move back to S123 v.2.9 (from 2018 so nope)  OR create a non-versioned view (copy of data) and have a nightly Python script to sync the changes so nope)

Does anyone have a suggestion or solution or anything really at this point?

 

Thanks in advance,

Teresa

ryanuthoff

Also, I missed the part about the versioned data. Versioned (traditional) data is also not supported (unless you use S123 Classic v2.9). Your data will need to be un-versioned in order to enable supportsApplyEditsWithGlobalID.

From the blog post, it must meet these requirements:

So just adding GlobalIDs won't be enough. You'll also need to un-version it, but be very careful about doing that. Un-versioning can potentially result in data loss if you don't fully compress the DB first, not to mention any dependencies on versioned data that might break. I'm not sure if it will work with branch versioning or not.