# How To: Create Multilingual Documents

Use template attributes and translated Salesforce values when documents need to match user language settings.

### Problem

You need templates that display values in different languages based on user settings or picklist translations.

### Solution 1: Using Translation Workbench

**Setup Required:**

1. Enable Translation Workbench in Setup.
2. Translate your picklist values.
3. Ensure users have language preferences set.

**In Your Template:**

```
{{!Product2.Color__c translate="true"}}
```

If the user's language is French and `Blue` is translated to `Bleu`:

**Result:** `Bleu`

### Solution 2: Using Substitute in Related Lists

**For German Documents:**

```
<!--{{!
<lineitems>
<listname>opportunitylineitems</listname>
<column>PricebookEntry.Product2.name</column>
<column substitute="true,Ja,false,Nein">IsActive__c</column>
<column substitute="1,Januar,2,Februar,3,März,4,April,5,Mai,6,Juni,7,Juli,8,August,9,September,10,Oktober,11,November,12,Dezember">Month_Number__c</column>
</lineitems>
}}-->
```

### Solution 3: Using SOQL with `toLabel()`

**For Related Lists:**

```
<!--{{!
<LineItemsSOQL>
<class>none</class>
<soql>
SELECT toLabel(Status__c) 
FROM Case 
WHERE AccountId = '{{!Account.Id}}'
</soql>
<column>Status__c</column>
</LineItemsSOQL>
}}-->
```

### Tips

* Translation Workbench follows the user's language automatically.
* `substitute` is useful when Translation Workbench is not available.
* `toLabel()` respects the user's language.
* `format-date` month and day names always stay in English.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.sdocs.com/sdocs/advanced-template-logic/template-attributes/template-attributes-how-to-guides/how-to-create-multilingual-documents.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.