Document Generation Limitations

The following article outlines any limitations when using Document Generation features in Drive Connect:

Supported Standard Objects

When creating a new template in Template Builder and selecting a source object, the following Salesforce standard objects are supported:


  • Account
  • Asset
  • Authorization Form
  • Campaign
  • Case
  • Contact
  • Contract
  • Event
  • Individual


  • Lead
  • Opportunity
  • Opportunity Product
  • Order
  • Price Book
  • Product
  • Task
  • User


Note: Template Builder supports all custom objects. If there is a standard object that we are not supporting please let us know and in most cases we can add support for it relatively quickly.

Unsupported Field Types

When adding merge fields to your merge templates, the following field types are not supported in the merge field generator:

  • Fields that are formatted for HTML (e.g., Rich Text Area fields, hyperlink custom formula fields, and formula fields with an IMAGE text function)
  • Fields that store base64 encoded binary data (e.g., Attachments, Document, and Scontrol records)

Lookup Fields from the Parent Record

When adding merge fields to your merge template that look up to a parent record, you are able to look up to multiple parents in a single merge field. The maximum lookup fields in a single merge field are five parent objects.

For example, if you wanted to retrieve an opportunity’s parent account, then get that account’s parent account name, you could use the following merge field below:

  • {{!Opportunity.Account.Parent.Name}}

The above example only looks up two times, which will merge properly as it does not hit the limit.

Note: When creating a merge field that looks up five times, then adding a Related Object field to the same merge field, the Merge Field Generator will “reset” and allow you to add an additional five lookup fields to that merge field.

When adding a bulleted or numbered related list or a related list to a table, you are allowed to add related objects of related objects to a single merge field up to three levels deep total.

For example, if you wanted to retrieve all child accounts from an account, then get those accounts’ opportunities, and lastly get a list of all the opportunity line item names from every opportunity, you could use the following merge field below:

  • {{!Account.r.ChildAccounts.r.Opportunities.r.OpportunityLineItems.Name}}

Note: When creating a merge field that uses related objects, you are only able to go down three related objects in total. For example, if you create a merge field to go down two related objects, then add a lookup field to the same merge field, the Merge Field Generator will only allow you to add one additional related object to that same merge field.

Unsupported Merge Field on Headers

When adding merge fields to your merge templates, you are allowed to include merge fields in page headers and footers. However, there are limitations around enabling a different first page header and footer and the merge fields that exist within them.

If “Different first page” is enabled, a merge field in the first page’s header and/or footer cannot be merged unless the same merge field exists elsewhere in the template, be it in the document body or the subsequent pages’ headers and footers.