Advanced Template Features


S-Docs provides many advanced features for merging data into your S-Doc Template. In most cases described in this document, they require editing of the template source code, which can be easily accessed by clicking on the Source button on the S-Docs Template Editor page.

The template source is based on HTML with specific tags that indicate the S-Docs engine will apply specific mergers or functions.

Merge Field Functions

You can apply multiple functions to merge field data by adding a space and a specific attribute (function) to the end of the field name, like the following:

Single Attribute: {{!Object.Field attribute="value"}}

Multiple Attributes: {{!Object.Field attribute1="value1" attribute2="value2" attribute3="value3"}}

For example, {{!opportunity.amount}} will return an unformatted numeric value as it is stored in the Salesforce database; adding {{!opportunity.amount format-number="#,###.##"}} will return the same value, but formatted to include commas and two decimal places.

Please take note of the following:

  • All attributes require a space between the merge field name and the attribute.
  • When using merge fields within other tags, you may need to escape the HTML in order for the merge to happen properly.
  • Be careful when using the Graphical UI editor to change the appearance of the merge field tag. Care must be taken that styling changes do not interject the merged field syntax. E.g. {{!Opportunity.<style= You may need to click on Source to validate that merged fields do not contain any characters.

Rich Text in Merge Fields

S-Docs will interpret HTML code* in a Rich Text merge field (links, text styling and formatting) when the field is surrounded by 3 sets of curly braces instead of 2:

Numbered list: {{{!Object.Ordered_List__c}}}

*  Images in Rich Text fields are only supported in PDF and DOCX format. For more, see the Dynamic Images article

Merge Field Attributes

Attribute Name Usage & Examples Notes
Format-Number The format-number attribute allows you to custom-format the way numbers are merged into your documents. Only the following EXACT patterns/values are supported for a number format:


format-number=" "

#,###.##  (Typical Currency with cents)

#,###     (Comma delimited whole number)

#.###     (EU formatting)


{{!Opportunity.amount format-number="#,###.##"}}

43222300.8 ➤ 4,222,300.80

{{!Opportunity.amount format-number="#,###"}}

43222300.8 ➤ 4,222,301

{{!Opportunity.amount format-number="#.###"}}

43222300.8 ➤ 4.222.301

  • 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="#.###"}}


Format-Date The format-date attribute allows Salesforce date and datetime fields to be formatted into any valid java pattern.


format-date=" "

{{!opportunity.createdDate format-date="MM/dd/yyyy"}}

2018-10-28 ➤ 04/04/2017

{{!opportunity.createdDate format-date="MMMMM"}}

2018-10-28 ➤ October

{{!opportunity.datetime__c format-date="MM/dd/yy hh:mm:ss TZ:America/New_York"}}

2018-10-28 ➤ 10/28/2018 12:56:32 EST

  • 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.
Checkbox The checkbox attribute allows you to map checked/unchecked checkbox images to boolean fields.


{{!opportunity.checkbox__c checkbox="true"}}

Displays a checkbox with a dotted white border; includes a black checkmark if checked.

{{!opportunity.checkbox__c checkbox="black"}}

Displays a checkbox with a solid black border; fills in with black and includes a white checkmark if checked.

{{!opportunity.checkbox__c checkbox="radio"}}

Displays a radio button.

  • 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
MICR The MICR attribute outputs text in MICR E-13B font (Magnetic Ink Character Recognition), which is used for banking and more specifically for generating checks.


{{!Check__c.RoutingNumber__c MICR="11"}}

To adjust spacing between MICR characters:

{{!Opportunity.Description MICR="[FONTSIZE (REQUIRED)],[SPACING (OPTIONAL)]"}}
{{!Opportunity.Description MICR="20"}}
{{!Opportunity.Description MICR="20,-5"}}

{{!Opportunity.Description MICR="20,5"}}



  • 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.
CR The CR attribute (Character Recognition) allows the user to choose to output text in OCR-A or OCR-B font (Optical Character Recognition), which is used for generating checks and other number strings that need to be read by computers without requiring special toner for printing.


{{!Opportunity.Description CR="[OCR-A/OCR-B],[FONT SIZE (REQUIRED),[SPACING (OPTIONAL)]"}}

{{!Opportunity.Description CR="OCR-A,20,5"}}

{{!Opportunity.Description CR="OCR-B,20,5"}}



  • 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.
ToUpperCase The ToUpperCase attribute transforms data to all uppercase characters.


{{!contact.billingStreet ToUpperCase="true"}}

