Skip to main content

Hi, I hope you can help me:

I have two tables. “Customers” and “Products”.
The “Products” table shows all items that belong to a specific product: Multiple items are assigned to one product via the “Product” field (single selection). By then grouping by the “Product” field, I get a catalog that shows me which items belong to which product. (Ex: Product 1, items 1-5, 7 and 9-10; Product 2, items 1-5 and 7-12).

Now we have a new customer. Again, in the table “Customers”, I want to show which items the customer gets. The easiest way would be if I can say via a link:Customer XY has product 1 and then Airtable automatically shows me the corresponding items in a single field (here in the example items 1-5, 7 and 9-10).

So far I have only managed to link each record individually, but then I don’t need the summary for the product. Basically I am looking for a way to link groupings.

I hope I was able to make my problem understandable🙈 Does anyone have any ideas? Is that possible at all?

@Sebastian_Apel If I understand you correctly, you have a Products table and a Customers table. Within the Products table, you have Products and Sub Products, each Sub Product assigned to a Product. From the Customers table, you want to assign a Main Product and get all of the Sub Products.

TLDR (Current Implementation): 2 Tables (Products and Customers), and 3 Data Types (Products, Sub Products, and Customers.

I would say the best way to solve this would be to add a third table for Sub Products. This allows you to create Sub Products assign them to Products, and then use a Lookup field to access the Sub Products when you assign them to a Customer. Here are some screenshots of an example:

Product Table

Sub Products Table

Customers Table

As you can see, this setup allows you to link Sub Products to Products as you used to have it. However, this new setup now means when you link a Product to a customer, you can easily use a Lookup field and grab all of its Sub Products.

Furthermore, if you like the grouped view, you can still do this from the Sub Products table:

TLDR (New Implementation): Split Products and Sub Products into their own tables, and use a Lookup field to pull Sub Products into the Customers Table.

@Sebastian_Apel If I understand you correctly, you have a Products table and a Customers table. Within the Products table, you have Products and Sub Products, each Sub Product assigned to a Product. From the Customers table, you want to assign a Main Product and get all of the Sub Products.

TLDR (Current Implementation): 2 Tables (Products and Customers), and 3 Data Types (Products, Sub Products, and Customers.

I would say the best way to solve this would be to add a third table for Sub Products. This allows you to create Sub Products assign them to Products, and then use a Lookup field to access the Sub Products when you assign them to a Customer. Here are some screenshots of an example:

Product Table

Sub Products Table

Customers Table

As you can see, this setup allows you to link Sub Products to Products as you used to have it. However, this new setup now means when you link a Product to a customer, you can easily use a Lookup field and grab all of its Sub Products.

Furthermore, if you like the grouped view, you can still do this from the Sub Products table:

TLDR (New Implementation): Split Products and Sub Products into their own tables, and use a Lookup field to pull Sub Products into the Customers Table.


If this doesn’t make sense, note that there is an Airtable Support article that walks you through two different implementations that could work for you, one of which I already outlined. Just found it after responding to you earlier! It’s based on tasks – so not everything is applicable – but some of the ideas may be helpful.

If this doesn’t make sense, note that there is an Airtable Support article that walks you through two different implementations that could work for you, one of which I already outlined. Just found it after responding to you earlier! It’s based on tasks – so not everything is applicable – but some of the ideas may be helpful.


Hey, thank you very much.

That makes definitely sense for me. It was a crucial move to create a third table!

Thank you again for your help!

Terms & ConditionsAccessibility statement