Hello,
I would like to submit the following issue, for which I cannot find a robust solution.
In ArcGIS, I need to establish a one-to-many relationship between a feature class (the origin table) and a standalone attribute table (the destination table). I intend to use GlobalID as the primary key and GUID as the foreign key. The aim is to create a web map to which features and relevant attributes can be added and edited via a form.
I understand that this workflow functions correctly in ArcGIS Pro when the relationship class involves a destination table that contains all the necessary fields (including GUID) but has no records (see the video tutorial ESRI Canada, Setting up Your Data for Editing Related Records, https://www.youtube.com/watch?v=HYrS34WUnn4, for example). Once the map is published in AOL MapViewer, records can be added and the relevant GUID values are generated automatically, enabling the relationship to work as expected.
However, in my case, I have a destination table that already contains a large number of records related to the origin table. Fields with the same value are already present in both tables to allow association of related records, but I would prefer not to use them as keys in a relationship class.
While defining the primary key is not a problem, I understand that the issue lies in generating the appropriate GUID value in the standalone attribute table. The value generated directly in the table using the '+' symbol is useless in this context. Therefore, the relationship class does not work.
What would be a feasible solution to overcome this problem and achieve the desired result?
Thanks you in advance.
