After you map the main filter@ merge field, the nested merge fields become available in the Data Mapping tool.
Related Object Nested Merge Field Mapping Examples
Related object |
Data to retrieve |
Navigation steps |
Resulting path |
Any related object |
Custom field value |
1 (Any)-> (traverse) 2 detailList-> (traverse) 3 Select the category of the custom field (traverse) 4 Select the name of the custom field (ok) |
Example: .detailList(LAWY).detailDateValueList(MyDate2).detailValue |
Involved parties |
Contact last name |
1 (Any)-> (traverse) 2 contact-> (traverse) 3 name (ok) |
.contact.name |
Contact first name |
1 (Any)-> (traverse) 2 contact-> (traverse) 3 firstName (ok) |
.contact.firstName |
|
Involved party's default role |
1 (Any)-> (traverse) 2 defaultCategory-> (traverse) 3 name (ok) |
.defaultCategory.name |
|
Histories |
Description (history text) |
1 text (ok) |
.text |
Child projects (such as Participants) or embedded projects |
Child project name |
1 (Any)-> (traverse) 2 name (ok) |
.name |
Child project number |
1 (Any)-> (traverse) 2 numberString (ok) |
.numberString |
|
Contact-centric contact's last name |
1 (Any)-> (traverse) 2 contact-> (traverse) 3 name (ok) |
.contact.name |
|
Contact-centric contact's first name |
1 (Any)-> (traverse) 2 contact-> (traverse) 3 firstName (ok) |
.contact.firstName |
|
Appointments |
Begins On date |
1 (Any)-> (traverse) 2 startOn (ok) |
.startOn |
Tasks |
Due on date |
1 (Any)-> (traverse) 2 dueOn (ok) |
.dueOn |