Dear ESRI Community, This question comes in two parts
Firstly – Can anyone confirm that if the Feature Classes we create are versioned this means then that it is IMPOSSIBLE to create unique indexes on any of the Feature Class Columns? You cannot therefore constrain unique data in any of the Feature Classes.
Secondly – This being the case has anyone a possible work round for this problem? Not being able to constrain uniqueness in data model fields is a fairly basic requirement.
You may be asking.... why ask this question…
Why do we want versioned Feature Classes – for offline capability
Why do we want uniqueness on fields – to force data integrity
It would seem in this thread this lack of capability (no unique indexes) is documented - https://community.esri.com/message/614898
Has anyone else found this a limitation?
Any suggestion on how to get round this?
Grateful for any suggestions