FormsModel-driven app

Main form

The page for one row: a header card, tabs, and sections of fields in one to three columns, with labels beside or above the fields.

Show me in the demoOpens the demo app with this component highlighted.

What it is

The main form is where you read and edit one row. At the top is the header card with the image, the name, the save status, the form selector and a few header fields. Below are tabs, and inside each tab are sections that hold fields in one, two or three columns. Labels can sit beside the field or above it. Subgrids, the timeline and other components can sit in sections too.

When to use it

Use the main form for full data entry and review of a row. Keep it scannable: put the fields people need first on the first tab and move the rest to other tabs. For fast entry of a few fields, give the table a Quick create form. When different roles need different layouts, make several main forms and let people switch with the Form selector.

Licensing and configuration

No extra licence. You build forms in the form designer, opened from the table in Power Apps or from the app designer. You add tabs, sections and fields, set the number of columns, and choose which fields go in the header. Forms are included in the app through the app designer, and security roles can restrict which forms a user sees.

Pitfalls

  • Too many fields and subgrids slow the form down. Load fewer on the first tab.
  • A field that isn't on the form can't be edited there, however much the column exists in the table.
  • Header fields are shown above every tab, so only put the ones people really need on every view.
  • Forms reflow on narrow screens, so check the layout at phone width before you rely on three columns.

Try it in the demo

  1. Open the first accelerator and look at the header card.
  2. Switch tabs and compare sections with one, two and three columns.
  3. Compare labels beside the field with labels on top.