For the complete documentation index, see llms.txt. This page is also available as Markdown.

Link records across tables

Create relationships and link rows together.

Create a relationship using a Link to record field. Match stable record IDs rather than names, which can change or repeat.

Understand the relationship

For example, each order has one customer, while a customer can have many orders:

Orders.id
Orders.customer_id
Customers.id
Customers.name

101

1

1

Ada

102

1

1

Ada

103

2

2

Grace

A single linked record on each order is the many-to-one side of this relationship. It is not automatically a one-to-one relationship. One-to-one also requires that the customer is used by only one order.

  1. Open the field containing the related record's ID, such as customer_id on Orders.

  2. Open its field type and choose Link to Record.

  3. Select the related Resource and Collection, such as Customers.

  4. Review the related field used to match IDs.

  5. Choose a Display Field, such as the customer's name, to make the linked record readable.

  6. Check Orders 101 and 102: both should resolve to Ada. Order 103 should resolve to Grace.

The related field identifies the record; the display field controls the label you see.

The following existing walkthrough uses Customers and Companies to demonstrate the same configuration:

spinner

In Jet Tables, add a Link to record field named Customer, select Customers as the related table, and choose Name as the display field. This form uses the related table's record identity; it does not show a separate matching-field selector.

Customer link field targeting Customers with Name as the display field
Configure the related table and the label displayed in the grid.

Select the related customer on the ticket. In this separate template-data example, ticket 1 is linked to customer 5, Ada Gazey. These sample records differ from the Orders example above.

Customer cell displaying Ada Gazey
The saved link displays the related customer's name.

Check that the target ID exists, both fields use compatible value types, and the target IDs are unique. Check blanks and formatting differences before changing the relationship.

For collections where records on both sides can have several links, see Many-to-many relationships. To display related values or totals, use Lookup or Rollup.

Last updated

Was this helpful?