You can cause system fields to be mapped automatically by following a naming convention in your merge field names:

@attributepath

where attributepath is the object attribute path that points from the starting object to the system field.

Object attributes are listed in Object Model: Read This First. To identify a system field that is related to the main object, create a path of attribute names that leads to the needed system field, delimited by periods (.).

Keep the following points in mind:

•If the system field is within the main object on which the template is based (such as the project number), then the path only contains one attribute with no periods.

•The final attribute cannot end with an arrow (->) in the attribute name as shown in Object Model: Read This First (or in related reference tables it points to) or the Object Navigator. For example, to select a contact, you must continue the path from contact-> to identify the name or some other attribute of the contact.

•You cannot create a path through an attribute that ends with List->, because these are related and sub-objects. For these, you must use loop@ or filter@ merge fields.

•System field names (known as object attributes) are case sensitive. Make sure to match the exact name and capitalization of the field name.

The following are examples of merge fields in a document template that is based on a project (such as Matter) that would be mapped automatically.

Examples of System Field Automatic Mapping