Honestly it is crazy that this is a workaround for such basic functionality of the software. Appreciate the help with the video but my god, it's painful? It's been a bug for over two years and still hasn't been solved with ArcGIS Pro 3.0, please resolve for my sanity!
This workflow works fine, with one caveat: The related table for Survey A must be a STANDALONE table. If you try to do the next to last step -- calculating into the Parent GUID field the new Parent GUID values captured by the join, you will get an error message if RelatedTableA is still linked to its host layer. Once I realized that, I exported RelatedTableA to a standalone table, and it was smooth sailing from there.
Hello @RickBombaci, can you tell me what error number you are receiving? I am attempting to append data into a related table, but I am getting the error message 999999. I am wondering if it is because one of my tables is not a standalone table.
Hello @@rebekahlindborg1782 , sorry for the delayed reply. I don't remember what error message I received. I'm reading my comment from 10 months ago ... If you want me to try and help you troubleshoot, feel free to provide more info about your situation. From my comment, it sounds like you just need to do the export prior to the calculation step toward the end of the process.
Why isn't this as simple as checking a box in the environment settings of the append tool to preserve GlobalID's with an appropriate warning for the user about the risks of copying the GlobalID
Hi Paul, thanks for the comment. I've passed your feedback on to my counterpart in the ArcGIS Pro space. You may also be interested in up-voting this ArcGIS Idea: community.esri.com/ideas/13150-preserve-globalid-on-append
Hi Paul, It will be that simple soon, The following enhancement is in the Product plan: ENH-000113717 : Add ability or workflow that would allow Append operations to preserve Global ID for hosted feature layers with relationships .
Do you have a tutorial about how to configure the survey 123 to save the collected data into a specified Enterprise Geodata base as soon as you sync it?
What's the point of creating the new field in the Related Tables? Can you update the ParentGlobalID of the related table with the GlobalID of Survey B after the join?
Because SurveyB autogenerates new GlobalIDs during the append. When looking at the data type one will have "Global ID" another will have "guid". The former is the one that autogenerates. Because SurveyB GlobalID is now different, during the join between related table A and SurveyB calculating into that new field will help when appending SurveyA related table to SurveyB related tables (after following the second calculation step).
