Recently I did a multilingual Microsoft Dynamics 365 Customer Engagement implementation, which I thought would be easy given that if you search for how to translate Dynamics crm, it give a simple three step process.
- 1. Export translation ,
- 2. Update translation and
- 3. Important Translation .
Sound easy ? I also thought that too until I found myself in a position where I need to keep my laptop open after working hours ( for me it’s a very big thing )
So here are few lessons I learnt during this implementation and how you can avoid those small bumps in the road.
Be reasonable with the efforts
If you are not considering efforts of language translation , you should and it should be well defined. Always bring a QA to review the translation and add his efforts too, keep in mind you would need to take long session with the native translator ( in general it is the customer ) , add those long session efforts in your budget. Keep at least 3 full day for translation 2 full day for customer review and 1 full day for QA. (how you would budget it let me know in comment )
Say No to automatic translation
Try translating something to your native language using automated translator, you’ll understand what I am trying to say. Each language if different ,words and sentences have different meanings given the situation. Trust a native translation for correct word and grammar.
Explain everything to customer
When you have decided to translate make sure you take your time to explain each and every corner of the application and what is the meaning of a view displaying a set of data , meaning of chart , fields , section and other area which user will use every day.
It is absolutely necessary to make sure customer or the translator knows what they are translating. CE is all about one word explanation ( field name ) and it must be precis. Just a simple example
Aunt is a one word but if you want to translate it into hindi you’ll get more than one meaning.
Not everything is translatable
And make sure your customer knows it.Some areas are out of scope for translation and they must be used as is. for example on chart if you are displaying a sum or count of a field it will always appear as Sum (field Name ) , so you cannot rename the entire display name as one word
Later the better
Translation must be done when all your development is finished and now you are moving towards UAT. Otherwise you’ll end up in a cycle of uploading translation file everyday and you’ll spend more than your budgeted time
Make a list and stick to it
Always make sure where the user will lurk around , make a list of all forms and application area where user will interact. make sure your customer gives confirmation. Otherwise it will be a very big task. However This is a very scenario specific choice , I’ll let you chose.
Don’t rely on a tool, I repeat “DON’T”
I have mentioned this before , but it also applicable for the XRMtoolbox’s easy translation plugin , I found it in a hard way that sometime when you upload translation it does not reflect. Always double check what you have uploaded and is it displaying updated translation or not. stick to the out of the box language translation, it’s a bit hard to manage but.. It never fails.
Don’t expect customer to fill translation template
It would be better if you have your own excel which you can take as a reference when you are updating translation xml file. Never give these XML file to customer to fill , its big , boring and confusing. (not even easy translator template )
Do you have some learning to share ? let me know in the comment , I’ll update this blog.
Like it ? Tweet It ,
See the button ? Press It. 😀
Check out the new blog “Lesson I learned during my multilingual crm implementation” , Do you have some thoughts to share ? let me know #mslearn #MsDyn365 #D365 #MSCRMTweet
One Reply to “Lessons I learned during multilingual CRM implementation”
CRM implementation is very challenging. Many companies failed to implement CRM for their sales and marketing departments.