topic GenerateID Table in GeoData Service Editing Environment in Addressing Questions

GenerateID Table in GeoData Service Editing Environment

JasonBalmut — Mon, 23 Jul 2018 19:31:54 GMT

Mike,

The setup: Two organizations want to edit replicas of the same address data through a #GeoData Service. Their edits occur locally throughout the day in versioned feature classes, they both run scripts to reconcile and post edits to their Default versions in the evening, and the deltas are synched through the replicas by the next morning. Both organizations use the #Attribute Assistant including the #GenerateID table.

Question: Does the GenerateID table have to be part of the replica? If so, how are duplicate IDs avoided since each set of editors is seeing the same numbers in a synched up replica? If it does not have to be part of the replica, should one of the organizations set their GenerateID table to have higher values to avoid future duplicates?

Re: GenerateID Table in GeoData Service Editing Environment

JoeBorgione — Mon, 23 Jul 2018 21:04:29 GMT

Right from the Online help : Increments a row in an unversioned table and stores that newly incremented value.

What is your workflow? Where does the 'parent' live? Is one organization maintaining the parent while the other replicates from it? When your replicate data, the GUID is tied to the parent eGDB and Child gdb.

Re: GenerateID Table in GeoData Service Editing Environment

JasonBalmut — Tue, 24 Jul 2018 11:46:24 GMT

Joe Borgione, thanks for the help. Organization 1 will house the parent and Organization 2 will replicate from it. We will increase the GenerateID numbers on one side to so that duplication does not occur.

Re: GenerateID Table in GeoData Service Editing Environment

MikeMillerGIS — Tue, 24 Jul 2018 16:03:51 GMT

I think that is the best option.