Study guide
8.1 Power Pages Lists, Basic Forms & Advanced Forms
Microsoft Power Platform Functional Consultant PL-200
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Dataverse Tables, Relationships & Core Columns
1.1 Dataverse Table Types, Properties & Ownership 1.2 Table Relationships & Cascading Rules 1.3 Column Types, Formats, Primary Keys & Alternate Keys 1.4 Rollup, Calculated & Formula Columns with Power Fx
2 Chapter 2: Dataverse Data Management & Governance
2.1 Dataverse Search, Quick Find & Relevance Indexing 2.2 Auditing Configuration & Log Management 2.3 Duplicate Detection Rules & Settings 2.4 Bulk Record Operations, Data Import, Export & Templates
3 Chapter 3: Dataverse Security Model & Access Control
3.1 Business Units, Ownership Models & Modern BU Matrix 3.2 Security Roles, Privileges & Depth Levels 3.3 Teams Architecture: Owner, Access, and Microsoft Entra (AAD) Group Teams 3.4 Column-Level Security & Hierarchy Security Models
4 Chapter 4: Model-Driven App Fundamentals & Information Architecture
4.1 Model-Driven App Design, Site Map Navigation & Modern App Designer 4.2 Form Types: Main, Quick Create, Quick View & Card Forms 4.3 View Configuration, System Views, Personal Views & Filters
5 Chapter 5: Advanced Model-Driven App Components & Custom Pages
5.1 Custom Pages & Modern Commanding with Power Fx 5.2 Form Component Controls & Specialized UX Elements 5.3 Embedding Canvas Apps in Model-Driven Forms 5.4 Embedding Power BI Reports, Dashboards & Tiles
6 Chapter 6: Canvas Apps Structure, Formulas & Data Operations
6.1 Canvas App Architecture, Screens, Containers & Controls 6.2 Power Fx Formulas, Delegation & Data Source Limits 6.3 Variables (Context, Global), Collections & State Management 6.4 Triggering Power Automate Cloud Flows from Canvas Apps
7 Chapter 7: Power Pages Site Design, Navigation & Content
7.1 Power Pages Design Studio & Site Structure 7.2 Power Pages Templates, Styling & Responsive Layouts 7.3 Web Pages, Navigation Menus & Content Snippets
8 Chapter 8: Power Pages Data Integration, Forms & Web Roles
8.1 Power Pages Lists, Basic Forms & Advanced Forms 8.2 Table Permissions, Web Roles & Page Access Security 8.3 External Identity Providers & Authentication Configuration
9 Chapter 9: Power Automate Cloud Flow Fundamentals & Triggers
9.1 Cloud Flow Types: Automated, Instant, Scheduled & Desktop Overview 9.2 Dataverse Connector Triggers & Operational Filters 9.3 Standard Connectors, Custom Connectors & Connection References
10 Chapter 10: Cloud Flow Actions, Expressions & Logic Controls
10.1 Logic Controls: Conditions, Switches, Apply to Each & Do Until Loops 10.2 Variables, Data Operations & Dynamic Content Manipulation 10.3 Power Automate Expression Language (WDL / Functions) 10.4 Error Handling, Configure Run After & Scope Controls
11 Chapter 11: Business Process Flows & Guided Processes
11.1 Business Process Flow Architecture, Stages, Steps & Data Steps 11.2 Branching Rules & Multi-Entity Business Process Flows 11.3 BPF Action Steps, Workflows & Cloud Flow Execution 11.4 BPF Security Roles, Order & Process Lifecycle
12 Chapter 12: Classic Workflows, Business Rules & Modern Logic Extensibility
12.1 Classic Dataverse Workflows: Real-Time vs. Background (Async) 12.2 Business Rules: Scope & Actions 12.3 Low-Code Plug-ins in Dataverse: Automated vs. Instant 12.4 Troubleshooting Automations, Run History & Analytics
13 Chapter 13: Power Platform Environment Architecture & Security
13.1 Environment Types: Default, Sandbox, Production, Trial, Developer 13.2 Environment Governance, Groups, Routing & Capacity Management 13.3 Data Loss Prevention (DLP) Policies & Connector Classifications
14 Chapter 14: Application Lifecycle Management (ALM) & Solutions
14.1 Unmanaged vs. Managed Solutions & Solution Layering Mechanics 14.2 Solution Components, Dependencies, Publishers & Prefixes 14.3 Exporting, Importing, Upgrading & Patches 14.4 Solution Checker, App Checker & ALM Best Practices
15 Chapter 15: Enterprise Interoperability & Service Integration
15.1 Exchange / Server-Side Synchronization & Email Integration 15.2 SharePoint & OneDrive Document Management Integration 15.3 Microsoft Word & Excel Document Templates
16 Chapter 16: Copilot, AI Capabilities & Exam Strategy
16.1 Copilot Studio & Generative AI across Power Platform 16.2 AI Builder Prebuilt & Custom Models in Apps and Flows 16.3 PL-200 Exam Strategy, Time Management & Question Analysis
8.1 Power Pages Lists, Basic Forms & Advanced Forms
Key Takeaways Explain This Topic AI
Power Pages Lists surface Dataverse views on website pages, supporting multi-view switching, text search, metadata column filtering, Excel downloads, and contextual row actions (View, Edit, Delete, Workflow).
Basic Forms render a single Dataverse model-driven form tab in Insert (create), Edit (update existing record via ID), or ReadOnly mode, with configurable post-submission actions and file attachments.
Basic Form Metadata enables field-level customizations including control styling (toggles, radio buttons, code editors), automatic value pre-population, forced values on save, and inline subgrid management.
Advanced Forms (Multistep Forms) deliver wizard-style multi-screen experiences utilizing four distinct step types: Load Form, Condition (branching logic), Redirect, and Load Tab.
Advanced Form session state is tracked in the adx_webformsession table, allowing users to save progress, navigate via Previous/Next buttons, view visual progress indicators, and branch dynamically based on field evaluations.
Last updated: August 2026
Power Pages Lists, Basic Forms & Advanced Forms
Microsoft Power Pages allows organizations to securely extend their Microsoft Dataverse data, business logic, and processes to external audiences—including customers, partners, citizens, and suppliers—over the web. Rather than building custom database endpoints or bespoke web components, Power Pages provides low-code, metadata-driven components that directly render Dataverse views and forms.
For the PL-200: Microsoft Power Platform Functional Consultant exam, you must master the architecture, capabilities, and configuration options of Lists , Basic Forms , and Advanced Forms (Multistep Forms) , including how to handle data operations, form modes, file attachments, field overrides, and multi-step wizard logic.
1. Power Pages Lists (Entity Lists)
A List (historically known as an Entity List) is a metadata-driven data-binding component that queries Dataverse and surfaces records in a responsive, tabular grid on a Power Pages web page. Lists eliminate the need to write custom HTML tables, CSS styling, or JavaScript data-fetching calls. +-----------------------------------------------------------------------------------+
- | POWER PAGES LIST ARCHITECTURE |
- | |
- | [DATAVERSE TABLE] |
- | └── Active Views (Columns, Sorting, Filter Criteria) |
- | │ |
- | ▼ |
- | [POWER PAGES LIST COMPONENT] |
- | ├── View Selection & Multi-View Switcher Dropdown |
- | ├── Search Box (Text Search across view columns) |
- | ├── Metadata Column Filtering (Dropdowns, Checkboxes, Date Ranges) |
- | ├── Download to Excel (Export view data) |
- | └── Row / Grid Actions (Create, View Details, Edit, Delete, Run Workflow) |
- | │ |
- | ▼ |
- | [WEB PAGE RENDERING] ───> Subject to Table Permissions & Web Roles |
- +-----------------------------------------------------------------------------------+
- List Configuration Capabilities
When configuring a List in the Power Pages Design Studio or the Power Pages Management app, functional consultants configure several core capabilities:
Dataverse View Integration & Multi-View Switcher:
A List binds to one or more system or public views defined on a Dataverse table (e.g., "Active Support Tickets", "Resolved Cases").
When multiple views are enabled, Power Pages automatically displays a view-switcher dropdown at the top of the grid, allowing external users to toggle between different filtered views.
Column names, display widths, and default sort orders are inherited directly from the underlying Dataverse view configuration.
Search and Column Filtering:
Search Box: Enabling search places a text input box above the grid that performs wildcard/contains queries across all text attributes included in the view.
Metadata Filter Engine: Consultants can configure structured filter controls (vertical or horizontal filter panels) enabling users to refine records using single-select dropdowns, multi-select checkboxes, date range pickers, or dynamic filters linked to the logged-in user's account.
Data Export (Download to Excel):
Enabling the Download action renders an "Export to Excel" button.
When clicked, Power Pages dynamically queries Dataverse respecting the active view filter, search terms, and the user's active Table Permissions , outputting an .xlsx workbook.
OData Feed Integration:
Lists can expose their underlying Dataverse dataset as an authenticated or anonymous OData v4 REST feed, allowing client-side JavaScript or external services to query the data programmatically.
Grid Item & View Actions
Lists support contextual actions divided into Item Actions (executed against a specific selected row) and View / Global Actions (executed at the list level):
Action Type Action Name Configuration & Behavior
View / Global Create Record Renders a "Create" button above the grid. Opens a target Web Page or Basic Form (in Insert mode) or launches a modal dialog to create a new row.
View / Global Download Exports the currently filtered grid dataset to Microsoft Excel.
Item Action Details / View Opens a target Web Page or Basic Form in ReadOnly mode, passing the record GUID via URL query string (e.g., ?id=a1b2c3d4-... ).
Item Action Edit Opens a target Web Page or Basic Form in Edit mode, passing the record GUID to allow data modification.
Item Action Delete Prompts the user with a confirmation modal and permanently deletes the selected Dataverse record (requires Delete table privilege).
Item Action Run Workflow Invokes a classic Dataverse On-Demand Workflow against the selected record row.
Item Action Trigger Cloud Flow Invokes a Power Automate Cloud Flow via the Power Pages Cloud Flows integration/Web API.
Important
Query String Parameter Binding: When configuring row actions (Edit/Details), Power Pages passes the record primary key as a query string parameter. By default, the parameter name is id (e.g., https://contoso.powerappsportals.com/ticket-details/?id=7c9e6679-7425-46d8-9189-9831f2378912 ). The target Basic Form on that page must be configured to look for the matching record ID parameter.
2. Basic Forms (Entity Forms)
A Basic Form (formerly known as an Entity Form) is a metadata-driven component used to render a single tab of a Dataverse model-driven form on a Power Pages website. It handles data binding, validation, subgrids, note attachments, and record persistence without manual HTML/JavaScript coding. +-----------------------------------------------------------------------------------+
- | BASIC FORM ARCHITECTURE & MODES |
- | |
- | [DATAVERSE MODEL-DRIVEN FORM] ───> Select Table & Specific Form Tab |
- | │ |
- | ▼ |
- | [BASIC FORM MODES] |
- | ├── INSERT: Creates new record (No Record ID required in URL) |
- | ├── EDIT: Updates existing record (Requires Record ID query string) |
- | └── READONLY: Displays data without editing (Requires Record ID query string) |
- | │ |
- | ▼ |
- | [FORM PROCESSING & HOOKS] |
- | ├── Field Validation & Business Rules Enforcement |
- | ├── Basic Form Metadata (Field Overrides, Prepopulate, Force Values) |
- | ├── Attachments (Dataverse Notes vs. Azure Blob Storage) |
- | └── On Success Action: Show Message / Redirect to Web Page / Redirect URL |
- +-----------------------------------------------------------------------------------+
- Form Modes
A Basic Form must be configured in one of three operational modes:
Insert Mode:
Used for new record creation (e.g., a "Contact Us" inquiry or "Submit New Warranty Claim" form).
Does not require a record ID in the URL.
Generates a new Dataverse record GUID upon successful submission.
Edit Mode:
Used for updating existing records (e.g., updating a customer profile or editing a support case).
Requires a record identifier, typically passed through a URL query string parameter (such as id ), session state, or mapped to the current logged-in Contact.
ReadOnly Mode:
Displays existing record attributes in disabled, non-editable controls.
Used for confirmation screens, historical order reviews, or static policy inspection.
Post-Submission & Success Behaviors
When an external user submits a Basic Form, Power Pages can execute one of three configurable On Success actions:
Display Success Message: Displays a configurable text banner (e.g., "Thank you! Your application has been received.") while remaining on the same page.
Redirect to Web Page: Automatically navigates the user to another internal site page (e.g., routing to an "Application Summary" page or returning to the List grid).
Redirect to URL: Navigates the user to an absolute external URL or internal relative path.
File Attachments & Storage Options
Basic Forms can capture document and image uploads from portal visitors using two architectural backends:
Dataverse Notes (Annotations): Uploaded files are stored directly in Dataverse file storage as annotation records linked regarding the primary record. Consultants can configure maximum file size limits (up to Dataverse limits), restrict file MIME types/extensions (e.g., .pdf , .docx , .png ), and enable multi-file uploads.
Azure Blob Storage Integration: For high-volume file scenarios or large media files (up to several gigabytes), Power Pages can be configured with Azure Blob Storage. Files are streamed directly to an Azure Storage container, leaving a lightweight metadata pointer in Dataverse.
3. Basic Form Metadata Customization
While a Basic Form inherits layout and fields from a Dataverse model-driven form, enterprise portals often require web-specific behavioral modifications. Basic Form Metadata provides granular overrides applied to specific fields, sections, tabs, subgrids, or notes on the form. +-----------------------------------------------------------------------------------+
- | BASIC FORM METADATA CAPABILITIES |
- | |
- | [FIELD OVERRIDES] |
- | ├── Label Customization (Rename field specifically for portal users) |
- | ├── Control Styles (Render OptionSet as Radio Buttons; Boolean as Toggle) |
- | ├── Validation (Custom regex, mandatory overrides, error messages) |
- | └── Description / Tooltip (Inject helper text above or below input) |
- | |
- | [AUTOMATION & VALUES] |
- | ├── Prepopulate Field: On Load set to Current Contact / Current Date / Value |
- | └── Set Value On Save: Force statuscode, owner, or system flag upon submit |
- | |
- | [COMPOSITE CONTROLS] |
- | ├── Subgrids: Enable inline create/edit/delete modal dialogs for child rows |
- | └── Timeline / Notes: Configure customer attachment and comment permissions |
- +-----------------------------------------------------------------------------------+
- Key Basic Form Metadata Types
Attribute (Field) Overrides:
Label Override: Modifies the field's display label on the web page without changing the underlying Dataverse column name.
Control Style Overrides: Changes how a column renders in the browser:
Single-line text rendered as Password , Email , or Code Editor (HTML/JSON).
Option Set (Choice) rendered as a Vertical/Horizontal Radio Button Group .
Two Options (Boolean) rendered as a Toggle Switch or Checkbox .
Custom Validation: Adds regular expression validation (e.g., postal code or tax ID format) with custom localized error messages.
Prepopulate Field (On Form Load):
Automatically sets a field value when the form opens:
Current Portal User: Populates a lookup column with the logged-in Contact record.
Current User's Account: Populates a lookup column with the logged-in user's parent Account.
Current Date/Time: Populates date fields with Today or Now() .
Constant Value: Populates default text, numbers, or option set keys.
Set Value On Save (On Form Submit):
Silently assigns or overrides field values when the user clicks Submit, regardless of form inputs.
Common pattern: Automatically setting statuscode to "Submitted", assigning a routing queue, or recording submission timestamps.
Subgrid Metadata Configuration:
When a subgrid is embedded on the model-driven form, Basic Form Metadata allows consultants to enable interactive subgrid actions:
Create: Opens an Insert modal to add related child records.
Edit / Details: Opens an Edit modal for selected child rows.
Delete: Enables deletion of related rows.
4. Advanced Forms (Multistep Forms)
When a business process requires capturing extensive data across a guided, multi-page wizard with dynamic branching and step-by-step validation, consultants use Advanced Forms (formerly known as Web Forms or Multistep Forms). +-----------------------------------------------------------------------------------+
- | ADVANCED FORM (MULTISTEP) WORKFLOW |
- | |
- | [STEP 1: Load Form] ───> Basic Customer Information |
- | │ |
- | ▼ |
- | [STEP 2: Condition] ───> Is Claim Amount > $10,000? |
- | ├── [TRUE] ───> [STEP 3A: Load Form] High-Value Asset Verification |
- | └── [FALSE] ───> [STEP 3B: Load Form] Standard Fast-Track Submission |
- | │ │ |
- | └─────────────┬──────────────┘ |
- | ▼ |
- | [STEP 4: Redirect] ───> Navigate to Confirmation Web Page |
- +-----------------------------------------------------------------------------------+
- The Four Advanced Form Step Types
An Advanced Form is composed of a sequenced collection of Advanced Form Steps . Each step is configured as one of four specific types:
Step Type Function Common Scenario
1. Load Form Renders a single tab of a Dataverse model-driven form (Insert, Edit, or ReadOnly mode). Captures or displays field data. Gathering contact info, capturing order details, or presenting review summary.
2. Condition Evaluates a logical expression against field values or session state without rendering UI. Branches to different next steps based on True or False outcomes. Routing users to different question sets based on age, territory, product type, or claim value.
3. Redirect Programmatically navigates the user to an internal Power Pages Web Page or an external URL. Forwarding to a payment gateway, document download page, or final thank-you screen.
4. Load Tab Legacy step type that displays a specific tab from the parent form. (Modern practice prefers standard Load Form steps). Legacy portal migration and backward compatibility.
Session State & User Experience
Advanced Forms include built-in state management and UI navigation features:
Session State Storage ( adx_webformsession ): The portal engine automatically records step progression in Dataverse. If a user closes their browser or loses connectivity, they can resume their application at the exact step where they left off.
Progress Indicators: Advanced Forms provide out-of-the-box visual indicators displayed at the top of the wizard:
- Title / Step Name List
- Numeric Step Count (e.g., "Step 2 of 5")
- Progress Bar (percentage completed)
Navigation Controls: Supports configurable Next , Previous , and Submit buttons. Enabling the "Previous" button allows users to navigate back and modify earlier responses without corrupting Dataverse record state.
Save and Return Later: Can be enabled to allow users to save incomplete drafts and receive a resume link.
Cross-Step Record Association & Reference Mappings
In multi-step wizards, Step 1 typically creates a parent record (e.g., an Application), while subsequent steps either update that record or create related child records (e.g., Applicant Dependents, Uploaded Documents):
Current Step Record Source: Each step defines where its record originates—either Create New (Insert) , Result of Previous Step , Query String (ID) , or Current Portal User's Record .
Associate Current Portal User: Steps can automatically bind the logged-in Contact as the record creator or lookup owner on step completion.
5. Comparison: Lists vs. Basic Forms vs. Advanced Forms
Architectural Dimension Power Pages List Basic Form Advanced Form (Multistep)
Primary Purpose Displaying tabular Dataverse views Single-screen record CRUD Guided multi-screen wizards & branching
Dataverse Binding Dataverse Public / System Views Single Tab of Model-Driven Form Multiple Form Tabs across one or more tables
CRUD Operations Read / Filter / Export / Row Triggers Create (Insert), Update (Edit), View (ReadOnly) Multi-table Create, Update, and Conditional Branching
State Management Stateless (URL / Grid Search) Stateless (Single HTTP POST) Stateful ( adx_webformsession persistence)
Conditional Logic View filter criteria & metadata filters Basic Form Metadata / Client JavaScript Native Condition Steps (No-code branching)