Currency Locale Troubleshooting - Support and Troubleshooting

Currency Locale Troubleshooting Issue There have been many open issues with currency. This article will help with the initial investigation.

How locale is determined:

Locale can be defined as user level or at system level.

Precedence order is –

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

Locale determines: Currency Formatting and Number Formatting

https://docs.servicenow.com/csh?topicname=locales.html&version=latest

We're reliant on the underlying JVM locale and formatting code for actual rendering of things in the appropriate locale.

Java supported locales:

https://www.oracle.com/technetwork/java/javase/javase7locales-334809.html

Example:

When glide.system.locale property is set to any valid locale, for example, "de.CH", system generates country code as "System (CH)". Customers can add "CH" in country code sys_choice list.

Expected results:

Setting User's country code to "System (CH)" and language to "de", will evaluate correct user locale "de_CH"

Unexpected results:

If user's language is set to anything else, for example, "English" which evaluate to an invalid locale "en_CH"

Some browsers (like firefox) will send in a browser locale with a language code, but among other things, a language code with no country code gives the java currency formatter class fits (illegal argument exceptions), So if the browser locale lacks a country or language code, the system will use the system default locale and the user will see inconsistent results.

Same case will work fine with safari as browser handles locale correctly. But if the user has an invalid locale, chrome ignores it https://developer.chrome.com/extensions/i18n and the user will not get expected results.

In case of unexpected results, below settings should be checked:

User language and country code should be a valid locale. glide.system.locale should be valid locale. If glide.i18n.languages plugin is installed, check for a language code synonym in the case where we have had to use an alternate language code. Locale is not necessarily the same thing as language as. For example, Quebequous and Frenchmen both speak French , but use different number formatting rules. The value of "glide.i18n.language.synonym." + user language (2 character) and country code should be a valid locale, i.e., a locale listed at the Java supported locales URL above .

Another helpful article to refer to while using different currencies on an instance (KB0596448)

https://support.servicenow.com/kb_view.do?sys_kb_id=cf56a163dbc193c43882fb651f96195a