There are a few of us that have been posting inconsistencies with case on globalid.
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.
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.
Seeing 123 doing lower case also
And when I look at this form in Pro I again get both depending on the attribute table or the popup
No idea which one is "correct" still.
I believe the issue lies with your avatar. If you change it to a Vikings Logo the sky will be blue for you once again.
On a less serious note. I just looked at the results of all locations collected in the field in the last 3 months for one of my apps and they are all uppercase.
Where did you look at them? If you look at them in Pro it will convert it for display. Look at them in a AGOL map or at the actual data service and you will see lower.
It is a hosted service. Esri support confirmed the issue as did others at Esri so I am pretty sure it is not something unique to me. The hard part is it may look different depending on where you look. But it is for sure consistent.