123 Main Street, Apt 3 ➤ 123 MAIN ST, APT 3

ToLowerCase The ToLowerCase attribute transforms data to all lowercase characters.


{{!contact.billingStreet ToLowerCase="true"}}

123 MAIN ST, APT 3 ➤ 123 main street, apt 3

Right to Left (RTL) The RTL attribute reverses the character string in the output. This is useful for RTL languages like Hebrew when generating to a PDF.


{{!account.greeting__c RTL="true"}}

שלום➤ םולש



  • 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:


  • 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.


Translate The translate attribute uses Salesforce Translation Workbench feature to return the picklist value based on the users locale/language settings


{{!product2.color translate="true"}}


Translate can be used only on picklist fields, but can be used on all field labels.

Click here to learn more.

  • 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:

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

  • Additionally, for fields merged within related lists, you may find the substitute column attribute feature useful.
replaceAll The replaceAll attribute allows for replacing values with other values. This attribute matches against (and replaces) all substring appearances of the specified string.


{{!Opportunity.Name replaceAll="ReplaceThis1,ReplaceWithThis1,ReplaceThis2,ReplaceWithThis2"}}

Encrypt The encrypt attribute allows for displaying fields with classic encryption set as encrypted in the generated document.


{{!Opportunity.EncryptedField__c encrypt="true"}}

  • This attribute is not supported for named query merge fields.
Display The Display attribute will render picklist field values as the field value (the value shown to users on records) instead of field API value. By default, S-Docs renders the field value API name.


{{!Opportunity.PicklistField__c Display="true"}}

  • In most cases, picklist field values are identical to their API names. This attribute covers instances when the two differ.
MSNL The msnl attribute will replace the semicolons between values from a multi-select picklist with new lines.


{{!Opportunity.Multi_Select_Picklist_Field__c msnl="true"}}

breakeverynchars The breakeverynchars attribute will insert a space after the character number that you specify to allow line breaks


{{!Opportunity.Long_Field__c breakeverynchars="10"}}

supercalifragilisticexpialidocious ➤ supercalif ragilistic expialidoc ious

  • 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;
toCells The toCells attribute will break a field value into single-letter cells. This attribute can only be used on merge fields within <td> tags. It is written in the following syntax:


{{!Object.Field toCells="Number of Cells to Generate,CSS class to apply to table cells"}}


{{!Opportunity.Three_Character_Code__c toCells="3,table873"}}

123 ➤ 1, 2, and 3 would be in separate table cells, which would each have the table873 CSS class applied to them.

  • Specifying more cells than the field value will result in blank cells being created.
strip-html The strip-html attribute will remove any HTML tags from data merged into your document from rich text fields.


{{!Object.Field strip-html="True"}}

justifyNewLines The justifyNewLines attribute prevents irregular spacing when merging multi-paragraph long text area fields wrapped in justify tags. It causes each paragraph to be treated as its own paragraph.


{{!Object.Field justifyNewlines=“HTMLElement”}}


INPUT: <div style=“text-align: justify;”>{{!Opportunity.Long_Text_Area__c justifyNewlines=“div”}}</div>

OUTPUT: <div style=”text-align: justify;”>Paragraph One</div><div style=”text-align: justify;”>Paragraph Two</div>

  • This attribute can only be used for style=“text-align: justify”
  • This attribute cannot be used with Microsoft templates
blobToString The blobToString attribute converts HTML-based blobs into strings


{{!Object.Field blobToString=“true”}}

  • 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

By default, S-Docs merges related lists into your template in the form of a table, where each record returned is generated as a row in the table. This means the table grows linearly with the number of records returned. In order to meet more specific formatting requirements, S-Docs has a variety of advanced attributes that can be leveraged.

Feature Name Description
DirectSOQL Allows you to execute a custom SOQL query within your template and merge the resulting data into your document at runtime. DirectSOQL supports aggregates and subquery functions.
Render Provides ability to show/hide sections of a template based on a condition.

Displaying Related Lists & SOQL Line Items Without Table Formatting

To remove the table formatting in a related list or SOQL table, you can place <class>none</class> at the beginning of your related list / SOQL code. For example, the following code will display account team members as a comma-delimited list rather than as a table:

<prefix>The Account Team Members are: </prefix>
SELECT FROM accountteammember WHERE accountid='{{!}}'
<column postfix=", "></column>
<postfix>. Please see page 3 for their contact information.</postfix>

