Repeatable sections
Let field users add multiple rows of line items inside a FieldSet group.
Video coming soon
Repeatable sections
id: academy-repeatable-sections · ~2–4 min
Audience: Admin
Some visits need many similar rows—parts used, tasks completed, meter readings, or audit line items. A FieldSet (fields group) can be marked Repeatable so mobile users tap Add to duplicate the whole section.
Enable repeatable mode
- Add a Fields group container and drop the line-item fields inside (description, quantity, list pickers, photos, etc.).
- Select the group and turn on Repeatable section in its settings.
- Optionally set:
- Min items — minimum rows required before submit.
- Max items — cap how many rows can be added.
- Add button label — customize the button text (default Add item).
Each row is a full copy of the child fields. Answers are stored as an array under the group’s structure.
How it works on mobile
The first row appears automatically. The user taps the add button to append another Item 2, Item 3, and so on. Each row can be removed when allowed by your min/max settings.
Conditional visibility inside a repeatable group is rewritten per row, so a rule on Comment inside row 2 only looks at values from row 2.
Typical use cases
| Scenario | Fields inside the group |
|---|---|
| Parts consumed | SKU list, quantity, notes |
| Safety checklist lines | Task name, pass/fail radio, photo |
| Multi-meter reading | Meter ID list, reading number, photo |
| Service lines | Description, hours, formula subtotal |
Pair repeatable groups with Lists from Data Sources for SKU pickers and Formulas for per-row totals. Summing across rows may require report exports or downstream tools—keep one formula field inside each row for line math.
Design guidelines
- Keep each row short—three to six inputs users can complete standing on site.
- Put shared context outside the group (visit header, customer, overall signature).
- Use Min items when at least one line is always required (
1is common). - Use Max items to prevent accidental hundred-row submissions on large forms.
Tips
- Preview on a phone: adding/removing rows should feel faster than reopening the whole form.
- Required flags on inner fields apply per row when the row is visible.
- Renaming the group slug after go-live may affect integrations—set stable codes early.
- For a single optional extra block (not a list), a second static FieldSet may be simpler than repeatable mode.