Advanced Template Features

• Larger numbers will still follow the pattern even if they exceed the 4 digits shown in the pattern. Rounding is applied when precision exceeds formatting.
• If you need to include a currency symbol, you can add it just before the merged field. E.g. ${{!Opportunity.amount format-number="#.###"}}

• Patterns are case sensitive. E.g. MM=month while mm=minutes. Reference to available patterns.
• Times are formatted per the database time (GMT).
• Time zones must be written using Java time codes.
• Only Salesforce-supported time zones are accepted.
• Long descriptions (e.g. Month, day of week) are in English. You can use formula fields if needed to meet a specific requirement.

• When this attribute is added, the merge field will display as the checkbox in its current state on the record once the document is generated.
• Currently not supported in DOCX file format

• The output is a series of images that can be used in PDF generation of checks. Only digits and ‘t,’ ’o,' ’a,’ ’d,’ are transformed. Other characters are ignored.
• The number following MICR represents the font width. E.g. MICR="16" will be larger than MICR="8".
• Spacing defaults to 0 if it is not specified. As shown, negative spacing values are allowed. The lower the spacing value, the closer together MICR characters.

• The output is a series of images that can be used in PDF generation of checks. Only digits 0-9 are transformed. Other characters are ignored.
• Spacing defaults to 0 if it is not specified. Negative spacing values are allowed. The lower the spacing value, the closer together OCR characters.

• Using the RTL merge field attribute will transform merge field data only, not static text.
• To apply RTL for both merge fields and static text, use the following style in the template source:

            <rtl>reverse</rtl>

• When using <rtl> tags, there is no need to add the RTL attribute to your merge fields. You can wrap an entire template in <rtl> tags to transform both merge field data and static text.
• Note that <rtl> tags will not work properly with text that breaks across two lines in the generated document. You should use separate <rtl> tags for each line if text breaks across two lines.

• This feature leverages Salesforce toLabel() function within a SOQL query. It is particularly useful for orgs that have Translation Workbench enabled. Translate keyword will cause an error if used on field types that do not support toLabel().
• For related list translations, or lookup fields, you should use direct SOQL query. If you set the class to "none" then only the data is returned – not in a table format. Here is an example usage from the S-Docs template source:

            <!--{{!
            <LineItemsSOQL>
            <class>none</class>
            <soql>Select tolabel(color__c) From product2 where id='{!ObjectID15}' and toLabel(color__c) =’BLEU’</soql>
            <column>color__c</column>
            </LineItemsSOQL>
            }}-->

• Additionally, for fields merged within related lists, you may find the substitute column attribute feature useful.

• This attribute is not supported for named query merge fields.

• In most cases, picklist field values are identical to their API names. This attribute covers instances when the two differ.

• Negative, zero, or blank values will not insert any line breaks.
• If you are using this attribute with PDF-Upload templates, force the merged text to wrap by adding the following code to the Additional Style field:

white-space: normal!important;

• Specifying more cells than the field value will result in blank cells being created.

• For related lists, use the type="text" column attribute (explained in the Related List Column Attributes section of this article)

• This attribute can only be used for style="text-align: justify"
• This attribute cannot be used with Microsoft templates

• The blob content must be able to be converted to a string or well-formed HTML
• This attribute is also available as a related list column attribute

• Substitute a checkbox for German language. values:substitute="true,Ja,false,nien"
• Matches are made ignoring case sensitivity and white spaces are trimmed, but the substitute values are exact.
• For checkbox fields use true and false as the value to match on.
• For organization purposes you can optionally use parenthesis to organize your list, e.g.:

substitute="(1,one),(2,two),(3,three)"

• If your value is null, you should not use the substitute attribute but rather use the nullprefix= attribute that will allow you to insert a value whenever null data is encountered for that field.
• If you are matching a numeric value, the precision needs to also match.

<column substitute="2.00,2">quantity</column>

• Example: Use Substitute feature to correctly display the full month Name of field that contains the month number:

<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,December,
unknown">MonthNumber__c</column>

<style type="text/css">.sdcheckbox {
width: 10px;
height: 10px;
border: 1px solid #73AD21;
}
</style>

• type="chackbox" Currently not supported in DOCX file format

• You can merge these two columns together and the resulting column will be

$12 $4

• Prefix and postfix are useful to put any spacing between cell values.

Note: mergenext is not supported when using group-by functionality.

<!--{{!
<lineitemsSOQL>
<class>none</class>
<soql>SELECT productcode FROM opportunitylineitem WHERE Opportunityid ='0061U0000078tEw'
</soql>
<column abfprefixouter=", ">productcode</column>
<postfix>.</postfix>
</lineitemsSOQL>
}}-->

This example would create a list of products that looks like:product1, product2, product3.

<lineitems>
<class>table646</class>
<listname>opportunitylineitems</listname>
<column startIndex="3">rownum</column>
<column>PricebookEntry.Product2.name</column>
<column>PricebookEntry.Product2.description</column>
<column>unitprice</column>
<column>quantity</column>
<column>totalprice</column>
</lineitems>

• This feature is only supported with <lineitemsSOQL> statements
• You must use <soql>...</soql> tags and include any field specifed in your subsitute="..." attributes in your SOQL query
• You should not specify a field between the <column></column> tags. Doing this may cause issues
• You can use RECORD.Field_Name to use related list record data fields within the render="..." attribute
• Any tags inside of the column render (e.g. <span>) will need to have the <> characters escaped (lt#, gt#)

Examples:
<column render="RECORD.Product_Type__c STARTSWITH Vacuum && RECORD.Product_Type__c ENDSWITH Cleaner,RECORD.Vacuum_Name__c,Not a Vacuum"></column>

• If the Product's Type field starts with Vacuum and ends with Cleaner, the column will output the name of the vacuum, otherwise the column will output "Not a Vacuum."

<column render="RECORD.Title==null,No Title Available,RECORD.Title"></column>

• If the Contact's title field is blank, the column will output "No Title Available," otherwise it will output the Contact's title.

You can also use nested render statements:
<column render="RECORD.Country__c == usa,[RENDER1]RECORD.City__c == new york,S-Docs HQ,[RENDER2]RECORD.City__c == ann arbor,S-Docs Innovation Center,[ENDRENDER2][ENDRENDER1],Work From Home"></column>

• If the record's Country field is USA, and the city is New York, the column will output "S-Docs HQ." If the record's Country field is USA and the city is Ann Arbor, the column will output "S-Docs Innovation Center." If the record's Country field is not USA, the column will output "Work From Home."

<column type="rtf" render="RECORD.StageName == 'Closed', lt#span style='color:red;'gt# Closed lt#/spangt#,Open"></column>

• If the Opportunity is Closed, the column will output "Closed" in red. Otherwise, the column will output "Open" in the default font color.

• The blob content must be able to be converted to a string or well-formed HTML
• This attribute is also available as a merge field attribute