Attribute Assistant and Versioning

5232
12
05-21-2012 06:00 AM
deleted-user-sxViYNIAAUFF
New Contributor
Is there an issue with the attribute assistant and versioning?
It appears that the attribuite assistant only works when I do not edit a version.
I must be directly editing the SDE tables.
0 Kudos
12 Replies
MikeMillerGIS
Esri Frequent Contributor
The Attribute Assistant does work in a versioning environment.  The only layer/table that cannot be versioned is the GenerateID table.  What errors are you experiencing?  What is not working?  Have you enabled the debug log file and review it for configuration issues?  Have you logged a tech support call?
0 Kudos
deleted-user-sxViYNIAAUFF
New Contributor
How does the Generateid table get updated if it is not versioned?  I am editing a versioned database, but the generateid table is not part of the versioned database.

ERROR: GENERATE_ID: Objects in this class cannot be updated outside an edit session [sde.SDE.GenerateId]
0 Kudos
MikeMillerGIS
Esri Frequent Contributor
Rodney,
   Internally, the code is making an unversioned edit.  If the table is versioned, you will get duplicate IDs.
0 Kudos
JustinStangl
New Contributor II
Mike,
We have our Attribute Assistant Add-in functioning properly within our MXD (Dynamic.gdb).  However, in our versioned environment workflow, the Autonumber / Generate ID functions will end up posting duplicate ID's to our SDE feature class tables.  Multiple editors throughout our version tree will create new featues in their versions (from the same feature class in different areas of the map document).  When i reconcile and post these versions, the ID's created from 'editor A' are the exact same as the ID's created from 'editor B' for that particular feature, as they are are set to auto-number based on the last number in sequence. 

We like the attribute assistant, but the ID fields are linked to our mobile software and we cannot have duplicate ID's.
Is there a way to set the starting points for each editors Dynamic.gdb (10000, 20000, 30000, and so on) so each editor will have enough unique ID's ???

Thanks,
-JS
0 Kudos
MikeMillerGIS
Esri Frequent Contributor
You need to not version the Generate ID table.  If the table is versioned you will get dup ids.
0 Kudos
TiffanyPuett
Occasional Contributor II

Can you elaborate a little more on this? I get that the GenID table should not be versioned. However, in a versioned environment, how does this avoid dup ID's? Should all users editing featureclass be working in the same version so that they get an implicit reconcile and thus update that last increment? Or will this work if all users have their own/separate version?

I hate to assume.

MikeMillerGIS
Esri Frequent Contributor

The attribute assistant code makes an unversioned edit to the table.  

0 Kudos
TiffanyPuett
Occasional Contributor II

...that doesn't really answer my question. Can someone else perhaps answer my question? I'm trying to understand so that I may trouble-shoot an issue.

0 Kudos
JustinStangl
New Contributor II
Mike, thanks for the input.  Actually our GenerateID tables are not versioned, each editor has their own seperate Dynamic/GenerateID tables linked in their MXD with different 'sequence' values in each table (1, 7, 10, 11), in order to reduce the number of duplicate ID's generated. 
However the sequence counter is not taking these numbers into account, its just going with the next number in sequence (1,2,3) instead of (7,14,21).  How can i get it to use the sequence numbers from the GenerateID table when generating ID's??
0 Kudos