Guides
Guides for multilingual Salesforce orgs
How translation and metadata work in Salesforce, step by step. Each guide starts with what Setup and Translation Workbench give you, then shows where a tool like Sextant saves the manual work.
- Where each label is translated
Translating a Salesforce org: where every label is translated
A map of which Setup page translates which label, how to translate many at once, the metadata types behind them, and how to check the result.
- Custom Labels
How to translate Custom Labels in Salesforce
Three ways to translate a Custom Label, how code picks the translation at runtime, the three different length limits, and the retrieve pitfall that catches developers.
- Picklist values
How to translate picklist values in Salesforce
Custom picklists, global value sets and standard picklists each keep their translations in a different place; how SOQL, reports and formulas treat them; and a checklist for a value that will not translate.
- Metadata behind a label
How to find the Salesforce metadata behind text in Lightning
A word on a Lightning page can be a field, a picklist value, a Custom Label, a section or a button. How to tell which, and find its API name in Setup, with a query or from the page itself.
- Missing translations
How to find missing translations in Salesforce
Find untranslated and out-of-date labels systematically: with Translation Workbench's export and grid, on the pages users see, and with a release checklist.
- Compare between orgs
How to compare translations between Salesforce orgs
Sandbox against production, with Translation Workbench's Bilingual export or a Metadata API retrieve and a diff, and what each comparison can and cannot tell you.
- Translation not showing
Why a Salesforce translation is not showing
A saved translation users don't see has a handful of causes, and the component behind the text decides which. A check for each, with its fix.
How these guides are written
Each guide answers its question with Salesforce's own tools first (Setup, Translation Workbench, the Metadata and Tooling APIs), so it is useful whether or not you use Sextant. Where a browser tool shortens a step, the guide says so in a box marked Where Sextant fits, and nowhere else.
The Salesforce steps are checked against Salesforce's own documentation, and each guide says when. What a guide says about Sextant is checked against the current release: the product page lists what it does and where it stops, and the Trust Center what it does with your data.