OBJECTID as the primary key in a feature class is not populating the foreign key in a related table

08-07-2020 11:14 AM
New Contributor III

I assumed you could use OBJECTID as the primary key as long as you don't split features (Relationship class properties—ArcGIS Pro | Documentation) ? I have a partner organization working on a database for my work group and they don't want the field crews to type in IDs for the features so we thought that if we used the OBJECTID as the primary key, it would auto-populate the foreign key field (which we set it up as a Long) of a related (1:M) inspector table so the numbers would be sequential and there wouldn't be an issue of two field workers accidentally trying to submit two records with the same IDs.

Thoughts/insights/clarifications are welcome!

0 Kudos
0 Replies