I am seeing that the Attribute Table and the Attributes pane show GlobalID differently. One is all upper case and one is lower.
I would call it a bug.
thanks
If you have any options to escalate the bug via your support please do.
ENH-000130624 and BUG-000146406 : Upper and lower case globalids
Thank you Doug for your persistence on this issue that really should be fixed ASAP.
We ran into query issues in our FME -> ArcSDE flow. After a lot of debugging it turns out ESRI should give a few more **bleep** about GUID standards.
@BenGunnewijk I met with the ArcPro team in person at DevSummit and they are looking at it. Maybe @KoryKramer can update.
Did confirm there is no standards board at Esri and there really should be. All companies struggle with consistency of course and it leads to a lot if interoperability issues.
I looked at this in ArcGIS Pro 3.5.1. While the GlobalID in ArcGIS Online displays with lowercase letters:
When added to ArcGIS Pro, it displays uppercase, in the attribute table and attributes pane:
The pane is also showing that I was able to successfully join local data to the hosted feature layer from Online using globalID, even though one is stored uppercase and the other lowercase.
Are you still running into interoperability issues?
I have not tested in a bit but try making an edit and see if it changes it on you.
@KoryKramer Sorry was busy getting back from vacation.
But I just tested now in Pro 3.3.5 and its still doing it. Sorry for the long gif its a HFS that is slow today.
See I change a totally different field and GlobalID goes uppercase on me which does break the relate. This was a 123 form data I was editing. 123 makes them all lower to start as does Field Maps.
No problem editing.
@BenGunnewijk , as much as I agree that consistency within and across a company's product lines is important, I am interested in what "GUID standards" you are referring to? ITU-T X.667, RFC 4122 (now RFC 9562), or some specific company's implementation like Microsoft (based on RFC 4122)? Or is it really about Esri just being consistent with their own Global ID implementation?
2-cents,
ArcGIS field data types
(ArcGIS Pro 3.3, 3.4, 3.5)