The Lookup Field in Automation Pro enables users to establish links between data entries across forms. This field can be used for configuring trigger actions and filter conditions. Currently, it supports only the following two types of configurations:
Related form A.Lookup = Related form B.Lookup(The right-hand value must be from a Lookup field linked to the same master form as form A)
Related form.Lookup = Master form.Data ID(The right-hand value must be the Data ID from the master form configured in the Lookup field)
Note:
These configurations do not support retrieving master form data based on related form data. To retrieve master form records, see Query Record. Similarly, to retrieve related form records more intuitively, see Query Records.
Key Concepts
To better understand the configuration, it is crucial to grasp the relationship between Lookup and Data ID.
1. Lookup -- Data ID
When a Lookup field is used to select a record from a master form, the selected record’s Data ID is stored in the Lookup field. This ID serves as the underlying reference to establish the relationship between the records.
Thus, a Lookup field essentially acts as a pointer to a record in the master form, linking the two entries.
2. Application of Data ID in Automations Pro
Automations Pro utilizes this Data ID to filter or assign records. You can use it to:
Filter related records based on the stored Data ID
Assign new Data IDs to update or establish new relationships
The user cases will be further explained in Sections 3 and 4.
Trigger Node
Trigger Action
When configuring a trigger action as Update Record > Any specific field, you can select the Lookup field as the target.
Trigger Conditions
Lookup fields can also be selected as trigger conditions. Supported filter relationships include: is empty and is not empty.
Filter Conditions
When using Update Record, Delete Record, Query Record, or Query Records, you need to define filter conditions to locate target records.
Lookup fields can be used on the left-hand side of a condition. Depending on the configuration, two main filtering scenarios are supported:
Note:
The same configuration applies when setting up conditions in the Add Path node.
Querying Related Form Records from Master Form
This scenario retrieves all related records from the related form based on a master form record’s Data ID.
For example, if the “Customer Information” form is linked to the “Contact Information” form, you can fetch all contacts for a specific customer by setting:
Contact Information.Customer = Triggered Data--Customer
Querying Related Form Records from Another Related Form
This retrieves related records from one related form based on a record from another related form, both referencing the same master form.
For example, both the “Order Details” form and the “Shipment” form are linked to the “Order” form. While modifying order details, you can fetch the corresponding shipment records using:
Shipment.Related Order = Triggered Data--Related Order
Adding/Updating Records
When adding or updating a Lookup field, you can assign a new Data ID to update the relationship. Two assignment types are supported:
Related Form A.Lookup = Related Form B--Lookup
This assigns the Data ID from Form B’s Lookup field to Form A’s Lookup field.
Related Form.Lookup = Master Form.Data ID
This directly assigns a master form record’s Data ID to a Lookup field in a related form.