Keep these tips in mind when creating custom labels, working with translators, and maintaining translations.
Required Editions
| Metadata translation available in: Salesforce Classic and Lightning Experience |
| Data translation available in: Lightning Experience |
| Available in: Professional, Enterprise, Performance, Unlimited, and Developer Editions |
| Data translation applies to: B2B Commerce |
- Salesforce assumes that all customizations are entered in the Salesforce org’s default language. We recommend that global administrators work together in the org’s default language.
- Salesforce recommends the XML Localization Interchange File Format (.xlf) for translation files.
- When creating a custom report type for translation into multiple languages via Translation Workbench, set your personal language to match your org’s default language. Setting a language ensures that translated words display in the correct language for translators.
- Advise users customizing reports or list views to use filter criteria values in
their personal language. However, if they use the
starts withorcontainscontains operators, advise them to choose the language of the filter criteria values they entered. - If you installed a managed package that includes translations, those translated values appear to users regardless of whether the language is active on the Translation Language Settings Setup page. To override metadata translations delivered by a managed package for custom objects, see Override Translations in Second-Generation Managed Packages and Unlocked Packages.
- Let translators know which languages they’re responsible for translating.
- Notify all translators when you add new translated components to your org. For best results, have your translators check their translations frequently, and be sure to notify them when changes occur.
- Periodically review outdated translations by exporting your translations. To generate a list of all the translatable customizations and the associated Out of Date states, use the Outdated and Untranslated export type or Bilingual export type.
- If you have more than 25 navigation menu items open, use the scroll bar to find the navigation tools at the bottom of the window to navigate between pages.
- You can create up to 1,000 custom objects that include the picklist field. If you receive an error that your collection exceeded this limit, reduce the number of custom objects with a picklist field to 999 or fewer or export the translation files.
- You can view up to 10,000 records in Translation Workbench. To view more than 10,000 records, use translation import and export.