Configure multilingual business data

Before you begin

• The enterprise has the Multiple Languages product enabled. Data-level multiple-language support is generally available. Every production enterprise can enable it for supported objects and fields without requesting a rollout.
• Your account has the Data Translation Settings management permission, can access Setup > Internationalization > Data Translation Settings, and can configure or maintain data for the target object.
• Identify only the fields that must vary by viewer language. After enablement, each record still requires values in each language; the system does not create business translations automatically.

Supported scope

• Custom objects: Single-line text and multi-line text fields.
• Built-in objects: Use the fields available on the Data Translation Settings page. Current documentation explicitly identifies selected name, code, or notes fields on Opportunity 2.0, Account Pool, Lead Pool, Sales Lead, Account, Product, Product Category, Work Order, Device, and other objects.

Enable objects and fields

1. Go to Setup > Internationalization > Data Translation Settings.
2. Select or add the target object.
3. Select the text fields that require multiple languages and save.
4. Return to the object’s create or edit page and check for the multiple-language entry point beside each enabled field.

Maintain one record

1. Create or edit the target record.
2. Open the multiple-language entry point beside an enabled field.
3. Enter values for the languages enabled by the enterprise and save the record.
4. View the detail and list pages with accounts using different languages and confirm the displayed values.

Populate historical data in bulk

1. On the object’s user-facing page, select Import > Update Existing Data.
2. Match existing records by Primary Attribute or Unique ID, and download the current template.
3. Keep the columns used to match records and enter the target-language field values. You can remove ordinary fields that do not need to be updated.
4. Upload the file, check field mapping, and select Start Import.
5. Review the success and failure counts and failure reasons. Sample the original and translated values.

[!WARNING] An update import changes existing business data. Export a sample for reference and verify Primary Attribute or Unique ID matching with a small record set before production use.

Validate and troubleshoot

1. Create a test record with a default value and at least one target-language value.
2. Check the list, detail, create, and edit pages using accounts with the default and target languages.
3. Search for the target-language value in that language. Then search for the default value and confirm the expected search behavior.
4. If the multiple-language entry point is missing, check the Multiple Languages product, Data Translation Settings permission, and whether the object and field were enabled and saved. Do not troubleshoot a data-level language rollout.
5. If only the default value appears, confirm that the record has a saved value for the current language.
6. If update import fails, verify the Primary Attribute or Unique ID, target-language columns, and field mapping. Correct failed samples before expanding the import.

Related topics

• Translate object and field names
• Multilingual content and maintenance entry points