Impact of changing glide.system.locale in production system

[sreedharkaliset]

Hi,

what is the impact of changing glide.system.locale in a live production system.

I want single currency to be used for calculations and so I already modified the following properties.

glide.i18n.single_currency

glide.i18n.single_currency.code

com.glide.financial_management.currency_code

But i still see some fields displaying values in USD and not the currency used in single currency code.

There are some projects ,programs and portfolios for which resource and cost planning is done. What will be the impact on these records.

Please let me know the impact if i change this property.

[Atul Kumar2]

Hi Sreedhar,

NOTE: Do not change this value once a system has gone into production. If a user's locale must be changed, update the "Country code" field on the user record.

The value of this property determines the system's default currency into which all prices are automatically converted before other sums or conversions are performed.

Changing this property after any price or currency fields have been given a value (for Service Catalog items, Assets, Project Tasks, etc.) may result in improper conversion or prices that sum incorrectly.

Hope this helps.

Regards,

Atul Kumar

[helmutpfeiler]

Hi Sreedhar,

did you find a solution for your question? I'm also seeing USD values in some PPM fields (I have changed the same properties than you did).

Thanks

Helmut

[sreedharkaliset]

Hi Helmut,

I modified the locale property to en.AU and there is no much impact as most of the tables do not have records in my system. Once modified, calculation is done in AUD.

Impact of changing the first 3 properties but not locale will create records in fx_currency_instance table with currency as AUD and reference currency as USD. Once the locale property is modified, both will be in AUD.

Regards,

Sreedhar

[seberly]

We are thinking about changing the glide.system.locale property as well because we believe that the browser's locale is being used per this article (snippet below).   In our case the user's record is missing a value for preferred_language ("Language") and there is no value for the property glide.system.locale so we are thinking that the browser's locale is what SN has to be using.   The behavior isn't consistent throughout our global user base though.   We have someone in Russia where we believe the browser's locale is being used because a save results in RUB, but for a user in the UK their updates result in USD.   I would expect GBP instead.

The user locale is determined by the following, in order of consideration.
User record in which both country and language are specified.
System locale set using the property glide.system.locale.
Browser locale.