In this example, <class>none</class> removes all the table formatting. The postfix attribute adds a comma and a space between each account team member, but if we did not have this postfix attribute here, the items returned by the SOQL query might look something like this: Jack JohnsonJohn JacksonSarah McCleanJohn Paulson. This is because using <class>none</class> will make your SOQL query or related list return raw data with no spaces or table formatting, all on the same line.

Alternatively, if you need to format your related list data in an entirely new way, you can also generate a template component that formats your data and then merges it into your final document. Click here to read more about this feature.

Related List Column Attributes

Related lists contain columns that can optionally include additional attributes (shown in bold below). These attributes provide a powerful way to dynamically manipulate data to meet your requirements.

Note: Attributes must always be double quoted, e.g. format-date="MM/dd/yyyy"
Example: <column format-date="MM/dd/yyyy">createddate</column>
Column Attribute Values Description & Syntax Examples & Notes
substitute Comma-delimited list of key-value pairs. Allows for replacing values with other values whenever a match is made. It checks the value against a series of values. If it is equal to a value, it returns the corresponding  result. If it does not match, no substitution is made unless a final catch-all value is provided in the list.

Substitute functionality can be useful for translating values to different languages for a template. While you may be able to do the same using a Salesforce formula field, this can drastically reduce the number of formula fields you would need to create.


<column substitute="value1tomatch, value1ToSubstitute, value2ToMatch,Value2ToSubstitute,




If the substitute list contains an odd number of values, then the last value will be the catch-all that is substituted when no matches are made.

  • 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.:


  • 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,

replaceall Comma-delimited list of key-value pairs. Allows for replacing values with other values. This is very similar to the substitute feature, with the following two exceptions:

1) substitute matches against (and replaces) the ENTIRE string, where as replaceall matches against (and replaces) all substring appearances of the specified string.

2) There is no "else" condition in replaceall (since we're replacing substrings, an "else" condition would be nonsensical)

This attribute supports regexs.


<column replaceall="replaceThis1,replaceWithThis1,replaceThis2,replaceWithThis2,...replaceThisN,replaceWithThisN">

Regex Syntax:

Start your replaceall string with [regex] (including brackets)

For example, say you want to replace all        "a) This is a test", "b) This is a test", etc. with " a) This is a test", " b) This is a test" but NOT replace anything that looks like "1. This is a    test", "2. This is a test", etc. (i.e. you want to       indent a) b) c) but not 1. 2. 3. and the data   structure / related list formatting prohibit     simpler solutions like using <li></li>). To    achieve this, you could use the following:       <column replaceall="[regex]([a-zA-Z]\)),     &nbsp;&nbsp;&nbsp;&nbsp;$1">


If the data value is "Burlington
Textiles Corp," but you want it to be "Boston Textiles Corp," use <column replaceall="Burlington,Boston">
showcolumn Conditional statement Allows you to conditionally show/hide a column.


<column showcolumn="{{!Object.Fieldname}} == 'FieldValueThatTriggersColumnShowing'">...</column>

Note that the column will be hidden if the syntax resolves to false.

If your table has a header row, you will need to apply the same condition to the header row as a RENDER statement:

<!--RENDER='{{!Object.Fieldname}}' == 'FieldValueThatTriggersColumnShowing'--><th>Column Name</th><!--ENDRENDER-->

You can conditionally show an entire column in your related list if the Opportunity record's StageName
field has a value of 'Prospecting' or 'Closed', and hide it if the StageName field has any other value, by using the following: <column showcolumn="({{!Opportunity.StageName}} == 'Prospecting' || {{!Opportunity.StageName}} == 'Closed')">...</column>
type "rtf", "text", "checkbox", or "radio" If your field contains markup that you wish to preserve and display in your document, you can specify type="rtf"

This is useful for inserting blocks of information that already contains formatting/markup.

If you wish to strip the HTML tags from your rich text field, you can specify type="text"

If you want to display a checkbox or radio button image (checked and unchecked) rather than the database values of true/false or yes/no, you can use type="checkbox" or ="radio"


<column type="rtf">Your content goes here.


When using type ="checkbox" the checkbox images have a class called "sdcheckbox." If needed, you can modify the CSS treatment of the checkbox. E.g.

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

  • type="chackbox" Currently not supported in DOCX file format
header String Allows you to specify a header text.


<column header="YourHeaderHere">

Example: <column header="Grand Total">will place "Grand Total" over that column as a header.
format-number Number Allows you to format your column’s numbers to automatically include commas and periods.


