ArcGIS Online Experience Builder Table number decimal places

1092
5
03-30-2023 12:14 AM
Labels (1)
LIEPAJABUILDINGBOARD
New Contributor

Hello!

I have created ExperienceBuilder app with table widget displaying field of numbers with decimal places. In the webmap I have configured decimal places up to two digits, but in the ExperienceBuilkder Table it displays many decimal places. It appears not to all othe entries but to several of them. As these are money amounts, the more than two decimal places look weird. Where should it be configured to display certain amount of decimal places? Below are examples (screenshots) showing decimal places of the same entry. 

 

Screenshot No. 1: Experience Builder Table widget number decimal places extended

Lidzfin_decim.jpg

 

Screenshot No. 2: WebMap pop-up of the same element number field

Lidzfin_decim_pop_up.jpg

5 Replies
AndreasHall
Esri Contributor

I found a related community post where the answer is that removing thousands separator and other settings are on the road map. Hopefully the product development team pick up your request as well!

How to remove comma separator in Experience Builde... - Esri Community

There is also a bug documented: BUG-000152331: The thousand separators are not honored by the Table.. (esri.com). You could try to reach out to technical support in your country and report this as a bug.

TomKukitz
New Contributor III

How is this fix coming along? I have Manholes with slopes in EB looking like this: 1.02365897458295%

This is inexcusable! My Director asked me to fix this and I said I can't Esri has to fix it. He made the comment of for how much we pay for this GIS system something like this should not be an issue!

LindsaySpencer-Henderson
New Contributor

Hi @AndreasHall - will this be addressed with the next update? If anyone has found a work-around, please advise, thanks!

AndreasHall
Esri Contributor

Sorry, I do not have any insights in the development of Experience Builder. I am not on that team.

0 Kudos
NIC
by
New Contributor

Any updates on this issue? I'd really prefer not to have to shorten 60+ fields on a live layer.

0 Kudos