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; } } }

AGOL Map Viewer treating text field like numeric field and adding decimal point after values

Bec

I was doing some updates to a pop-up for an Intersections layer that is hosted in AGOL and noticed that some text fields that have numeric values are being treated as numerical fields even though they are clearly showing as a text field for the data type. This same layer if I bring it into Pro, the fields are displayed correctly. Does anyone know why this might be happening? And is there any way I can fix this so that it will display correctly within AGOL since this is part of a dashboard? See the below images for examples. Take a look at the following fields: Functional School Zone, Council Districts, and Signal ID.

AGOL Table ViewArcGIS Pro Table View

Find more posts tagged with

Accepted answers

Bec

Mike,

Yes, both the data source in Pro and AGOL are the same. This data was originally published to AGOL back in November or December of 2023. And yes, weirdly it is adding decimal points and zeros after some of the decimal points in the three string fields I pointed out, but like you noticed, it is not consistent. I never saw the issue I am seeing now back then when I first published the data. I will reach out to my technology department to let them know this will need to be sent up to ESRI support. Thanks!

All comments

CVCJ

I also get this error. Did you hear back from Esri technical support?

Bec

Mike,

MikeMinamiP1

Hi @Bec

Are you saying that decimal points are somehow being added to your data for a string field? That would be a very weird bug. It's also strange that it's not happening consistently. In the Functional School Zone field, sometimes 99.0 displays and other times, just 99.

Are you showing the exact same data source in Pro and Online? Is that a hosted feature layer?

Is it possible that somehow the data was corrupted before publishing to ArcGIS Online?

I'd suggest contacting Esri technical support. This is an issue that we'd need to look at the data and understand how it was published to troubleshoot.

Mike

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.