I have a Web AppBuilder application that displays commas in numeric fields that have been configured to not display commas for values larger than 1000. We have also configured any date fields to be displayed as Month, Day, Year format but this does not format in the application as well (2nd image)
We have built a Web AppBuilder Application that uses the Jewel Box theme with the Smart Editor widget added to the left pane. But the values keep displaying with a comma. Second image is from the date field that is not formatting to our selected format.
We are using the developers edition and i am hoping that somebody could help us out by identifying which files need to be adjusted with some code. Similar to Liana Smith's issues
I know it is an old post but just for reference I thought I should reply. This issue is not reproducible in the current version on WAB in ArcGIS Online and Smart Editor widget honors the comma separator settings for the layer.
I am able to reproduce the issue with Smart Editor widget in WAB.
Also, there are some other widgets that still show the comma separator regardless of the layer settings from visualization tab or in web map pop ups. These include:
There is an existing bug requesting to fix this issue.
All the best,
MJ Biazar I am experiencing the same problem in web app builder (a field I have configured within "configure pop-ups" of my web map to not display thousand separator commas is still showing these within the Smart Editor widget in a Web App I have built). Any update on this issue? It seems like I have reproduced the same error as City of Kelowna GIS.
Ryker Garrett After more testing I'm able to reproduce this issue with Smart Editor widget too. It seems like it still shows commas when you select a feature but when you click in the box the edit the values, the comma is gone.
While the bugs are still being reviewed, as a workaround you can create a text field, and calculate values from the integer field to remove the commas in WAB widgets.
This is still an issue more than a year later. Seems like something simple to fix. Why is this not being resolved? Creates confusion for end users resulting in service calls.