Hi James,
No problem, I've checked the ENH-000120747 entry with my Esri support.
But they were not sure it meant what we wish for.
Does "Support the ability for user to disable Regional format for a thousands separator.".
mean the users won't be allowed to type the thousands separator?
Also, looking at the docs of the early adopter website, I discovered
I can program custom javascript functions. That's cool.
Using it, there's a workaround for sort of disabling the thousands separator.
Not very convenient, but it seems to work...
Here's the XLSForm I've created, with 2 fields:
//Auxiliary field, for user input
type: text
name: decimal_text
bind::esriFieldType: null
constraint: regex(., '^[0-9]+[.,]?[0-9]*$')
//Field for actually storing the value
type: calculate
name: decimal_number
bind::esri:fieldType: esriFieldTypeDouble
bind::type: decimal
calculation: pulldata("@javascript", "to_decimal.js", "to_decimal", ${decimal_text})
Javascript file, to_decimal.js:
function to_decimal(x){
return parseFloat(x.replace(",","."))
}
Is there an easier or better way to do this?