Setup Translations
Choose the right translation method for the UI, picklist values, field labels, and document content.
Last updated
Was this helpful?
⌘Ctrlk
Choose the right translation method for the UI, picklist values, field labels, and document content.
Use this section to set up translated S-Docs experiences and translated document output.
Start with the guide that matches your goal.
S-Docs translation has two layers.
UI translation changes the S-Docs screens your users click through.
Document translation changes the content inside generated output.
Use the document method that matches the value source.
Use translate="true" for Salesforce-translated picklists and labels.
Use toLabel() for picklist values returned by direct SOQL related lists.
Use the UI translation guides.
That covers pages like Generate Documents, Send Email, and Attach Files.
Use Salesforce Translation Workbench.
Example use cases:
picklist field values
standard field labels
translated custom field labels
Use toLabel() inside the SOQL query.
That tells Salesforce to return the translated picklist label instead of the raw API value.
Before testing translations, confirm these basics:
Translation Workbench is enabled when needed
The template Language field is configured for Salesforce language codes
Your test user is using the expected Salesforce language
The translated field or value exists in the right system
If you are starting fresh:
Translate the S-Docs UI if users need a localized generation flow.
Translate document content with Translation Workbench.
Add toLabel() for translated picklist values in direct SOQL related lists.
Test one language with one template before scaling out.
Last updated
Was this helpful?
Was this helpful?