Open existing record in Survey123 phone app via link from Field Maps popup

[DuncanC]

I'm struggling to get something that should be really simple working.

I'm viewing the feature layer from a Survey123 survey in Field Maps.  I want to have a link in the popup in field maps that opens Survey123 with the currently viewed record opened in it. 

I've used a similar feature to open an existing record in the web form to edit with no trouble but wasted hours fighting with this and can't get it to work.

I've reviewed the documentation:

https://doc.arcgis.com/en/survey123/get-started/integrate-launchfieldapp.htm

I've read the two forum posts I can find that were releated:

https://community.esri.com/t5/arcgis-survey123-questions/existing-record-not-opening-when-linking-fi...

https://community.esri.com/t5/arcgis-survey123-questions/url-with-query-parameter-to-open-existing-s...

I've tried it with update, even though I don't want to have it update. I want to assume the user already has up to date infomation in their inbox. (we are using inbox for this Survey)

I've tried it with q:where=globalId=<GlobalID> & q:globalId=<GlobalID>

https://survey123.arcgis.app/?itemID=<ItemID>&action=edit&q:where=globalid=<ID>

If anybody could point me in the right direction it would be greatly appreciated!

[DuncanC]

Well, this is the code I mentioned in my last reply to you I could dig out...  Looks like you already have it. If it's not working my first thought is did you comment out the update = true bit?  When I was working with it the best I could tell it was bugged and didn't work unless you update, it just opens the inbox and sits there.

[JoshB123]

Thanks for your thoughts, it actually was the update=true part, got it working now!

I've found a workaround by setting up two Survey123 forms with Inbox's, one for editing the survey layer and one for editing the related records layer. Then have separate hyperlinks to each one in Field maps. It would be nice to do it all in one, but may have to leave it in the interest of time

I take your point about preferring Field maps too. It works out really well for my situation being able to view the results on Field maps, both lines and polygons together, then editing through Survey123.

Thanks

Josh

[EmbertMorton]

I went with a private ASN for my initial BGP testing and small-scale routing. It’s cheaper and avoids the overhead of managing global announcements. But if you’re aiming for multiple upstreams and visibility in global tables, public ASN is the way to go. Depends on whether your network needs true multi-homing or just internal routing control.