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; } } }

Pass Global ID from Collector to G

kkoz490

Has anyone been able to pass the Global ID from a service in Collector to the related GUID in Survey123 using the URL method?

I have a database relationship of Bridges to Inspections. In addition, Inspections have related Elements. Since Survey123 can only go two deep in relationships I have a service for Bridges in Collector and the Inspections and Elements in Survey123. I have created the Survey123 from the Inspection and Element service.

Find more posts tagged with

Accepted answers

All comments

JamesTedrick

Hi Kevin,

What you're asking for is possible. You would need to configure the Bridges layer's pop-up to have a url that includes the GlobalID in the parameters; this is described in Integrate with other apps—Survey123 for ArcGIS | ArcGIS and https://community.esri.com/groups/survey123/blog/2016/07/30/understanding-survey123s-custom-url-scheme . This would go into a hidden field.

There is a known issue with Survey123 receiving the globalid value - it can't process the value if it already has curly braces ( { } ). To get around that, the survey should be designed with 2 fields to handle the globalid value:

The first field (let's cal it "incoming") should be a hidden field (or text, if you want to validate that it's receiving the value) that has a fieldType null (so it isn't submitted to the database. In your case, using an existing feature class, this would be added if you have Survey123 create a form based on the feature class
The second field (parentglobalid) will hold the value, minus any curly braces. This can be a calculate (or again, text for validation checks) question with a formula like:

if(regex(${incoming}, '^\{[\w\-]*\}$'), substr(${incoming},1, string-length(${incoming}) - 1), ${incoming})

The regex detects if the guid is formatted as {1080901b-c30d-411b-a485-151c8f6ad8e6}, if the braces are present, it extracts the portion between the braces, otherwise it passes the guid unaltered. The field type should by of esriFieldTypeGUID.

See the attached sheet for an example of this pattern.

globalid_incoming.xlsx

kkoz490

Hello James,

I appreciate your response. I read the articles you provided, they were informative. Being an old GIS dog trying to learn new tricks, I still have some questions.

My goal is to maintain the relationship class between the Bridge service’s GlobalID and the Bridge GUID in the Inspection service. If I have created the survey by importing the Inspection service schema, which has the Bridge GUID already and cannot be seen in the survey as a question, how would I list this existing GUID as a question? Documentation says that reserved fields in a feature layer are not added to the XLSForm, which GloabalID is a reserved word. Adding such a field with the same name would seem to change the Inspection schema and create a new service. Your example calls this the “theguid” in the XLSForm.
How does a GlobalID and GUID work if the curly brackets are removed?

Below is my thought process based upon your suggestions.

Bridge feature service has GlobalID field.
Inspection feature service has a GlobalID and brdg_guid fields.
In the Survey123 form have the following questions added:
- brdg_guid_txt as type null
- brdg_guid as type esriFieldTypeGUID and the calculation for the regex statement
Have Collector Bridge popup as: arcgis-survey123://?itemID=fe06d025e41a4ceabdb3dd1ba15713c6&field: brdg_guid ={GlobalID}

Thank you for your help,

Kevin

JamesTedrick

Hi Kevin,

When Survey123 creates a form based on an existing feature service, it omits the GlobalID and GUID fields as the form rendered (including bridges and inspections) would automatically manage the relationships. When switching to a URL-launched survey, we go from automatic management to manual management. You need to manually add the ParentGUID question manually to accommodate this.
From the question, are you planning to edit the Bridge layer when being launched by a hyperlink? This is currently not supported; opening the app by hyperlink is supported for add only (Inspection form)
Survey123 supports fields with a bind::Esri:fieldType of null - this means that a question will not be submitted and has no effect on the table schemas
The curly braces are added automatically by Survey123, which is why they need to be removed

The URL as you've specified looks to be appropriate for what you're describing.

kkoz490

Hello James,

I was able to implement your suggestions and it worked. Old dogs can learn new tricks. Below is the general outline I used in case someone needs to do the same type of function.

Create database in a file geodatabase with relationship class of Global ID to GUID.
Create ArcMap document with data layers and save as service in AGOL.
Set service to allow editing and share to editing group.
In Survey123 Connect, create new survey by importing service.
In XLS Form add a text question that has a Null field type for holding the related Global ID.
In XLS Form add a text question that has a GUID field type. For the question name, use the same name as the GUID in the service.
For the GUID question use the following calculation to remove the curly brackets from the Global ID. if(regex(${brdg_guid_txt}, '^\{[\w\-]*\}$'), substr(${brdg_guid_txt},1, string-length(${brdg_guid_txt}) - 1), ${brdg_guid_txt})
In AGOL create a web map with the related service to the one in Survey123. Use the following popup line. arcgis-survey123://?itemID=affe05ec8db8448daccb0688c9583ce8&field:brdg_guid_txt={GlobalID}

Thank you for your help. If you are every in Olympia, WA please let me know. I owe you a cup of coffee.

Kevin

SuddhaGraves

Hi James,

I have a follow up question associated with this topic. I was able to successfully pass the GlobalID from Collector to Survey123 using the custom url. It works as expected when creating a new record. However, if I try to edit an existing record using the inbox in Survey123, I get a Code 400 send error. After much trial and error, I noticed the GUID field had the curly brackets added back into the value. If I went in and removed the curly brackets during the edit and resubmitted it would successfully update. Otherwise, I get a Code 400 send error. Any thoughts?

Suddha

AliciaRitzenthaler

Closely related to the original question, I am trying to pass the GlobalID from Collector features into a Survey123 field called CollectorID.

When the CollectorID field is text this works. When the CollectorID field type is GUID however it appears to work (GlobalD passed, no brackets) but I cannot save the survey. I get the following message:

Any idea how to pass a GlobalID from Collector to a GUID field in Survey123? I am passing the GlobalID to a GUID field because I need to set up a relationship class between the Survey123 and the Collector features based on this passed GlobalID. If someone has an alternative way to get around this I'm also open to that.

JamesTedrick

Hi Suddha,

See my comments in https://community.esri.com/message/761251-re-survey123-converting-characters-to-code?commentID=761251&et=watches.email.t… - for working with curly braces in globalids.

SuddhaGraves

Hi James,

Thanks for the responding. I have read through the comment you suggested and I verified that I was following the instructions as noted in the comment. The process appears to work when submitting the initial record. However, the problem arises when I have to edit an existing record from the inbox. When editing an existing record, the curly braces are put back on the GUID field. Unless I manually remove the braces, I will receive an error when submitting. I am hoping there is another way to automatically remove the curly braces when editing an existing record.

Thanks,

Suddha

JamesTedrick

Hi Suddha,

I would not use a form that takes in the globalid via URL parameters in conjunction with the Inbox - we do not support editing via URL currently. As I mentioned in the comment, the behavior of globalids and curly braces will be addressed in a future release of Survey123.

ChrisBlinn1

Can the incoming and parentglobalid fields be hidden? When I set the type to hidden, it doesn't populate the parent GUID.

JosGabrielOcampoGiraldo_0-1731625450954.png

newMapViewerAndEd-01-newMapViewer-IntroImage.jpg

arcgis_fmpng.png

ElliottPlack1

Did you solve this? It is possible the incoming Global ID is not formatted correctly and James Tedrick‌'s answer above could work.

ShanaGail1

Oh nooo... I had totally missed this issue of not being able to edit an existing feature using Survey123. I had plans to incorporate this into the workflow for 2 different projects and need to come up a plan B quickly. We really wanted to have the field inspector fill out a Survey. Is there an elegant workaround? Is the functionality in a project plan?

Thanks,

Shana

EvanOlivier

Hello Kevin,

Does this method prevent survey123 from creating it's own feature in the feature service, instead allowing the related table information to pass back into the existing feature you opened from collector? If so, this would be very useful for me as well. I am trying to build a workflow where inventory is collected in collector, while inspections of the asset are done in survey123. At the moment, uploading will create a point from collector inventory and another pole point from survey123, with the first containing only inventory information and the later containing no inventory information and only related table inspection information, requiring us to join the two points into one feature later. Definitely not ideal. Please let me know, thank you.

IMG_1711.JPG

Laura_B_0-1731633345178.png

kkoz490

Hello Evan,

I just completed creating a culvert inspection application where culverts have related inspections. The culverts is in one service and the inspections in a different feature service since Survey123 always creates its own point. Hopefully, at some point Survey123 will work with tables too. I pass the GlobalID from culverts to the inspections through a URL link. In the Survey123 connect form you do have to add the foreign key question as hidden and type of GUID. That is the question field you pass the related GlobalID too. No more needing to add a text question in Survey123.

Hope this helps,

Kevin

EvanOlivier

Hello James,

I am creating a workflow that would do something very similar, with one important distinction.

We will be utilizing collector to gather inventory of a utility pole, and it's related table components that exist in one feature service with the Poles Feature Class and it's related component tables (Cross Arms, Insulators, etc). Then, we will be inspecting those assets in survey123 that is built from a different, existing feature service that contains an All Inspections Feature Class and the related Pole Component Inspection Tables (Pole Inspection, Cross Arms, Insulators, etc).

I've got the relationship classes down, indexing figured out and an appropriate guid field to pass the Global IDs of the Pole & it's attached components to, but have one major question I am concerned about now.

Say we have 2 cross arms on the pole, and I need to pass the two cross arm Global IDs that will show from the popup of the pole (pulled from the cross arm component related table) into two separate repeats within the PoleCrossArmInspections table(repeat) inside of survey. So Cross Arm A sends the Global ID into the CompRel_GlobalID Guid field of the first repeat in that table, and Cross Arm B sends that Global ID into the CompRel_GlobalID Guid field of the second repeat in that table.

Is this possible at all? If not, do you have any ideas for a work around?

The structure of the relationships are established as this, with GlobalID being the parent keys and Rel_GlobalID being the foreign or child GUID keys. Then, there is a third relationship class that links the GlobalIDs of the Cross Arm Inventory Table (blue) to the CompRel_GlobalID GUID child or foreign key field of the Cross Arm Inspection Tables.

COLLECTOR (Feature Service 1) SURVEY123 (Feature Service 2)

Poles FC (Inventory of Poles) (GlobalID) All Inspections FC (GlobalID)
(Rel_GlobalID)-Related Table Cross Arms (GlobalID) -------->(CompRel_GlobalID)Related Table Cross Arm Inspections

(Rel_GlobalID)

Thanks for your consideration here.

Evan

JamesTedrick

Hi Evan,

It is not currently possible to send data into multiple repeats. Instead, you may want to have a separate form for cross arm entry that gets opened for each cross arm.

EvanOlivier

Hi James,

Thanks for your response. Would this require the Cross Arm form to be a feature class of it's own instead of a related table? Or could I cut out the rest of the feature service from that form and publish a component only survey that shares the submission url of the larger feature service?

Best,

Evan

Anonymous User

Hi James,

Has this function been removed? I tried to do this the way you said but my guid field (and even the text field) always end up blank. I can see it in my url that it's getting sent but for some reason survey123 is not reading it.

Anonymous User

Hi Kevin,

Did you need to create a relationship between the culvert and inspections beforehand? Have you tried passing the GLOBALID from one service to the GUID of another service (but they're not related)? I am doing it this way and I can see from my url bar that it's getting passed but it's not showing up in the survey.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

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