Skip to content
Tutorials Center
My learning

Topics

Lesson 20 of 38 ยท Model-driven Apps

Forms, Views and Columns

Learn the form types, tabs, sections and views of model-driven Power Apps: main forms, quick create, view filters, sorting and how columns reach the screen.

Every row in a model-driven app is shown through a form and every list through a view. Getting these two right is most of the work of a good model-driven app: a clear form lets people enter data fast, and a well-filtered view lets them find the right rows without searching.

The designer is a visual editor, so this lesson describes what you click and what each setting does, then uses stand-ins to show the logic behind views.

Form types

Open a table in the maker portal (Tables, then pick the table, then Forms). You will see several form types:

  • Main form: the full editing form, shown when you open a row. Can have tabs, sections, a header and a business process flow bar.
  • Quick create form: a short slide-in form for adding a row from anywhere (the + New button).
  • Quick view form: a read-only mini form embedded in another table's form (for example, show the customer's phone on an order).
  • Card form: a compact layout used in lists on small screens.

A table can have several main forms; users with different roles can be assigned different ones.

Form structure: tabs, sections, components

A main form is organised like this:

  1. Header: key fields that stay visible at the top.
  2. Tabs: major groupings (General, Details, Timeline).
  3. Sections: blocks of columns inside a tab, arranged in 1 to 4 columns.
  4. Components: a column control, a subgrid (a view of related rows), a quick view, a timeline, a map or an embedded canvas app.

In the form designer you drag columns from the Table columns panel into sections, set Display name, Required and Read-only in the properties, and choose a component for a column (for example, show a choice column as a dropdown or as a set of radio buttons).

Put the three or four most important columns in the header. People then see status, owner and key dates while scrolling a long form.

Views

A view is a saved query: which columns, which rows, in which order. Open the table and choose Views. The system provides several: Active ..., Inactive ..., and Quick Find ... (the search view). You can create public views for everyone and users can make personal views.

In the view designer you set:

  • Columns to show (and their width).
  • Sort by one or two columns.
  • Filter conditions, for example Status equals Active and Created On in last 30 days.
  • Quick Find search columns for the search box.

A view is a saved query

Filter Which rows
Sort In what order
Columns What to show

Same table, many views.

1 / 2

A view as a query: a stand-in

A view is conceptually filter, sort, project. This stand-in runs that idea on sample data. Dataverse runs the real thing on the server.

JS Stand-in: a view is filter + sort + columns

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Notice that the same data can back many views. Views never change data; they only select and arrange it.

Required, business-required and read-only

Each column on a form can be:

  • Optional: users may leave it empty.
  • Business required: a red asterisk; the form refuses to save until it has a value.
  • Business recommended: a blue plus sign; a hint only.
  • Read-only (locked): shown but not editable on this form.

These settings are per form, not per column definition. The column's own Required setting in the table is stricter: it makes the column required everywhere, including data imports and API calls. Prefer the table-level setting for rules that must always hold, and the form-level setting for rules that depend on context. (Business rules, covered in Business Rules and Commands, can toggle these dynamically.)

Checking required columns: a stand-in

JS Stand-in: a form's save validation

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Practical tips

  • Keep the main form to what staff need on most days; move rarely used columns to a second tab.
  • Use subgrids to show related rows (an account's contacts) so users do not need to navigate away.
  • Limit views to the columns people read; fewer columns load faster.
  • Hide the Created By and system columns unless they are part of the process.
  • Always Save and publish after changing forms: unpublished changes are not visible to users.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which form type is a short slide-in used for adding a row from anywhere?

    The quick create form opens from the + New button and captures only essential columns.
  2. 2. What is a view?

    Views never change data. They are saved queries over one table.
  3. 3. Where do you put columns so they stay visible while scrolling a long form?

    Header columns stay visible at the top of the main form.
  4. 4. Which setting is stricter: form-level business required or table-level required?

    A table-level required column is enforced everywhere; a form setting applies only to that form.

Summary

  • Main, quick create, quick view and card forms serve different jobs; forms have header, tabs, sections and components.
  • Views are saved queries: filter, sort and choose columns; many views can share one table.
  • Required settings exist at form and table level; the table level is stricter.
  • Save and publish for changes to take effect.

Next: Business Rules and Commands