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

How to remove comma separator in Experience Builder table

CalebAnderson

Hello! I'd like to remove the thousands comma separator in the table I have in an experience:

I tried going to the visualization for the feature and unchecking the thousands separator. Also tried pulling the data from a web map where I did the same with no luck:

Find more posts tagged with

ArcGIS Online

Accepted answers

All comments

DustinGriffin_GISP

This is pretty unbelievable... I held off on WAB migration to ExB for long as possible because of these type amongst many other app update issues and we still can't perform the most simple of formatting adjustments and have them persist. ESRI has completely lost the plot here. Soon as I complete my open source mapping toolset I'll be slowly getting every client possible off ESRI. I simply can't endorse these products anymore as ExB and Pro have moved GIS backwards instead of forwards.

DanCopKac

how do i fix this issue in the search widget's result? The map service was added via URL, so it's only part of the Experience, it's not part of a web map so I can't change the settings in the web map.

Ming

This issue has been fixed in ExB v1.18.

Ming

For JSAPI v4.32, you can:

1. Following the official link to install the JSAPI offline (don't need to install calcite offline) and update the variables arcgisJsApiUrl

https://developers.arcgis.com/experience-builder/guide/install-guide/#install-the-offline-node-cache

2. On your web server that hosts JSAPI, navigate to 4.32 --> Esri --> widgets --> FeatureTable --> FieldColumn.js file

3. Modify

const A = { useGrouping: !0, maximumFractionDigits: 20 };

const A = { useGrouping: false, maximumFractionDigits: 20 };

4. After update, clear browser cache or use private mode to test the application.

JBH

Having to do a workaround of adding a new field is a bit of a crazy ask when this feels like a no brainer feature.

jfischer91

@TianWen mentioned several years ago that esri was working on this. I wonder where that stands now?

RachelS

3 years on, and still no fix. Really could do with this fixed and I can't change ours to a text field as it's being used in a dashboard for filtering years.

Is there any update on this @jcarlson?

SophieSanders_24

Also experiencing this issue in Experience Builder on Enterprise, e.g showing as;

2,023

2,024

2,025

Similar to this poster the experience builder is not honouring the fields settings

JM_Rail

April 2025 and this is still an issue. Please move this up the priority list, ESRI. Thank you.

CameronLacelle

The only "solution" I've found about this from Esri is this: https://support.esri.com/en-us/knowledge-base/how-to-remove-comma-separators-in-arcgis-experience-bui-000029996

They basically just say to create a brand new field in your data that is a text field and populate it with your numeric values from your numerical field. Not sure about others but this is certainly not a viable solution from my organization's end. This is a poor excuse for a technical solution/workaround for an issue where all you need is a setting in a widget or a dataset to turn off comma separators. By default these should be off anyways. We are experiencing this problem with our Civic Addresses in our applications where users pushing data to a table widget will see fields like "Street Number" displayed with a column so 1234 Fake Street would show up as 1,234.

A REAL solution needs to be implemented that does not involve poor data design.

eleanor_ME

Having a similar issue - at the moment the thousands separator settings in the web map are being honoured in the Experience Builder tables, but the significant digits settings are not. When will there be a fix for this?

Gerald_Farrell

Change the field to text in webmap

JordonHenderson

Still showing thousand separators. Any resolve to this issue? It should be fairly straightforward.

ChristopherRobinsonEdu

Agreed. Would be wonderful for ID's to not have commas. I understand you have to prioritize enhancements and all but usually you knock out the low hanging fruit as well. This seems like really low hanging fruit, almost like picking it up off the ground.

Daniela

We are also struggling with this problem! Shouldn't be so hard to implement, no?

AprilJohnson2

Still waiting for a solution on this ESRI!

Krocha

It is still under review since May 25, 2022. It is frustrating having to use numbers in a string field.

KKelechenyi

Honestly, I'm stunned that this is still not solved. Hoping Esri enables this widget to use custom settings sooner than later.

CaseyRandolph

I am interested in this feature, as well. We recently rolled out an experience that includes a table with a document number. The comma is getting passed through to Survey123 and we are having to remove it through Python when the survey is processed.

jfischer91

I'm also very interested in this functionality! If you have an ArcGIS Idea post for it, please link so I can upvote.

CherieBryant

The text widget also does not honor the MapView number formatting.

Andrus_Nicholas

Issue appears to persist through February 2024 update.

RobertAnderson3

Any updates on this @TianWen ?

SerjStol

Thanks, your code change looks like a neat way to fix this in an ExB Developer Edition, however, we are using ArcGIS Online built in Experience Builder so its not possible to make a code change and we are not switching to Dev Edition any time soon.

VenkataSrikanthDasari

Here is the screenshot for the Experience Builder - Table widget uses ArcGIS Portal. @SerjStol

SerjStol

I can confirm this setting is still NOT honored in ExB within AGOL after the latest October release. The thousands separator option toggle works fine in the Attribute Table within Map Viewer, but does not affect Table Widget in the Experience Builder.

VenkataSrikanthDasari

Hello GIS Developers,

@KaraUtter2 @BrianEaster @Adam_Bourque @CalebAnderson @jcarlson @TianWen @ShefaliVerma_afsc @JoshTownsend @d-slet @AW_Grove @CristianGraf @AaronKoelker

After spending one long week I try to understand the API code and figured out a solution.. Esri didn't implement the field formatting but we can implement using a small code modification.

1. Download the JavaScript API from this link and ArcGIS Javascript API and host the API in your web server (I placed ArcGIS JavaScript API beside to the actual application)

2. Navigate to 4.23 --> Esri --> widgets --> FeatureTable --> FieldColumn.js file and search for the below line of code and usually it exists in the declarations section (line 7 in 4.23)

M=A.convertNumberFormatToIntlOptions({digitSeparator:!0,places:null})

3. Just replace !0 with 0 and that's it. It worked for me like a charm.

M=A.convertNumberFormatToIntlOptions({digitSeparator:0,places:null})

4. Now I don't see comma in Integer, Float and Decimal datatype columns.

Note: Use this URL https://js.arcgis.com/4.23/ locally while building the custom widgets in the client folder. Replace the URL https://js.arcgis.com/4.23/ with JS API deployed URL https://domainname.com/4.23 in the client folder in all the files. Build the package and deploy it.

Happy and Enjoy coding 😎

- Srikanth Dasari

https://www.linkedin.com/in/srikanth-dasari-0526/

ShefaliVerma_afsc

I still can't format the fields in the Table widget.

KaraUtter2

Here we are in October 2023 and we still have this issue. I have formatted the number values in both the web map and visualization tab of the feature layer itself and still the table widget will not honor the formatting for anything, including Dates, Integers, Doubles, etc. This is very frustrating.

Adam_Bourque

Agreed, this is still unfortunately the case. It is disappointing as we want to use experience builder for replacement of web app builder yet this seems to be the one major hold out as it is a pain to have to format every time for exports which is main purpose of web app / experience builder.

BrianEaster

It seems that as of 27 September 2023 the table still is not honoring the settings of the layer in the attribute table widget. I was searching for a solution and found this.

The pop ups are and map widgets in Experience Builder all honor the settings properly. Only the attribute table has a thousand separator and the time in a date field showing.

AaronKoelker

Still seeing this issue. I'm assuming the planned fix never made it?

CristianGraf

Have something similar... with a bonus problem!

When exporting a CSV on the export tool, we have some issues on the CSV. As some people are entering commas (,), well colums and lines are a total mess on Excel.

Any ideas how to change the separator on ExBuilder? On the REST?

Thank you! for any help or work around!!!

AW_Grove

I'm still seeing this issue too.

d-slet

I'm utilizing Enterprise Builder in AGOL and we still are experiencing this issue. I tell you this because Enterprise releases generally follow AGOL and it has yet to have been implemented in AGOL. Maybe and ESRI rep can chime in but I have not found a resolution to this issue.

Take care.

JoshTownsend

@TianWen can you provide an update on this enhancement? Thousand seperators are still showing in enterprise Experience Builder 10.9.1 atleast.

CalebAnderson

Thanks @TianWen, looking forward to it

TianWen

This is actually what we are implementing recently and the table will be able to honor the thousand separator (and other settings) soon.

jcarlson

What version of EB are you using? And is your datasource being referenced by the table directly, or is it a view? In older versions of EB, data source views would ignore field-level formatting options of the original data source.

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.