Learn how to specify valid merge fields in the translation profile using the Object Scheme explorer for flexible translation.

Only valid merge fields or SPECIAL.PPOC in the translation profile can be translated. You can refer to the Object Scheme explorer available on the Edit HTML Template page to specify merge fields that will be translated flexibly. Click the icon at the bottom-left corner of the Edit page to open the explorer.

You need to follow the following rules when specifying the merge field values:

• A valid translatable merge field must be in the object.field format. In the explorer, some items are not displayed in the object names. You need to refer to the annotations to identify the object name. In the below example, because the object name of BillTo is Contact, a valid merge field should start with Contact, such as Contact.AccountId.

• The field type must be String.

• You cannot specify objects or fields that don't exist in the Object Scheme explorer.

• The object position must be a single object. You can refer to the data type annotations in the explorer to identify the correct object name. For example, if you want to translate the ChargeName field on the Invoice Item object, use InvoiceItem.ChargeName in the translation profile.

Note that in the explorer, the display name is InvoiceItems. But the annotation of this item is List of InvoiceItem. You need to use the singular object name InvoiceItem. The below screenshot demonstrates the position of the correct values: