Subtable in seatable

User Talk Base design
1

I use Seatable for the administration of my electronoic components.
Sometimes they were delevered in kits with a lot of different componemnts in the kit. Now I have made a record for each item and a link to a table of all the sets. It is working but it is not exactely what I want.
I wamnt to make a table for each set and a link to tyhes tables in the main table. So in the main-table I see the sets and when I click a set a new table will open with the items in that set. A kind of sub-tables. I that possible in Seatable

2

Please review your post and describe your challenge in greater detail. What exactly is the challenge? Use unambiguous terminology, e.g. do you use the terms kits and sets interchangeably? (Out of courtesy to the community, you could also apply a spell checker.)

3

In SeaTable and similar tools, “subtables” for Kits and their Items are managed through relational links between two separate tables. Instead of nesting data within a single cell, you create a parent table for “Kits” and a child table for “Items.” Each component in the Item table is linked to a specific Kit record, ensuring data integrity and enabling deep analysis.

To achieve your desired workflow in SeaTable:

  1. Relational Structure: You maintain one central “Items” table where every single component for every Kit is stored. These are connected via a “Link to other records” column.

  2. The “Subtable” Experience: SeaTable offers a built-in subtable view within the Row Details. When you open a Kit record, all linked items appear as a filtered list within that window, allowing you to add, remove, or edit components directly.

  3. Dynamic Filtering via Universal App: For a more seamless interface—where selecting a Kit automatically filters a separate list of Items—you can use the SeaTable Universal App. This allows you to build a dashboard where the “subtable” element dynamically reacts to your selection in the main Kit table.

  4. Automatic Calculations: Using Rollup columns in the Kit table, values from the Item table (such as total weight, price, or quantity of all components) are automatically summed up and displayed in the main Kit record.

Comparison: While some other tools offer “Compositions” that feel like embedded sub-forms by default, SeaTable provides more flexibility for cross-kit reporting. In SeaTable, you don’t just see components per Kit; you can also analyze how many different Kits use a specific Item across your entire 2026 inventory with a single click.

4

Yes, a spell checker is a good idea. Lets specify what i mean.

I have, let say, 15 different Totem Maker Construction Sets. They have different components (unique for a specific set) but also the same basic-parts in every set. In seatable I have made a table of all those components and also a table of all the sets. It is easy to link every component to 1 or more sets via link to other records. In this step you can see which comonent is in which set. But I also want to know how many components of one kind are in one set. see example

Component set amount

Brick 1 Basic Set 10

Brick 1 add on set 5

Brick 2      Basic Set             12

ect…

I think that, when linking an component, you must link it to one or more sets.

But then the next problem, where do I have to pu the amout-field.

Or do I have to make a extra table with a few fields and a new record for every component in every set.

Thanks