How to use connected tables inside forms
Using connected tables inside forms means a person filling in a form can also view and edit the related records without leaving it. In Jestor, you control which tables appear, which fields are visible, which are editable and which are read only.
Why forms and related data usually stay separate
A form traditionally writes to one table. Anything related to that record has to be handled afterwards, in another screen, by someone who knows where to look.
For a process with several connected tables, that means the form captures a fraction of what the process actually needs.
What this changes:
- Related records handled in a second step, often forgotten
- The person filling the form unable to see relevant context
- Multiple screens for what is one logical action
- Reference data retyped because it was not visible
What you control in the configuration
| Setting | What it defines | Why it matters |
|---|---|---|
| Which tables appear | More than one connected table can show | A full 360 view in one place |
| Which fields show | The visible subset per table | Avoids overwhelming the person |
| Read only fields | Visible but not editable | Context without risk of change |
| Editable fields | What the person is meant to fill | Focus on the actual task |
| Form behavior | How records are added and displayed | Matches the process flow |
Step by step to set it up
- Open the form and go into the edit view.
- Add a connected table block, giving it a clear name.
- Select the table it should display.
- Choose the fields that appear, keeping the set small.
- Mark reference fields as read only, leaving only the ones that need input editable.
- Add a second connected table if the process requires more than one.
- Test as an end user before releasing it.
Where this fits best
Processes with a header and detail benefit most: an order with items, a project with stages, a supplier with documents. The person handles the whole thing in one screen, and the data still lands in separate, properly structured tables underneath.
- Several tables in one form: the complete picture without navigation
- Editing in place: connected records changed without leaving the form
- Field level control: visible, editable or locked, per field
- Structure preserved: the data still lives in its own tables
Frequently Asked Questions
Can a form show more than one connected table?
Yes. Multiple connected tables can appear in the same form. See jestor.com.
Can I make some fields visible but not editable?
Yes. Fields can be set to read only while others remain editable.
Does this work inside cards as well?
Yes. The same connected view is available in cards, not only in forms.
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.