The Repeater is a container field for E-forms that repeats a group of fields once per entry. You design the group one time — the template — and at runtime the user adds as many entries as they need, each rendered with the full free-form layout of a normal E-form section. Use a Repeater when each entry should read like a small form (labels, multiple lines, show/hide logic), and use a Table when a compact spreadsheet-style grid is the better fit. Under the hood the two store data the same way, so everything that works with table data works with Repeater data.


Adding a Repeater

Drag the Repeater field from the Container Fields section of the toolbox onto the form (turn on Show Advanced if you do not see it). Then drag the fields you want repeated into the Repeater. Give the Repeater a unique, meaningful Field Name — entries are stored and addressed by this name, just like a table.


Most field types can be placed inside a Repeater: input fields, advanced input fields, display fields, signature fields, and button/action fields. A few types that only make sense once per form are blocked, including File Upload, Record Notes, Scanner, reCAPTCHA, containers (including Tables and other Repeaters), mapping, calendar, data/viewer, and chart fields. The designer will tell you if a field cannot be dropped into a Repeater.


Settings

  • Entry Layout — the column layout applied to each entry, using the same layout choices as Flexible Columns.
  • Row Count Field — optional. When set, the number of entries follows that field's value (for example, a Number field asking "How many children?"). The add and remove buttons are hidden in this mode.
  • Minimum Entries / Maximum Entries — bounds on the number of entries. Maximum 0 means unlimited.


Display options

  • Allow Adding Entries, Allow Removing Entries, Allow Copying Entries — show or hide the per-entry buttons. These are hidden automatically when a Row Count Field is set.
  • Add Button Label — the text on the add button (default "Add Another").
  • Show Entry Numbers — shows the entry number above each entry.


Saving data

By default a Repeater saves its entries into the E-form document. Turn on Save to Record to write each entry into the record's data as table-style rows, where workflow, merge templates, and reports can use them. With Save to Record on, you can also turn on Save Entries as Line Items to store the entries as record line items instead — useful when the entries ARE the record's line items, such as invoice detail rows.


Using Repeater data on the form

Repeater entries are addressed exactly like table data, using the Repeater's Field Name:

  • {Name|1|Child} — the value of the Child field in entry 1.
  • {Name|rowcount} — the number of entries.
  • {Name|display} and {Name|data} — all entries as formatted text or delimited data.
  • {Name||Child} — every entry's Child value as a list.

These references update live as the user types. Fields inside the Repeater cannot be referenced by plain {Name} from outside it — address them through the Repeater as shown above.

Inside an entry, conditions and calculations are scoped to that entry: a Visible When on a template field reacts to its own entry's values, and a Text Label whose value contains {Child} shows its own entry's Child. A Text Label whose Value holds a bracket formula such as [Number1] + [Number2] computes per entry, the same as a Table label column. Column footers and totals across entries do not exist on Repeaters — put a Math Label outside the Repeater and reference the entries instead.


Actions and buttons inside entries

Buttons, Multi-Action fields, and field events placed inside the template run per entry: a Multi-Action watching a template field fires for the entry that changed, and a Button that sets a sibling field sets it in its own entry. Action Sets and Return Table Data commands work on Repeaters with the same grammar as Tables, including clear, row updates, and sort. Inside an entry, the token [#] resolves to that entry's number in outgoing values — so a Button in the entry that sends [#]|delete to the Repeater removes its own entry.


Limitations

  • Repeaters are supported in the current E-form designer and runtime only; the classic (V4) interface cannot display them.
  • Containers cannot be nested inside a Repeater.
  • Entries print in PDF conversions as a simple grid rather than the free-form layout.


NOTE: Signature pad fields inside a Repeater store an image per entry, which can add up quickly when saving to the record. Use them sparingly in Repeaters with many entries.