Can the decimal separator be independent of the user language?

Nadira
Tera Contributor

Hello,

 

In our environment the glide.system.locale is nl.NL, the country code of the users is 'NL'.

The users can choose for preferred language 'Dutch' or 'English'.

What we have recently seen is that if the user's preferred language is set to English, the decimal separator becomes a dot (.).

This is not what we want, we want the decimal separator to be a comma (,) for all users, independent of the preferred language.

Does anyone know a way to make this happen?

 

Kind regards, Nadira

3 REPLIES 3

Ankur Bawiskar
Tera Patron
Tera Patron

@Nadira 

it's a default behavior.

the decimal separator is controlled by user's locale and not language.

Check this

Why instead of a dot a comma (,) appears as the decimal separator when the instance locale is set to... 

Some browsers use a comma (,) instead of a period (.) as decimal separator. 

If my response helped please mark it correct and close the thread so that it benefits future readers.

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

Nadira
Tera Contributor

Hello Ankur,

 

Thanks for your answer.

I have also created a support case at ServiceNow and the answer was:

 

The precedence order is –
Locale as defined by language and country code in the user record (language and country both must be specified in the user record. User locale is a combination of language + country code.
Locale as defined by language code only in the user record (use the default locale for language)
Locale as defined by glide.system.locale system property
Locale as defined by your browser

 

However. we want the comma (,) to be the decimal separator in the following situations:

1. glide.system.locale = 'nl.NL', User Country = 'NL' and User preferred language = 'English'

2. glide.system.locale = 'nl.NL', User Country = 'NL' and User preferred language = 'Dutch'

But instead, due to the precedence order of ServiceNow we get a dot (.) to be the decimal separator in situation 1.

 

Does anyone know a workaround for this?

@Nadira 

I doubt this is feasible due to the way how platform takes the precedence.

Did you ask ServiceNow in that case itself?

If my response helped please mark it correct and close the thread so that it benefits future readers.

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader