How to show parent record data on a child card
Bringing parent record data on a card means a task card can display information from the project it belongs to, and from whatever that project is connected to, several levels up. In Jestor, you choose exactly which fields travel down and how they are displayed.
Why context gets lost in connected data
A relational structure stores each fact once, which is correct. The side effect is that the person working on a child record often sees only a reference: the project name, and nothing else.
Then they have to open the project to answer a simple question about budget, client or deadline, and the context switch costs more than the answer is worth.
What this solves:
- Opening the parent record just to check one number
- Task owners working without knowing the project budget
- Decisions made on a card without the surrounding context
- The same information copied onto the child record to avoid the lookup
How many levels you can traverse
| Level | Example | What you can display |
|---|---|---|
| The record itself | A project stage | Its own fields |
| One level up | The project it belongs to | Budget, client, deadline |
| Two levels up | The client account | Contract terms, owner |
| Further up | Whatever the chain connects to | Selected fields at each level |
Step by step to configure it
- Open the card or form where the child record is displayed.
- Add the connected view, choosing between the card display and the super form display.
- Select the fields that should come down from the parent, rather than showing everything.
- Add another level if the parent has its own parent worth surfacing.
- Customize the appearance, since the display can be styled per level.
- Set fields as read only where the person should see but not edit them.
Why choosing the fields matters
Surfacing everything reproduces the clutter problem in a new place. The value is in picking the two or three facts the person actually needs at that moment, and leaving the rest one click away.
- Selective display: only the fields you choose travel down
- Multiple levels: the chain can go as deep as your structure does
- Two display modes: standard card view or a nested super form
- No duplication: the data stays stored once, at its source
Frequently Asked Questions
Does this copy data onto the child record?
No. The information is displayed from the parent, so it stays stored in one place. See jestor.com.
Can I go more than one level up?
Yes. If the parent has its own parent, you can surface that level too.
Can the surfaced fields be edited?
They can be set as read only, so they are visible without being editable.
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.