WS on a multilanguage environment

WS on a multilanguage environment

Rate This
  • Comments 0

After collecting Partner's and Customer's feedback about the changes introduced on build 32558 regarding Web Services (remember), DEV team has decided to introduce a way of avoiding them if desired.

 In order to do so a new feature has been introduced on build 33137 (KB Article 2667345), this new feature allows you to add a new key to CustomSettings.Config file that will revert changes performed on build 32558 and therefore language used or WS will be the one that is logged for the calling user identity in the User Personalization Table, if any.

 This is the key that has to be manually added (Meaning is not present on the Config File)to the NAV Server configuration file:

 

<!--

The default Culture in which SOAP Web Service calls are run.

Supported values

"false" (the default)
ensuring Web Services are running on a fixed culture,

"true" use the Culture
that is logged for the calling user identity in the User Personalization Table,
if any -->

 <add
key="ServicesCultureDefaultUserPersonalization"
value="false"/>

 

If we select false then everything keeps the same and what was applied on build 32558 remains, thus you will see all error messages in English and culture (Decimals, dates, etc.) will work with EN-US values.

However if we set the key to true then the Culture that is logged for the calling user identity in the User Personalization Table (if any) will apply.

 KB article for this Hotfix is placed on the next link:

https://mbs2.microsoft.com/Knowledgebase/KBDisplay.aspx?scid=kb;EN-US;2667345

Please be aware that this change (32558 build one) was introduced to break the dependency of WS language to RTC one so applying this HF and setting this key to true will enable that dependency back again which could be buggy on  mltilanguage environments where different languages are present for different NAV clients (RTC, WS, Classic Client). 

What was introduced on build 32558 guaranteed that WS will always take EN-US as default language building a more predictable scenario.

 

Anyhow and following your feedback we have asked DEV for a way to let NAV administrators to make this decision and this is the answer to this.

 

 I hope you find this helpful.

 Best regards

 

Diego García Álvarez

Dynamics NAV Senior Support Engineer 

Leave a Comment
  • Please add 7 and 3 and type the answer here:
  • Post