Hi everyone, I am currently facing a blocking issue with Survey123 regarding ID management when creating related records via a begin repeat. My Architecture: * Environment: ArcGIS Enterprise Portal with an Enterprise Geodatabase (SDE). * Service: Referenced Feature Service (not hosted). * Structure: A "Line" layer (Parent) and a "Points" layer (Children, 1:M relationship). * Relationship Class: Based on the Line's GlobalID to a guid_globalid field (GUID data type) in the Points layer. The Problem: When filling out a form using a begin repeat, Survey123 correctly links the children to the parent within the mobile app. However, upon submitting the data to the server, the IDs become out of sync: * The server (or SDE database) rejects the temporary ID generated by the app and creates a brand new definitive GlobalID for the parent Line (e.g., {AAAA-AAAA...}). * The issue is that the child Points retain the temporary ID initially generated by Survey123 (e.g., {BBBB-BBBB...}) in their guid_globalid field. Result: The points become orphaned on the server and my relationship is broken, because the server changes the parent's ID without updating the foreign key of the related children. Given that this is a referenced layer from an SDE database, would anyone have a workaround or solution for this conflict? Is there a specific setting I missed (on the ArcGIS Pro publishing side, Enterprise GDB configuration, or an option in Survey123 Connect) to force the relationship to be maintained? Thanks in advance for your help and insights!

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Survey123 GlobalID / GUID desynchronization in a repeat (SDE Referenced Feature Service)

HatimKhayroun

Hi everyone,

I am currently facing a blocking issue with Survey123 regarding ID management when creating related records via a begin repeat.

My Architecture:

Environment: ArcGIS Enterprise Portal with an Enterprise Geodatabase (SDE).
Service: Referenced Feature Service (not hosted).
Structure: A "Line" layer (Parent) and a "Points" layer (Children, 1:M relationship).
Relationship Class: Based on the Line's GlobalID to a guid_globalid field (GUID data type) in the Points layer.

The Problem: When filling out a form using a begin repeat, Survey123 correctly links the children to the parent within the mobile app. However, upon submitting the data to the server, the IDs become out of sync:

The server (or SDE database) rejects the temporary ID generated by the app and creates a brand new definitive GlobalID for the parent Line (e.g., {AAAA-AAAA...}).
The issue is that the child Points retain the temporary ID initially generated by Survey123 (e.g., {BBBB-BBBB...}) in their guid_globalid field.

Result: The points become orphaned on the server and my relationship is broken, because the server changes the parent's ID without updating the foreign key of the related children.

Given that this is a referenced layer from an SDE database, would anyone have a workaround or solution for this conflict? Is there a specific setting I missed (on the ArcGIS Pro publishing side, Enterprise GDB configuration, or an option in Survey123 Connect) to force the relationship to be maintained?

Thanks in advance for your help and insights!

Najděte více příspěvků označených jako

Accepted answers

dougbrowning

I am confused as there are no globalids until the record enters the database on a submit. Are you adding code to try and generate ids or something in the form? You should not even have globalid or parentglobalid listed in the form that is all taken care of automatically.

Post up at least those parts of your form to see what you are doing.

Personally I let 123 use those fields but them have a second relate with a readable key I mange myself. That way they are always connected when moving the data to export, import into a diff database, etc.

All comments

dougbrowning

Post up at least those parts of your form to see what you are doing.

HannesVogel

Hi @HatimKhayroun , did you use Survey123 Connect and the option to use the existing FeatureService you published from the SDE?

Your shown GUID doesn't look like a Globalid managed by the SDE, those have mostly a format like 84858C3D-8984-4A4D-9C6C-2EF55B55F985

HatimKhayroun

Hi, thanks for your reply!

Just to clarify, I am not adding any code or manual calculations in the form. I am letting the repeat handle everything natively.

Since I have a 1:M relationship class properly set up in my SDE database (linking the parent's GlobalID to the child's GUID field), I rely entirely on Survey123's native behavior to manage these IDs during the submission. I don't have those ID fields listed or calculated in my XLSForm.

That being said, your idea of using a second relate with a custom readable key that I manage myself is a really cool solution! It's a great workaround to make sure the records always stay connected during exports or database moves. Thanks for the tip!

HatimKhayroun

Hi, thanks for your help!

To answer your first question: Yes, exactly. I used Survey123 Connect and chose the option to create the survey directly from the existing Feature Service published from our SDE.

Regarding the GUID format: sorry for the confusion! {AAAA-AAAA...} and {BBBB-BBBB...} were just dummy placeholders I used in my forum post to make the explanation easier to read.

In my actual database, the GlobalIDs and GUIDs do follow the standard format (like 84858C3D-8984-4A4D-9C6C-2EF55B55F985). So the format is correct, but the desynchronization between the parent and the children still happens natively upon submission to the SDE

dougbrowning

Weird not sure what it is mad about, maybe case sensitive?. I got a full right up on using other relates here. https://community.esri.com/t5/arcgis-survey123-questions/mapping-with-survey123-within-a-polygon-or-admin/td-p/836112

Připojte se ke konverzaci

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.