Available in: Axsy Mobile for Salesforce, Axsy Field Service, Axsy Public Sector, Axsy Retail Execution
Record Lookup Filters
Using Filter Input From Another Element
Record Lookup filters enable you to limit the records displayed in the mobile app.
In the example below a text element is used to capture either the first or last name of a desired contact and this is used as an input to Filter records which compares this value to the Name record field (Name in the Contact object contains the both first and last name).
As filters are case sensitive the use of the LOWER function ensures a match is made.
Figure 1 – Record Lookups Using Inputs from a Text Element
Using Multiple Record Lookup Elements to View Child / Parent Records
Continuing the above example Contacts are a child object of Accounts. We can use the output from a the above Record Lookup to view the parent Account Object.
An invisible Element is used to capture the AccountId field for the contact we have looked up. Note how the Default is configured to reference the previously selected contact and find the Account ID identifier. The full Default syntax is: Contact_Lookup.AccountId.
If we want to lookup account information of the contact we have just selected, we can setup a second Record Lookup Element on the Account Object (in the example below the Element is called AccountCheck) and configure a filter so that an id input is used for the first part of the CONTAINS functioning he second part is the AccountId from the invisible text element above.
Figure 2 – Configuring a Second Record Lookup to find a Parent Object
Expanding Available Information
As shown in the two examples above the Record Lookup is able to concatenate multiple fields together into a single string. For practical purposes the number of fields should not exceed 4 or 5 so as not to confuse the mobile user screen.
However if more information is required this can easily be facilitated by making use of the default values in text Element fields that can be optionally enabled. An example is shown in Figure 3 below.
Figure 3 – Expanding Available Information Into Text Elements