Available in: Axsy Mobile for Salesforce, Axsy Field Service, Axsy Public Sector, Axsy Retail Execution
Once values have been inserted using the Mapping Lookup Tool, the syntax will vary slightly depending on whether the element is a Loop Element, the element is contained within a Loop, or the element is referencing a Salesforce Field that is accessed via a Lookup Relationship.
NOTE: Custom Lookup Fields and Custom Related Lists use the suffix __r instead of __c. Custom Fields you want to map to, and Custom parent Lookup Objects, always use the suffix __c.
NOTE: Salesforce Object and Field API Names are always used in mapping configurations.
Loop Mappings
For Loop Field Mappings, Lookup Fields used to access the Related List will all be separated by a dot, and the parent Lookup Object of the Related List will follow a colon.
In the examples below, it is assumed that the Work Order object is running the Smart Form.
Relationship | Syntax Example |
---|---|
Related List related directly to the Object running the Form (Work Order) | WorkOrderLineItems:WorkOrder
|
Related List path uses one Lookup Field to access the Related List from the Work Order | Account.Contacts:Account
|
Related list path uses two Lookup Fields to access the Related List from the Work Order | Contact.Account.Requests__r:Account
|
NOTE: To reference the Related Object records correctly, you need to use the Child Relationship Name, by accessing the Salesforce Field that connects the Related List to the parent Lookup Object.
Elements Contained in a Loop
Mappings for Elements contained in a Loop follow the pattern of FieldName:RelatedObject, where RelatedObject is the Object API Name of the Related List referenced in the Loop Element containing it.
Example: If the Loop Element's Field Mapping is set as WorkOrderLineItems:WorkOrder, an Element inside the Loop would have a mapping like MinCrewSize:WorkOrderLineItem.
Elements Outside a Loop
Field Mappings for Elements outside a Loop follow a similar pattern to Loop Field Mappings, where the Lookup Fields and target Salesforce Field are separated by dots, and the parent Lookup Object follows a colon.
In the examples below, it is assumed that the Work Order object is running the Smart Form.
Relationship | Syntax Example |
---|---|
Field on Object record running the Smart Form (Work Order) | Status:WorkOrder
|
Field on Object accessed via one Lookup Field from the Work Order | Contact.Email:Contact
|
Field on Object accessed via two Lookup Fields from the Work Order | Building__r.BuildingSite__r.SiteName__c:Site__c
|