Skip to main content

Lookup

Walks you through the basics of the Lookup field and the relationships you can build through Lookup

Updated over a month ago

What is the Lookup Field?

A Lookup Field is a special field type that allows you to establish relationships between data records—either across different forms or within the same form. Through Lookup fields, you can link related data, making data management, querying, and maintenance more efficient and structured.


What Relationships can you Build through the Lookup Field?

1. Inter-Form Relationship

Inter-Form Relationship is used to establish a “one-to-many” relationship between two independent forms in your business. This relationship enables convenient data reference, management, and maintenance between the two forms.

What is a One-to-Many Relationship?

A one-to-many relationship exists when each record in one form (the “master form”) can be associated with multiple records in another form (the “related form”), but each record in the related form only links to one record in the master form. Both forms can exist independently.

For example:


A “Customer” can have multiple “Contacts,” but each “Contact” only belongs to one “Customer”. In this case, the Customer form is the master form, and the Contact form is the related form.

How to build an Inter-Form Relationship through Lookup?

1. Add a Lookup field to the related form (Contact Information here) and select the master form (Customer Information) as the data source.


2. After the relationship is established, a new Tab is automatically added to the data detail page of the master form. This allows you to view and manage all associated records from the related form in one place.

Note:

The settings on the data detail page only take effect for members with permissions to both forms, while the Manage Data page still maintains the default configuration.

2. Intra-Form Hierarchical Relationship

An Intra-Form Hierarchical Relationship refers to a relationship established between records within the same form, allowing you to organize data in a hierarchical, tree-like structure. This is commonly used to represent parent-child relationships within a single dataset.

What is a Tree Structure?

A tree structure is a way of organizing data that looks like an upside-down tree. In this structure:

  • Each “node” stands for a specific data record, such as a department, a task, or a category.

  • The connections (or lines) between nodes show how they are related, with one node being the parent (higher level) and the other being the child (lower level).

  • The top-level node is the root node, which has no parent. All other nodes can only have one parent.

Tree structures are widely used in scenarios such as organizational charts, multi-level product BOMs, and performance goal breakdowns. For example, in performance management, a top-level goal (e.g., annual sales target) is broken down into sub-goals (e.g., semi-annual targets), forming a layered hierarchy.

For example, for the image below, "Annual Sales Target" is the root node, and "H1 Target" and "H2 Target" are the child nodes.

How to build an Intra-Form Hierarchical Relationship through Lookup?

To create a tree structure using Intra-Form Hierarchical Relationship:

1. Add a Lookup field to the form and select the current form as the related form.

2. Enter the root node data without using the relational field.

3. Enter one or more child node records, using the relational field to link each child to its parent node.

4. Repeat this process to build additional layers of the hierarchy.

Note:

The relational data field only supports building relationships between adjacent levels (e.g., level 1 to 2, level 2 to 3). It does not support directly linking level 1 to level 3.

Taking the Sales Performance Management as an example, let's see the specific steps:

1. Add a Lookup field to the Sales Performance form, and select the current form as the form to relate to.

2. Add a root goal, with no need to enter the Annual Sales Target.

3. Add two child node records: H1 Sales Target and H2 Sales Target. Remember to link both of them to the "Annual Sales Target" we submitted before.

Now we have established the relationship between the first level (Annual) and the second level (H1 & H2) goals.

4. Once the relationship is in place, a Related Tab is automatically added to each data detail page to display and manage child nodes.

Note:

No manual configuration is needed for this related tab. For customization options (hide, rename, reorder), refer to the Related Tab.


More to Know

A record cannot relate itself to its parent. To prevent this, the current record is automatically excluded from the list of selectable values when using the relational field.


I have finished reading. 🏆

👉I can't wait to Try for myself.

👉I need more HELP in Discord Forum.

Did this answer your question?