AFrameSupport

While creating date templates, emails/letters, and email/letter templates you will utilize merge field codes to pull the correct information from the transaction. In this article, it will explain how to use merge field codes and provide merge field code lists.

NOTE: letter case IS important in the code to pull/reference the correct information!

TABLE OF CONTENTS

• Using Merge Field Codes
• Default Date Merge Field Codes
• User Role Merge Field Codes
• Participant Role Merge Field Codes
• Transaction Merge Field Codes
• General Merge Field Codes

Using Merge Field Codes

Emails

When creating an email, using merge field codes can save a lot of time and effort. Merge field codes allow you to personalize the email by automatically populating information into the email. To use merge field codes, simply insert them into the email template or email directly & it will populate the information specific to the transaction or contacts you are creating the email for. The merge field codes can pull different information, such as contact information, transaction date template dates, transaction information cells, and auto-attach attachments. For AFrame merge field codes, use the format: $CustomMergeCode.

Related Articles: Email/Letter Templates, Email Tab

Dates

Each date entry has a custom merge field code associated with it. With this code, you can define what it will be and you can reference it in email templates or even use it within due date formulas for other date entries or tasks. To help you identify the type of code, the date merge field codes start with the prefix $d_.

Related Articles: Date Templates, Dates Tab

Tasks

When creating tasks there are two options for due dates: no due date or due date formulas. When choosing the due date formula you have the option to select a referenced date. The reference date is a date entry or standard date (such as list date, effective date, template start date, closing date, or any custom date made) that will have its unique merge field code associated with it.

Related Articles: Task Templates, Task Tab

Attachments

Each attachment entry has a unique custom merge field code associated with it. This code allows you to define a placeholder for the attachment and reference it within email templates. When you include the merge field in an email template, the corresponding file will automatically be attached, as long as a file has been uploaded to that specific placeholder. This streamlines the process and ensures relevant documents are included in communications. To help you identify the type of code, the attachment merge field codes start with the prefix $a_.

Related Articles: Attachment Templates, Attachments Tab

Information Fields

Each information field has a unique custom merge field code that acts as a placeholder for that field. Similarly, each group of fields has its own custom merge field code. When you use a field group merge field code, it automatically inserts data from all fields within the group that contain information, while excluding empty fields. To help you identify the type of code, individual field codes start with the prefix $f_, and group field codes begin with $fg_.

Related Articles: Field Definitions Templates, Information Fields

Default Date Merge Field Codes

These are the date entries in the default date template for each account. You can always create custom dates with their own custom merge field codes within the date templates. There are optional suffixes for the date merge field codes to help with more conversational formats for emails.

ProTip: You can create multiple date templates in your account with custom dates to apply to your transactions, which is beneficial when you cover multiple states/areas with different contract dates. You can learn more with our Date Templates article.

User Role Merge Field Codes

Add the Prefix (including -) and Suffix together to pull the correct information (i.e. $UserAssistant1-FirstName)

Participant Role Merge Field Codes

Add the Prefix (including -) and Suffix together to pull the correct information (i.e. $UserAssistant1-FirstName). You can add custom participant roles with their own custom Merge Field Code Prefixes under Admin > Lists > Transactions Participant Roles.

Note: You can customize your list of transaction participant roles under Admin > Lists > Transactions > Participant Roles.

Related Articles: Lists :: Participant Roles

Transaction Merge Field Codes

These merge codes will pull the data from the transaction.

Note: You can customize your Information Fields area by moveing or adding more custom fields. You can learn more with our Field Definitions Templates article.

Related Articles: Field Definitions Templates, Information Fields, Payout Tab

General Merge Field Codes

These general merge field codes can be used in emails or email templates.

The use of these general merge field codes within emails or email templates will pull the available information that coordinates with the transaction side that you represent. For example: If you have a buyer side transaction, then the $FirstLastNames Merge Feild Code will pull the buyer(s) participant's first and last name(s) - John & Jane Smith.