Yes this is exactly what I did....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.
I see someone else is having the same issue posted on ESRI.
Hey all, I have a workflow where I annually publish a map with updates reflecting new features from field maps, and we are working for the 2023 iteration of these maps now. Generally, I will go to the previous years map, export all of my features as shapefiles or FGDB files add them to the new map, and load them into my new database. However, my relationships are built on GlobalID to GUID relationships, and to not lose visibility on inspections, I will do "Preserve GlobalIDs" and assign the new Global ID field to the GUID field as the ESRI procedure states. I have done this successfully for a few years now, but we have run into an issue where we get a warning saying that to use "Preserve GlobalIDs", we have to have a unique index on the GlobalID field. I saw on some ESRI documentation that using the "Add Attribute Index" data management tool will fix this, but it has not in my case. Even after I run the tool I get the same error. Can someone help point me in the right direction? We use this workflow quite a bit and it will be difficult to make this work without a fix. Thanks, Damon
Thank you
