AGOL unique constraint for relationship classes

06-14-2021 09:47 AM
Status: Open
New Contributor III

Now that it's possible to set a unique value constraint on hosted feature layer fields is there anything which I should be aware of if I start to use fields other than globalid as primary keys in relationship classes? Being able to use string and number fields as keys would make reading related tables a lot easier. 

Perhaps ESRI can provide some guidance on this? It would be useful to know what the potential issues are now if not using globalID as the origin key.