nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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-survey123/td-p/822843

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.

Find more posts tagged with

Accepted answers

All comments

dougbrowning

Had some other team reach out to me just today that this is STILL an issue, which I am sorry is just insane. Esp since I have talked to each team in person face to face. Yet 5 years and counting.

BUMP

thank you

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/td-p/92900

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

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

ArcPro edits change globalid.gif

BUG-000146406

dougbrowning

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.

RobertBorchert

It could be a conflict between database formats.

Is your data stored in the Cloud or on a server somewhere.

dougbrowning

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.

RobertBorchert

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.

dougbrowning

No I have not heard anything. Status is In Review it says. I tried to escalate it already.

HarshalGharat

Hi,

I tried to look up this bug but didn't get any information around it. Do you know if this has been resolved?

dougbrowning

Esri now agreed to update this to a bug BUG-000146406

thanks

dougbrowning

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.

thanks

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.