Lists and forms are how most real Dataverse data actually reaches a Power Pages site — both are configuration-driven, built from the same underlying views and forms concepts you already know from the Customization course.

Lists

A list is built on top of a Dataverse view and renders as a filterable, sortable, paginated grid on the page — the portal equivalent of opening a table’s grid in the model-driven app. Lists can include search, custom filtering options, and action buttons (like “Create New,” wired to a form).

Basic forms

A basic form renders a Dataverse form (or a configured subset of fields) for creating or editing a single record — directly reusing a form you’ve already built for the model-driven app, or a dedicated portal-specific form if the fields needed externally differ from the internal one.

Multistep forms

For longer processes (a multi-page application, a detailed intake form), multiple basic forms can be chained into a single guided, multistep wizard experience — each step can even write to a different table, useful for complex onboarding or application scenarios.

Why this reduces real development time so much. Because lists and forms are configuration on top of existing Dataverse views and forms, a portal page showing “my open cases” or “submit a new request” is often just a few configuration steps, not custom code — assuming the underlying table, view, and form are already sensibly designed. This is the single biggest reason Power Pages projects move faster than a custom-built external portal talking to the same data.