HOW TO
When working with related tables in ArcMap, some form of unique value is required to represent the relationship between the 'primary key' and 'foreign key'. Esri recommends creating relationships using the GlobalID field on the layer so the primary key of the relationship is unique when establishing a connection to a new inspection record.
The most convenient way to achieve this is through Global IDs and GUIDs. Both data types store registry style strings comprising 36 characters enclosed in curly brackets, for example, {90A942E1-BC7C-4F1E-94D5-AACAAD24F08C}.
Global IDs and GUIDs have a few differences. ArcGIS actively maintains Global ID fields (that is, when a new feature is created, a GUID value is assigned), whereas, GUID fields are left blank. The onus is on the user to maintain these fields.
To use related tables in a Relationship Class, the Global ID in the origin table can be used as the primary key, and the GUID field in the destination table can be used as the foreign key. Using this method, ArcGIS automatically copies the primary key (Global ID) into the foreign key (GUID) field.
The following workflow demonstrates how to set up related tables for use in ArcGIS Collector or ArcGIS Field Maps by adding Global IDs in ArcCatalog. In this example, a relationship is made between a feature class, Weeds, and a related table, Inspections.
Article ID:000015422
Get help from ArcGIS experts
Download the Esri Support App