Skip to main content

List Forms

A list form is the new, edit, and display experience that opens when someone adds or opens a list item. Out of the box it shows your columns, but modern SharePoint lets you shape it: reorder and hide columns, show or hide fields based on a conditional formula, and add custom headers, footers, and body text. For straightforward data entry this no-code form is often all you need. When requirements grow - branching logic, rich layout, connected data - you can switch the form to Power Apps.
Related
Approvals, List, Rules

Common Use Cases

  • Cleaner entry: hiding system or rarely used columns from the form
  • Conditional fields: showing a field only when another value applies
  • Guided forms: adding instructions in a header or body
  • Required data: combining the form with required columns
  • Tailored display: a different look for new, edit, and view
  • Branching needs: moving to Power Apps for complex logic

Benefits

  • No code: the built-in form is configured, not built
  • Show and hide: control which columns appear
  • Conditional logic: fields appear based on a formula
  • Custom text: headers, footers, and body messaging
  • Consistent: everyone enters data the same way
  • Upgrade path: Power Apps available when needed

Details

  • Feature Category: Sites & Navigation

How It Works

  • Edit form: the form designer opens from the new or edit view
  • Reorder and hide: drag columns or toggle visibility
  • Conditional formula: a rule decides when a field shows
  • Header, body, footer: custom content around the fields
  • Save the layout: the configured form applies to the list
  • Customize in Power Apps: switch the form to a Power Apps form

Limits and Nuances

  • Conditional logic is basic: simple show or hide, not full branching
  • One form set: new, edit, and display share the configuration
  • Power Apps for complexity: advanced needs leave the native form
  • Column types: some types offer limited form control
  • Not pixel design: layout options are structured, not free-form
  • Validation separate: field rules come from column validation

Common Questions About List Forms

What is a list form in SharePoint?

A list form is the new, edit, and display experience that opens when someone creates or opens an item in a list or library. Modern SharePoint lets you configure it without code: reorder and hide columns, show or hide fields with a conditional formula, and add custom headers, footers, and body text. For richer needs, the form can be switched to Power Apps.

Can I hide columns on the form?

Yes. The form designer lets you show or hide individual columns, so the form presents only the fields users should fill in. This is handy for tucking away system columns or fields that are set automatically. Hiding a column on the form does not delete it from the list; it simply keeps the entry experience focused and uncluttered.

How do conditional show and hide rules work?

You can write a conditional formula on a column so the field appears only when another column has a particular value. For example, a details field can stay hidden until a status of Other is chosen. The logic is intentionally simple – show or hide based on a condition – which covers many forms without needing the full branching power of Power Apps.

When should I use Power Apps instead of the built-in form?

Stay with the native form for ordinary data entry, since it is no-code and quick to configure. Move to Power Apps when you need complex branching, rich layout, connected data sources, or custom controls beyond what the built-in form offers. Switching is a deliberate step up in capability and maintenance, so it is best reserved for forms that genuinely require it.

Can I add instructions to a list form?

Yes. The form supports custom header, body, and footer content, which is the place to add instructions, links, or context that helps people fill the form out correctly. A short note at the top often reduces errors more than any validation rule, because it guides users before they start rather than correcting them afterward.

Are the built-in forms enough for most lists?

For everyday tracking, usually yes. Greg Zelfond, the consultant behind LookBook 365, configures the native form – hiding noise, adding a little guidance, and using conditional fields – before ever reaching for Power Apps. Keeping simple lists on the built-in form means less to maintain and a faster experience, with Power Apps held in reserve for the genuinely complex cases.