Groups & tables — related records inside a form.

Section vs Group

Both Section and Group are containers — you drop other fields inside them — but they serve different purposes:

• Section — a visual container with a title, optional border, and a column count (1–10). Use it to group related fields and lay them out side by side.
• Group (Pro) — a container that represents multiple related Salesforce records. The visitor can add several entries; each entry is one related record that gets prefilled, updated, or created.

Both elements sit next to each other in the Building Blocks panel under Display Elements.

Section

Add a Section, then drop fields inside. The Section's settings live in the right-hand Element Properties panel when you select it. The key ones:

• Title — the heading shown at the top of the section.
• Show Title — toggle whether the title is visible.
• Boxed — whether to draw a border around the section.
• Columns (1–10) — how many columns the section's children are laid out in.

Group

Add a Group when the visitor needs to enter multiple of the same kind of related record on one form. Drop input fields inside the Group — each field becomes a column for every entry the visitor adds. At runtime, the visitor can add or remove entries within the limits you set.

The Group element is wired to Salesforce records on a child object. Combined with prefill and submit, this lets the form show existing related records, let the visitor edit them, add new ones, and have the changes saved back to Salesforce in one submit.

Table view

A Group can render its entries two ways:

• Stacked cards (default) — each entry is a vertical card with its child fields. Best for forms with longer fields or many fields per entry.
• Table — each visible field becomes a table column, and each entry is a table row. Best for short, tabular data like timesheets or line items.

You pick the view in the Group's element properties. On mobile, table layouts collapse so the form remains readable on small screens.

Row labels

In table view, you can choose whether to repeat the field labels on every row, or show them only once as a single table-style header on desktop. Both options are available in the Group's element properties:

• Show labels on each row — visible on every entry. Reads more like a stack of cards even when rendered as a table.
• Single header row — labels appear once at the top, like a spreadsheet. Tighter on desktop.

On mobile, labels are always shown per entry regardless of the desktop choice, so each entry stays readable on a narrow screen.

Prefill, update, create

A Group works hand-in-hand with prefill and submit actions:

• Prefill — use a Find multiple records (findMany) prefill action to look up existing related records. Bind the result's alias to the Group, and each returned record becomes one pre-populated entry on the form.
• Update / create — use a Save records list (upsertMany) submit action. Pick the Group as the source of entries, the target child object, the parent relationship (which lookup links the child to the parent record, and where the parent Id comes from), and map each entry's fields to the child object's fields.

Each entry's hidden Id field decides whether that row is updated (Id present) or created (no Id) on submit. Visitor-deleted entries can also be deleted from Salesforce when the submit action is configured to allow it.

See Prefill and Submit actions for the full patterns.

More in element properties

The Group element has additional settings beyond what's covered here — entry limits, the add-entry button label, conditional visibility, and other behavior controls. Select the Group on the canvas and review the right-hand Element Properties panel for the full set.

Limits & gotchas

• Group is a Pro feature — it appears in Building Blocks for everyone, but it requires a Pro license to use in published forms.
• File uploads inside a Group entry are not supported in V1. Use top-level File Upload elements outside the Group instead.
• Signature can be added directly inside a Records List on Pro. Each submitted row receives its own signature, and Submission PDF is enabled automatically so the signed rows are preserved in a readable document.
• Lookup fields inside a Group entry are not supported in V1. Use a hidden Id field instead, or move the lookup out of the Group as a top-level field.