*This post is locked for comments
Thanks David!
Here are my findings:
- CRM translates the out of the box field’s labels for us, but we will have to provide and upload translation for all custom fields.
- Each user can select preferred language and the CRM will translate the UI accordingly.
- The user can input in the selected language only. In other words, we have one field behind the sense and we can store data in one language. For example, we have one field for “Contact Name”, So if we store “Yaqub” in it, the CRM won’t translate it to French or Arabic for us.
- Reports will display whatever we have stored.
- We will also require taking care of the messages/notifications we are displaying to the CRM user and we will require to show the error message in their selected language, for the out of the box error messages/notifications, CRM will do it for us, but we will have to take care of our custom validation/error messages.
- There are no character set limitations - CRM uses Unicode throughout.
- If we want to store data in multiple languages, then one approach is to have multiple fields for same attribute. For example, we can have “Contact Name (In English)”, “Contact Name (In French)” and “Contact Name (In Arabic)”.
You will need to translate the labels and option set values. You can export these from CRM, translate them, then reimport. These labels are solution-aware, so you can include them in a solution when deploying between organisations
Data can be entered in any language. Reporting will be across all data, unless you specifically include a field to indicate which language is being used
There are no character set limitations - CRM uses Unicode throughout
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,253 Super User 2024 Season 2
Martin Dráb 230,188 Most Valuable Professional
nmaenpaa 101,156