<column format-number="#,###.##">

Format number supports these four types:#,###




For example, if a number in your column was stored as 123456 and
you chose the 2nd type listed above, the number would appear as 1,234.56

format-date Date, Date/Time Allows Salesforce date and datetime fields to be formatted into any valid java pattern.


<column format-date="MM/dd/yyyy">

To turn a date into just a day, month, or
a year, you can use <column format-date="MMMMM"> (for days, use D, and for years, use Y)
mergenext Any value Allows you to merge a cell with the cell to the right of it.


<column mergenext="true">

If you have a currency symbol column and an amount column,
like           $        |        12$        |        4

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



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

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

colspan Any value Allows you to create a column that spans across multiple columns.


<column colspan="4">

has no effect; by default, a column
already spans 1 column.
Will make this column span 4 columns total (i.e. this column will be 3 columns longer than it would normally be).
This works the same as the HTML
colspan attribute.
newrow Any value Allows you to specify when to end the current row and create a new one.


<column newrow ="4">

<column newrow="true">
Will create a new row for each record in this column. For example, instead of seeing
cell 1 | cell 2 | cell 3
you will see
cell 1
cell 2
cell 3----<column newrow="3">
Will create a new row after the 3rd
record of each row, e.g.
cell 1 | cell 2 | cell 3
cell 4 | cell 5 | cell 6
cell 7 | cell 8 | cell 9
This attribute is useful for creating documents such as mailing labels.
prefix Any value Allows you to put a string at the beginning of each column.


<column prefix="YourStringHere">

<column prefix="$"> would put a
dollar sign at the beginning of each
column like so:$                12$                4
nullprefix Any value If the content of a column is "null," this will swap null with a string or character of your choice at the beginning of your column.


<column nullprefix="YourStringHere">

<column nullprefix="N/A"> will make columns with "null" values appear as
postfix Any value Allows you to put a string at the end of each column.


<column postfix="YourStringHere">

<column postfix="dollars"> would put "dollars" at the end of each column like so:12                dollars

4                  dollars

nullpostfix Any value If the content of a column is "null," this will swap null with a string or character of your choice at the end of your column.


<column nullpostfix="YourStringHere">

<column nullprefix="N/A"> will make columns with "null" values appear as
allprefix Any value. This replaces the need to use both prefix and nullprefix in the same template if they have equal values. If your template has both prefix and nullprefix set to the same value, you can replace them with this attribute.


<column allprefix="YourStringHere">

<column allprefix="$"> will put "$" at
the beginning of each column
regardless of if the value is null or not.
allpostfix Any value This replaces the need to use both postfix and nullpostfix in the same template if they have equal values. If your template has both postfix and nullpostfix set to the same value, you can replace them with this attribute.


<column allpostfix="YourStringHere">

<column allpostfix="€"> will put "€"
at the end of each column regardless
of if the value is null or not.
abfprefixouter Any value Allows you to put a string at the beginning of each column except the first one. The string will appear on the outside of the prefix attribute's contents.


<column abfprefixouter=",">

<soql>SELECT productcode FROM opportunitylineitem WHERE Opportunityid ='0061U0000078tEw'
<column abfprefixouter=", ">productcode</column>
}}-->This example would create a list of products that looks like:product1, product2, product3.
startIndex Any numerical value Allows you to offset the beginning row number when you include the rownum column in your related list.


<column startIndex="3">

Note that numbering starts at the number equal to the startIndex number + 1.

<column startIndex="3">rownum</column>

This example would output a table with row numbers beginning at 4.

render Comma-delimited list of render conditions & output values Allows you to conditionally render different values in your related list columns.


<column render="CONDITION_1,output_value_1,CONDITION_2,output_value_2...DEFAULT OUTPUT VALUE IF ALL RENDERS EVALUATE TO FALSE">

  • 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#)


<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.
breakeverynchars Any numerical value Inserts a line break after a specified character amount.


<column breakeverynchars="10">

<column breakeverychars="10">Long_Line__c</column> will insert a line break after every 10 characters.
addToEmail "To", "CC", "BCC" Adds email addresses merged through this column as document email recipients.

Note: This attribute must also be added as an apex parameter to your S-Docs button URL.


<column addToEmail="To">

<column addToEmail="CC">CreatedBy.Email</column> will add the email addresses of every user who created a record in this related list as document email CC recipients
blobToString True Converts HTML-based blobs into strings


<column blobToString=“true”>

  • 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

Tags: , , , , ,

Was this helpful?