> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How nested forms work for connected records
- URL: https://blog.jestor.com/nested-forms-connected-records/
- Published: 2026-09-16T18:49:36.000Z
- Updated: 2026-09-16T18:49:36.000Z
- Author: Bruno Bannach

**Nested forms for connected records** let one form create the parent record and all of its child records in the same submission. Instead of saving an order and then adding its items separately, both happen at once. In **Jestor**, this view is called a super form.

## Why connected data usually takes two steps

Most systems treat the parent and the child as separate operations. You create the sales order, save it, open it again and then add the line items.

That second step is where records end up incomplete, because the person who created the header moved on before filling the detail.

What one step submission solves:

- Orders saved without their items
- Projects created without their tasks
- Requests missing the attachments that justify them
- Two screens for what is conceptually one action
- External respondents unable to submit detail through a public link

## Classic view versus super form

| Aspect            | Classic view                     | Super form                          |
| ----------------- | -------------------------------- | ----------------------------------- |
| Layout            | Standard connected list          | A form rendered inside the form     |
| Field selection   | Default set                      | You choose which fields appear      |
| Arrangement       | Fixed                            | Blocks, including side by side      |
| Styling           | Standard                         | Custom button and background colors |
| Conditional rules | Not available in the nested view | Supported                           |
| Read only mode    | Limited                          | Fields can be locked for viewing    |

## Step by step to configure it

1. **Open the app or form** where the connected table appears.
2. **Go to the connected table settings** and choose between classic and super form.
3. **Select the fields** that should show inside the nested form.
4. **Arrange the blocks**, placing fields side by side where it makes sense.
5. **Customize the buttons and background** to match the rest of the screen.
6. **Add conditional rules** so nested fields respond to what was answered.
7. **Mark fields as read only** where the user should see but not edit.

## Why this matters for public submissions

The nested view also works on public links. That means an external person, a client or a supplier, can create a complete record with all its detail in a single submission, without an account and without a follow up email asking for the missing parts.

- **Parent and children created together:** one action instead of two
- **Works on public links:** external respondents submit complete records
- **Custom layout:** fields and blocks arranged as you want them
- **Conditionals inside the nested form:** detail adapts to the answers

## Frequently Asked Questions

### What is the difference between classic and super form?

Classic is the standard connected list. Super form renders a customizable form inside the form. See [jestor.com](https://www.jestor.com/?ref=blog.jestor.com).

### Can I create child records through a public link?

Yes. The connected view works on public links and record creation.

### Can I lock some nested fields?

Yes. Fields can be set to read only so they are visible but not 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](https://www.jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.