In a globally run business where employees and customers are spread across the globe, it is essential to have a multi-language support system to avoid any language barrier. The CRM understands this and thus provides an option to choose a preferred language for your CRM. In the CRM, when you set a preferred language, it applies to the modules, custom fields and picklist values too. This can pose a barrier if your organisation operates in different countries.
Say for instance, your organisation has its headquarters in Germany with branches in US, Europe and Japan. Since you mainly operate from Germany your preferred language in CRM would be German. However, the sales personnel from other branches would find it incomprehensible and will prefer their native language. Translations, in the CRM, addresses this issue and lets you translate the fields and picklist values to an individual's preferred language.
To begin translating language files, follow the steps below:
Step 1. Switch On the Translation Settings
The first step is to turn on the translations settings. Before your begin, make sure you are logged in to your CRM account with Administrative privileges.
Step 2. Add Language
The second step is to add the language into your CRM account. In the CRM, you can select a language from 24 pre-defined list of languages. When you add a language, a file is added that consists of a unique language code to identify the language. The file lists all the picklist values and custom fields in the default language of your CRM account. One by one, you can add as many languages as you require and use the language files to translate them.
Step 3. Export Language Files
Once you add the languages, the next step is to export the language file that you want to translate for your organisation. An export file contains all the picklist values and the custom fields that need to be translated. You can choose to export individual file or export all the language files at once. Once the language file is exported, you can translate the picklist values and custom fields in an export file either yourself or outsource to a vendor.
Step 4. Import Translated Language Files
After exporting the language file, you can either translate the fields yourself or outsource it to a translator. Please ensure that the format of the exported file is not changed as it might affect the translation in the CRM. Once you have finished translating the fields, you must import the translated file into CRM.
To translate a language and add it in CRM
A complete list of files that are imported till date is available under the Language Import History. The imported language files are arranged in a chronological order with the most recent ones on top.
To view language import history
There can be chances when you have already translated a language and later added new custom fields or picklist values in a module. In such case, you can choose to export the translated file and just translate the new fields and import the language file back into your CRM account. This will help you avoid translating all the fields again. Alternatively, you can export an untranslated language file and translate all the fields.
To export a translated file
In case you have imported a wrong language file, or if you do not wish to use the file that is imported into CRM, you can revert the action. Reverting it will undo the translations in the CRM that were done using the file.
To revoke an imported language
There are two options to deactivate the translation.
To deactivate a language
To deactivate translation settings
A picklist field value that is translated in various languages may not be functional when any one of the languages' value is used to define conditional checks of custom functions, parameters of web hooks, formula fields, merge fields of email template or task subject etc.
For example, if one of the option "Advertisement" in a picklist field "Lead Source" is translated in 10 different languages, then the function will not work with the same value "Advertisement" for users who use different language in CRM. To address this issue we have brought in Reference Values. Each picklist field is represented by a reference value, which is common in every language. While defining any of the above functions that involve a picklist field, the user must use only the reference values for the function to occur.
To use reference values