How to model a one-to-many relationship between tables
A one-to-many relationship between tables means one record on one side connects to many on the other: one supplier has many payables, but each payable belongs to a single supplier. In Jestor, you create it by adding a connected record field and pointing it at the other table.
Why this is the most useful structure to learn first
Most business data follows this shape. One client with many orders. One project with many tasks. One employee with many expense claims. Getting it right removes the single largest source of duplicated data.
The alternative, repeating the supplier's name, phone and email on every payable, is what turns a table into an unmaintainable mess.
Where you will use it constantly:
- Payables pointing to a supplier
- Orders pointing to a client
- Tasks pointing to a project
- Vehicles pointing to a driver
- Tickets pointing to a requester
Choosing the label field
| Decision | What to pick | Why |
|---|---|---|
| Which table to connect | The registry table | It holds one row per real entity |
| Label field | Usually the name | It is the most recognizable identifier |
| Direction | Many to one, from the detail side | Each payable has one supplier |
| Field name | The entity, such as supplier | Clear to whoever fills it in |
Step by step to create it
- Build the registry table first, with one row per supplier, client or project.
- Open the detail table, such as payables, and add a column.
- Choose the connected records field type.
- Select the direction, many to one from the detail side.
- Pick the table the field should point to.
- Set the label field, normally the name, since it identifies the record to the user.
- Fill in a record to confirm the connection behaves as expected.
What you gain immediately
Once the connection exists, the supplier's details are available from every payable without being stored again. Change an address once and every related record reflects it.
- No repeated data: the entity is stored once
- Any field can be the label: the name is just the usual choice
- Consolidated history: the supplier record shows everything linked to it
- Foundation for formulas: calculations can read across the connection
Frequently Asked Questions
What does many to one mean in practice?
Many payables can point to one supplier, but each payable has exactly one. See jestor.com.
Which field should I use as the label?
Any field can serve, though the name is usually the most recognizable.
Do I need to create the registry table first?
Yes. The connected field needs an existing table to point at.
Video Tutorial: Step by Step
With Jestor, you can automate workflows, connect teams, and build internal systems your way, all without code and powered by AI. Discover Jestor at jestor.com and see how to take your company's operations to a new level of efficiency and control.