You’re offline. This is a read only version of the page.
15
We have decided to implement D365 Finance & Operations in a single language. After a successful implementation, local divisions can choose their language for daily work .
My priority today is to communicate the WHY to my end users.
It’s very normal, end users are concerned about not being able to communicate. I want to manage their expectations from the very beginning of this project.
Do you have up-to-date success stories, documentation, case studies, reference material to support single language is better for the implementation? Suggested articles form the forum are 7-10 years old.
Hi Debbie,
When you have made a decision, I do think you considered various pros and cons carefully. So, you should have the reasons already. I do think the information from 7-10 years old might be indeed outdated. E.g., technology has changed. If it was because of translation time of customizations, then there is now a very good and quite accurate Dynamics Translation service available which can do brilliant quick translations for languages supported by Microsoft out of the box. For helpdesk, it is quite easy to switch the language temporary to make screenshots of a problem in different languages: dynamicspedia.com/.../
As you notice, I do think there are less valid reasons compared to 10 years ago. Also there are requirements in various countries to do reporting in the local language.
A very good reason is to mention that training can't be done in all languages. Using the system for that reason initially in a global language would be beneficial for learning and performing exercises. Although I mentioned that translations are quite quick and good, you might want to focus on quick go live and do translations in a second phase.
You can also search for more information on the internet as this is more a project management question in general which is not restricted to Microsoft Dynamics only.
Share
Report
All responses (
Answers (
