We're a Swedish partner, with a few native English speakers. As we started to roll out NAV 2016 for some new clients, we started to set it up on all workstations here. The RTC works fine for all users. However, the machines where the primary OS language is Swedish cannot open the development environment. The moment they do, they get the attached error message, which reads:
"ShortCutKey kan inte vara Ctrl+Skift+N. Ange en giltig tangentkombination, t.ex. Ctrl+F5"
(Roughly: "ShoutCutKey cannot be Ctrl+Skift+N. Enter a valid keyboard shortcut, for example Ctrl+F5")
Then the development environment crashes.
If we run finsql with the command line "langid=ENU", it does not help. If we try "useoldeditor=ja", that does not help.
This can be reproduced on the English OS machines by simply setting the language to SVE. The only way to reopen the Development Environment on those machines after the language change is to delete the ZUP file to force it back to English. I have also tested. If I create a fin.zup on an English OS machine with the DevEnviron, then transplant the zup to the Swedish computers, the development environment will open.
Sharing this here in case other people have this issue.
HERE is a NAV2016 zup file that ONLY has the correct settings for opening in English (no license, databases, etc).
I'm also curious if anyone else uses 2016 in a non ENU environment, seeing if this is a SVE specific issue or all non ENU.
Comments
"Errors using the development environment in some languages"
"If you change the language in the development environment to languages other than English (United States), you may see error messages, for example if you use certain keyboard shortcuts or similar. We have identified a very small number of issues and will include fixes in the next cumulative update."
"Delete the fin.zup file and then, in the development environment, change the language to English (United States). The default location of the fin.zup file is C:\users\<user name>\AppData\Roaming."
"In general, we recommend that you set the language to English (United States) when you work in the development environment, especially if you work in a multilanguage-enabled solution."
Source:
https://mbs.microsoft.com/Files/customer/NAV/Downloads/Productrelease/ReleaseNotesForMicrosoftDynamicsNAV2016.htm
FYI to anyone running into this. If your OS is in non-English, and you delete the ZUP file, then try to open it - you can't, which means you can't change the language to English even if you want to. The langid parameter is also not working to override that.
Hopefully that ENU zup file will save some folks some folks some trouble.
CEO, Spare Brained Ideas, Göteborg, Sweden
New (April 2021) Getting Started with Microsoft Dynamics 365 Business Central Book Available: "Your First 20 Hours with Business Central"