This article contains all the MailMerge tables for the CRM module. Each table contains MailMerge fields that can be used to edit CRM document templates. Please see Template editing for a video tutorial of the template editing process and familiarise yourself with how to Manage Document and Email Templates before editing your templates. CRM document templates can be downloaded from Settings → Document and email templates → CRM. 

CRM MailMerge fields are used in the following template types: Task, Task List and Opportunity.

NOTE: DEAR have a dedicated support team for resolving template issues, don't hesitate to contact DEAR Support for help.

Prerequisites

• Manage Document and Email Templates (required) - please start here first if you are unfamiliar with how MailMerge fields work.
• Getting started with CRM (required). 

Table of Contents

• Important table structure information 
• CRM MailMerge Fields
  • Tasks and Task Lists
  • Opportunity
    • Products
    • Additional Charges

Important table structure information

[back to top]

All sections in a template must be contained within TableStart and TableEnd tags. This defines which table the mail merge fields data will be pulled from. 

• Templates will start and end with the parent TableStart and TableEnd tags, e.g. «TableStart:Purchase» and «TableEnd:Purchase». Child TableStart and TableEnd tags can be placed within the parent tags. 
• Tables that may have multiple lines generated in them, for example, tables with sale order lines, purchase order lines, or additional Charges, will have TableStart and TableEnd tags within the table itself. e.g. «TableStart:POLines» and «TableEnd:POLines». These are child tags that will be found within the parent tags. 
• TableStart and TableEnd tags that end in Details (POLineDetails, InvoiceDetails etc.) are for matrix documents, e.g. Purchase Order Matrix, Invoice Matrix. 

If you need to customise standard templates, make sure that the opening tag for any table «TableStart:NAME» has the matching closing tag «TableEnd:NAME», or your template will not work. Try to change the structure as little as possible to preserve the template functionality. 

Parent table fields can be used in child tables but child table fields can only be used within the child table. In the sample table, Purchase is the parent table and POLines is the child table. 

Sample Structure:

Right-click any <<field name>> and click Toggle Field Codes to show the field code (displayed as {MERGEFIELD field code}). 

Windows users can toggle all field codes by holding down ALT + F9.

Mac users can toggle all field codes by pressing OPTION + F9.

FIELD NAMES: Don't change these.

FIELD CODES: Change these.

Once you have made your changes to the field code, right-click and click Update Field for the changes to take effect. 

CRM MailMerge fields

[back to top]

CRM MailMerge fields are used in the following template types: Task, Task List, Opportunity.

Tasks and Task Lists

[back to top]

The Task and Task List document templates are essentially the same, except Task List shows multiple tasks, whereas Task shows only one. 

These field codes can be used between the «TableStart:Tenants» and «TableEnd:Tenants» tags. This is the parent MailMerge table for the task and task list templates. Parent fields can be used anywhere between the parent start and end tags.

These field codes can be used between the «TableStart:Tasks» and «TableEnd:Tasks» tags. 

These field codes can be used between the «TableStart:TaskCategory» and «TableEnd:TaskCategory» tags. Task categories are optional for tasks. 

Opportunity

[back to top]

These field codes can be used between the «TableStart:Opportunity» and «TableEnd:Opportunity» tags. This is the parent MailMerge table for opportunity templates. Parent fields can be used anywhere between the parent start and end tags. 

Opportunity field codes can be used in the Opportunity document template.

Products

[back to top]

These field codes can be used between the «TableStart:Products» and «TableEnd:Products» tags. This is a child MailMerge table. Parent MailMerge table (Opportunity) fields can be used between child table start and end tags but child MailMerge table fields can only be used between the child table start and end tags. 

Products TableStart tags, TableEnd tags and field codes are used to generate tables where opportunity product lines are displayed.

AdditionalCharges

[back to top]

These field codes can be used between the «TableStart:AdditionalCharges» and «TableEnd:AdditionalCharges» tags. This is a child MailMerge table. Parent MailMerge table (Opportunity) fields can be used between child table start and end tags but child MailMerge table fields can only be used between the child table start and end tags. 

AdditionalCharges TableStart tags, TableEnd tags and field codes are used to generate tables where opportunity additional charges lines are displayed.