1

Is there a workaround for using Esri's Attribute Assistant's Autonumber or GenerateID in a versioned environment without creating duplicates?

re: Attribute Assistant and Versioning

could Python autoIncrement perhaps accomplish new unique IDs in a versioned environment if AA cannot?

Improve this question
3
  • 1
    The GenerateID table should not be versioned, even if the feature classes it populates are versioned. Attribute Assistant is still able to use and increment the ID values in the non-versioned GenerateID table during a versioned edit session. A single user can also do field calculations on non versioned feature classes or tables during a versioned edit session, but they have to switch to a non-versioned edit session to manually type values into a non-versioned feature class or table.
    – Richard Fairhurst
    Commented Jul 2, 2019 at 20:44
  • 1
    Because the GenerateID table is non-versioned it resticts that table to being a single user table during edits. Since only one user can update the table at a time and non-versioned edits are done quickly by Attribute Assistant, only one versioned user can gain control of the table at a time to read and update the ID value, which allows Attribute Assistant to avoid duplicates.
    – Richard Fairhurst
    Commented Jul 2, 2019 at 20:52
  • @RichardFairhurst These excellent comments would be great as an answer
    – Midavalo ♦
    Commented Jul 25, 2019 at 0:21

1 Answer 1

Reset to default
2

The GenerateID table should not be versioned, even if the feature classes it populates are versioned. Attribute Assistant is still able to use and increment the ID values in the non-versioned GenerateID table during a versioned edit session. A single user can also do field calculations on non versioned feature classes or tables during a versioned edit session, but they have to switch to a non-versioned edit session to manually type values into a non-versioned feature class or table.

Because the GenerateID table is non-versioned it restricts that table to being a single user table during edits. Since only one user can update the table at a time and non-versioned edits are done quickly by Attribute Assistant, only one versioned user can gain control of the table at a time to read and update the ID value, which allows Attribute Assistant to avoid duplicates.

Improve this answer
1
  • Thank you for the helpful insights!
    – sirgeo
    Commented Aug 14, 2019 at 12:37

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.