<aside>

Description

Take translations out of the Metadata Translator, work on them elsewhere, and bring them back in. Use CSV or XLS for spreadsheet review, or Salesforce XLIFF to publish straight into Translation Workbench.

</aside>

Prerequisites

• Metadata has been retrieved on the connected environment (see Retrieve Metadata).
• Metadata has been translated in SimpleTranslate (see Translate Metadata).
• For Salesforce XLIFF: Translation Workbench enabled, every target language added with an active translator, and email notifications set up. Salesforce rejects a file for any language missing one of these, and the export arrives by email rather than as a download.

Available formats

Steps

Import a file

1. Open the Metadata Translator section, then the export and import dialog from the toolbar, and switch to the import tab.
2. Upload the file. .xlf and .xliff are read as Salesforce XLIFF; CSV and XLS are also accepted.
3. For a spreadsheet, fill in the Translated Value columns first and leave the identifier columns on the left alone, since rows are matched on those.
4. Check the summary. Nothing is written yet. It shows what would change, what already matches, and what is skipped. Importing the same file twice changes nothing the second time.
5. Click Apply. This overwrites the existing translated values, so check the counts first. Imported values then join the normal translation and review flow (see Translate Metadata).

Export translations

1. Pick your target languages. Only these go into the file.
2. To narrow the export, filter by metadata type or select individual rows (see Filter Metadata).
3. Open the export and import dialog from the toolbar and select the file format.
4. Choose whether to export all translations or only the rows you selected.
5. Click Export. CSV and XLS download now. Salesforce XLIFF is emailed when ready, usually a minute or two, and contains only rows that have a translation.

Publish a Salesforce XLIFF file in Salesforce

1. Unzip the archive. There is one file per language, named after the language code.
2. In Salesforce, open Setup and go to Translation Workbench, then Import.
3. Upload one language file at a time.
4. Read the confirmation email. Salesforce applies every valid row and lists the ones it rejected, so a single bad entry costs you that translation rather than the whole file.

Good to know

• Spreadsheets carry an Org Value column, what Salesforce has today, and a Translated Value column per language. Only Translated Value is read on import.
• Untranslated rows are left out of a Salesforce XLIFF file, because Salesforce rejects a file containing an entry with no translation.
• Each file updates one language, taken from the file header rather than the filename.

Troubleshooting

• Salesforce XLIFF is missing from the format list. No org credential is connected to this environment.
• The export never arrived. Check email notifications for your organization, then open the log entry for the export.
• The file is shorter than expected. Those rows either have no translation for the language you picked, or the environment has not been retrieved since this feature shipped. A fresh retrieve fixes the second.
• Rows come back as not found after a spreadsheet import. The identifier columns were edited, reordered or removed. Export a fresh file and redo your edits on that copy.
• Salesforce reports a maximum character limit error. The translation is longer than that field allows. Shorten it and export again.
• Nothing matched on import. The file came from a different environment. Identifiers differ between orgs.

<aside>

Quick View

End User Documentation

• SimpleTranslate
• SimpleT AI
• Organization </aside>