I created a hosted Feature Classe using Survey123 and published it.
I created a Web Map via the new Map Viewer and added the FeatureClass.
I tried to create a link from an entity to open Survey123 and open the form to update feature attributes. I used the
$feature.globalid
attribute to create the following link :
globalid is present everywhere.
However, when I opened the same map in Field Maps, the globalid using $feature.globalid mysteriously disappears
I didn't succeded finding any explanations about this. However the objectid displayed by using $feature.objectid works well...
Solved! Go to Solution.
Since this bug is still unresolved, I've developed a workaround with a colleague @StevenFabijanski . The StandardizeGuid function can be used to cast the Global ID to a text variable and can be done in a way that strips the curly brackets, which may help with it not being displayed in Field Maps. (historically, Collector had a tough time with Global ID display and would appear differently on various platforms (iOS, Windows, Android.) By standardizing you can bypass the bug.
Simply set a variable like so and then swap out the GLOBALID with your Global ID's field name.
var standardizedGuid = StandardizeGuid($feature.GLOBALID, 'digits-hyphen');
Try
$feature["GlobalID"]
or
$feature.GlobalID
Wondering if it 's a case sensitivity thing.
Well I tried those two. Works well in Map Viewer
But still not working in Field Maps
Since this bug is still unresolved, I've developed a workaround with a colleague @StevenFabijanski . The StandardizeGuid function can be used to cast the Global ID to a text variable and can be done in a way that strips the curly brackets, which may help with it not being displayed in Field Maps. (historically, Collector had a tough time with Global ID display and would appear differently on various platforms (iOS, Windows, Android.) By standardizing you can bypass the bug.
Simply set a variable like so and then swap out the GLOBALID with your Global ID's field name.
var standardizedGuid = StandardizeGuid($feature.GLOBALID, 'digits-hyphen');
This is a bug