Field Maps is creating lowercase GlobalId but AGOL does uppercase

[DougBrowning]

There are a few of us that have been posting inconsistencies with case on globalid.

See here https://community.esri.com/t5/arcgis-survey123-questions/globalid-in-lowercase-from-collector-to-sur... 

and https://community.esri.com/t5/arcgis-pro-questions/globalid-inconsistent-display/m-p/291405 

I think I may have traced it down to Field Maps.

If I add a feature in a web map in the browser I get uppercase GlobalID.  If I use the exact same map and add in Field Maps it does lower case.

AGOL Add

Field Maps add

Then ArcPro changes the lower to upper for display

So the exact same record shows lower in AGOL and upper in Pro.

The big issue here is my relationship class will NOT match lower and upper so all my relationships are breaking.

At this point I am not even sure the standard?  More info in the posts.

Please help I am going nuts.

[DougBrowning]

Got a gif of it happening today.  Even when I edit a different field it does it.  Will it ever get fixed?  thanks

BUG-000146406 

 

[DebSF]

@DougBrowning I realise this is pretty old now but did you ever get it sorted?

I have a point dataset with related table using GlobalID to a GUID field, set it up and Pro, worked okay, uploaded it to AGOL and now when I view in Pro I can't see the related records. The only potential cause I can see is this uppercase/lowercase issue.

[DougBrowning]

Uploading to AGOL probably changed the globalids on you.  That is why I do it use them as the key.    See ,y post here on not using them. https://community.esri.com/t5/arcgis-collector-questions/related-tables-for-offline-data-collection/...