how to use the useThousandsSeparator property

Question

Been reading the documentation under PopUpFieldInfo for the Flex API, and it seems like I should write the popupconfig file like this: But this doesn't take out the comma in the number field in the pop up window. Does anyone know the right syntax to use to achieve this?

SveinungRaheim · Answer

I have a problem with the thousand separator. I have an integer-field (ID-field) in this rest-service (http://askeladden_wms.ra.no/ArcGIS/rest/services/Askeladden/Kulturminner_ReadOnly/MapServer/1) which I want to include in a rather complex url to be able to open an external database with information about features in the service: http://www.kulturminnesok.no/content/search?search=9373&searchtype=1&county=&municipality=&culture_environment=0&man_em_dating=0&category=&em_art1=&em_category=&em_date=&conservation=&em_old_function=&submit=S%C3%B8k I have created a custom pop-up that looks like this: http://www.kulturminnesok.no/content/search?search={LokalitetID}&searchtype=1&county=&municipality=&culture_environment=0&man_em_dating=0&category=&em_art1=&em_category=&em_date=&conservation=&em_old_function=&submit=S%C3%B8k The important field heire is {LokalitetID}. This is returned in the flex-viewer pop-up (standard pop up, version3.5) with the thousand separator ",". That means, instead of "113224" it returns "113,224". This makes the URL invalid. By chance or maybe pure luck, I found a workaround. In the xml-file for the spesific pop-up, I had to add theese two lines: The whole xml-file looks like this: {Navn}_1 Faktaark - kulturminnesøk]]> false false I dont know why the flexviewer add "use utc" and "dateformat", but it seems like you have to specify this value: usethousandsseparator="false" It looks like "true" is the default value, a bit confusing that in the builder, you have an option to check it on. Anyway, this looks like a solution for me.

BjornSvensson · Answer

This will be fixed in the next release - 2.3.1 - which is planned for release later this week.  Also the property name will be spelled with two s's to be consistent with the API.

RobertScheitlin__GISP · Answer

Cameron,

I am not sure about the priority of getting an update out but I would say it might come quickly as there is a MAJOR bug in the API that prevents snapping and editing when the map is any other wkid than webmercator or geographic.

The reason (partially) for the usethousandseparator being different in the viewer than in the API is that esri uses a standard of having all attributes in the config files lowercase for consistancy. As to why they left out the "s" is anyone's best guess.