Sign up / Sign in
Builder review8 min readUpdated June 5, 2026

Repeating sections and repeating tables

Plan a Power Apps pattern for InfoPath repeating data instead of forcing it into a flat SharePoint row.

Quick answer

In short

Repeating InfoPath data usually needs a child list, gallery, or JSON pattern in Power Apps. It rarely maps cleanly to one flat SharePoint list item.

Most likely cause

Repeating sections become messy when every repeated row is treated as another top-level field on the primary item.

What to do next

Choose a child-list pattern unless the repeated data is simple enough to store as JSON or does not need independent reporting.

Pattern choices

  • Child SharePoint list: best for reportable, editable repeating rows.
  • Power Apps gallery: best for editing child rows in the app.
  • JSON column: acceptable for small, non-reporting data where fidelity matters more than SharePoint views.
  • Manual rebuild: best for deep nested repeating structures or relational data that belongs in Dataverse/SQL.

What Form Migrator can do

The analyzer identifies repeating structures and can produce review notes or a first-pass scaffold. The final data architecture should be confirmed by a maker or architect because it affects permissions, reporting, performance, and long-term maintenance.

Questions to answer

  • Do users need to add/remove rows after submission?
  • Do repeated rows need approvals or workflow of their own?
  • Will SharePoint views or reports filter by repeated row values?
  • How should child rows be related to the parent item?

Keep reading the next most relevant guides for this form pattern.

Start7 min read

How to use Optional Settings for field mapping review

Review included fields, override target columns, exclude noise, and leave builder notes before export.

Export8 min read

Validate the generated app before publishing

Run a focused test pass that covers screens, dropdowns, labels, checkboxes, save behavior, and business rules.

Plan8 min read

Triage a portfolio of InfoPath forms

Group forms by complexity, data source, business priority, and export readiness before scheduling migration waves.