Share via

Translate product names and properties into multiple languages

  • Article

 

Applies To: Dynamics 365 (online), Dynamics 365 (on-premises), Dynamics CRM 2013, Dynamics CRM 2015, Dynamics CRM Online, Dynamics CRM 2016

When you sell your products in different regions, it is important that you translate significant product details into multiple languages. Help sales agents find things they need easily by making all the relevant details like cross-sell or upsell suggestions, or properties, available to them in their preferred language.

Important

This feature was introduced in CRM Online 2015 Update and CRM 2015 (on-premises).
Interested in getting this feature? Find your Dynamics 365 administrator or support person.

On this page

Down arrow button Step 1: Export data for translation

Down arrow button Step 2: Import translated data

Down arrow button Selection of language in different scenarios

Step 1: Export data for translation

  1. Make sure that you have one of the following security roles or equivalent permissions: System Administrator, System Customizer, Sales Manager, Vice President of Sales, Vice President of Marketing, or CEO-Business Manager.

    Check your security role

    • Follow the steps in View your user profile.

    • Don’t have the correct permissions? Contact your system administrator.

  2. Go to Settings > Data Management.

  3. Click Export Field Translations.

  4. In the Export Field Translations dialog box, click OK.

    All product fields that are marked as localizable by default will be exported. Your internal developers can mark the fields as localizable. More information: Work with localizable attributes.

  5. Save the .zip file to your local computer.

    Exported text is saved as a compressed file that contains a CrmFieldTranslations.xml that you can open by using Microsoft Excel. You can send this file to a linguistic expert, translation agency, or localization firm.

Step 2: Import translated data

When you get the localized data back from translation, import it into Microsoft Dynamics 365.

Important

It is important to provision the language packs first. If you import translated values for languages that aren’t provisioned in the organization, they’ll be discarded. More information:     Install or upgrade Language Packs for Microsoft Dynamics CRM

  1. Make sure that you have the Manager, Vice President, CEO-Business Manager, System Administrator, or System Customizer security role or equivalent permissions.

    Check your security role

    • Follow the steps in View your user profile.

    • Don’t have the correct permissions? Contact your system administrator.

  2. Go to Settings > Data Management.

  3. Click Import Field Translations.

  4. In the Field Translation Import Jobs page, on the Action toolbar, click Import Field Translations.

  5. In the Import Translated Text dialog box, click Browse, and select the file that you’ve received from your translation agency.

  6. Click Import.

    This starts the import job. You can check the status to see if the import has succeeded or failed.

After you’ve imported the translated text, users in your organization will see the data in their preferred language. If a value for the preferred language does not exist, the results will be shown in the user’s base language.

Selection of language in different scenarios

This section explains how the duplicate detection and workflow logic affect translation in Microsoft Dynamics 365:

  • Calculated fields logic, including conditional clauses, uses only the base language. The behavior of workflows and portable business logic is similar to Microsoft Dynamics 365 SDK. The label for the user’s preferred language (user interface language) is used if present. Otherwise, the base language is used.

  • When a record is created or updated, duplicates are detected from the localizable fields (attributes) that are in the base language. Creating or updating a localizable field is not applicable in a non-base language.

  • During data import,

    • For updating or creating records through import, when import is executed in base language, only the labels in the base language are used for duplication detection.

    • When import is executed in non-base language, import fails because update can’t be performed in a non-base language.

  • When you run duplicate detection in the base language, only the base language is used in conditional clauses.

  • When you run duplicate detection job in the preferred language, label in the preferred language is used first. When preferred language is not available, it uses the base language.

See Also

Set up a product catalog: Walkthrough
Set up duplicate detection rules to keep your data clean