Dataverse Integration">

Dataverse Integration

What is Microsoft Dataverse?

Microsoft Dataverse is the data platform used across Power Platform to store and manage business data. In Power Pages, Dataverse acts as the backend data source for website forms, lists, and other data-driven components.

Microsoft Learn states that Power Pages documentation includes areas for connecting to Dataverse, using the data workspace, adding lists to pages, adding basic forms to pages, adding multistep forms, securing data with table permissions, and creating, updating, and viewing Dataverse information. [2](https://learn.microsoft.com/en-us/power-pages/)

Dataverse Concept	Simple Meaning	Power Pages Example
Table	Stores a type of business data	Customer Request, Course Registration, Application
Column	Stores one piece of information in a table	Name, Email, Request Type, Status
Row / Record	One complete data entry in a table	One submitted enquiry or registration
View	Defines selected rows and columns to display	Show only active requests
Form	Defines how users create or update records	Submit a service request form

Why Dataverse Integration is Important in Power Pages

A Power Pages website becomes much more powerful when it is connected to Dataverse. Without data integration, the website may only show static content. With Dataverse integration, users can submit information, view records, update records, and interact with real business data.

Microsoft Learn explains that in a Power Pages Dataverse tutorial, learners build a web application that allows users to create, read, and update Dataverse records. The same tutorial lists activities such as creating a Dataverse table, creating a Dataverse view, creating a Dataverse form, configuring table permissions, adding a list to a page, and adding pages with forms for creating and viewing or editing records. [1](https://learn.microsoft.com/en-us/power-pages/getting-started/tutorial-dataverse-website)

Dataverse stores structured business data for the website.
Power Pages forms can create or update Dataverse records.
Power Pages lists can display Dataverse records.
Dataverse views control which rows and columns are displayed in lists.
Dataverse forms control how records are created or edited through the website.
Table permissions protect Dataverse data exposed through Power Pages.

How Power Pages Connects with Dataverse

Power Pages connects with Dataverse mainly through the Data workspace, Dataverse tables, Dataverse views, Dataverse forms, lists, forms, and table permissions.

Microsoft Learn states that with the Data workspace, makers can visualize and manage business data for the site with tables, forms, and lists. It also states that all data and changes are stored in Microsoft Dataverse. [3](https://learn.microsoft.com/en-us/power-pages/getting-started/use-data-workspace)

Power Pages Website
        |
        +-- Page with List
        |       |
        |       v
        |   Dataverse View
        |
        +-- Page with Form
                |
                v
            Dataverse Form
                |
                v
        Microsoft Dataverse Table

This diagram is a learning representation based on Microsoft Learn’s explanation that Data workspace uses tables, forms, and lists and stores data and changes in Dataverse. [3](https://learn.microsoft.com/en-us/power-pages/getting-started/use-data-workspace)

Data Workspace in Power Pages

The Data workspace is the main low-code area in Power Pages for managing Dataverse data structures used by the site.

Microsoft Learn explains that the Data workspace allows makers to create and edit tables for the site, and create new or edit existing model-driven forms and views. It also explains that makers create basic forms, advanced forms, and lists by using forms and views created in the Data workspace. [3](https://learn.microsoft.com/en-us/power-pages/getting-started/use-data-workspace)

Data Workspace Area	Purpose	Power Pages Use
Tables	Create or manage Dataverse tables	Create a Registration table or Request table
Columns	Add fields to store specific values	Add Name, Email, Status, Request Date
Views	Define which records and columns appear in lists	Show active requests or submitted applications
Forms	Define how users create or edit records	Create a contact form or service request form
Lists	Display Dataverse records on pages	Show user requests or registration records

Dataverse Tables

A Dataverse table stores a specific type of business information. In a Power Pages site, tables are commonly used to store data submitted by external or internal users through website forms.

Microsoft Learn explains that in the Dataverse tutorial for Power Pages, a table is used to store information about specific objects. It gives examples such as a scholarship, an application, or a company. It also explains that a table is made up of columns, where a column is a specific piece of information about the object, such as name, description, application date, or a choice of options. [1](https://learn.microsoft.com/en-us/power-pages/getting-started/tutorial-dataverse-website)

Business Scenario	Suggested Dataverse Table	Example Columns
Customer enquiry website	Customer Enquiry	Name, Email, Enquiry Type, Message, Status
Course registration website	Course Registration	Learner Name, Email, Course Name, Registration Date
Service request portal	Service Request	Request Title, Category, Description, Priority, Status
Application portal	Application	Applicant Name, Application Type, Submitted Date, Review Status

The table examples are teaching examples based on Microsoft Learn’s explanation that Dataverse tables store information about business objects and contain columns for specific pieces of information. [1](https://learn.microsoft.com/en-us/power-pages/getting-started/tutorial-dataverse-website)

Dataverse Views

A Dataverse view defines which rows and columns should be shown from a table. In Power Pages, views are important because lists use views to display records on website pages.

Microsoft Learn explains that a Dataverse view is a type of query used to display specific rows and columns of data from a Dataverse table. It also states that when creating a view, makers specify criteria such as which columns to show, how records are sorted, and how rows are filtered. [1](https://learn.microsoft.com/en-us/power-pages/getting-started/tutorial-dataverse-website)

Microsoft Learn also states that views are a foundation of the list component that can be added to pages. [3](https://learn.microsoft.com/en-us/power-pages/getting-started/use-data-workspace)

View Example	Purpose	Possible Filter
Active Requests	Show open service requests	Status equals Active
Upcoming Events	Show future event records	Event date is in the future
Submitted Applications	Show submitted application records	Status equals Submitted
Approved Registrations	Show approved registration records	Registration Status equals Approved

Dataverse Forms

A Dataverse form defines how users create, view, or edit a Dataverse record. In Power Pages, forms are used when website visitors need to submit or update information.

Microsoft Learn explains that the Forms tab displays forms used in basic forms embedded in the site and other forms in the environment associated with the table. It also explains that makers use the Data workspace to create and modify Dataverse table forms directly in the Power Pages design studio. [4](https://learn.microsoft.com/en-us/power-pages/configure/data-workspace-forms)

Microsoft Learn further states that the form designer provides a modern WYSIWYG authoring experience and that forms can be used to add a form component to a page on the site. [4](https://learn.microsoft.com/en-us/power-pages/configure/data-workspace-forms)

Form Type	Purpose	Example
Create Form	Allows users to submit a new record	Submit a new enquiry
Edit Form	Allows users to update an existing record	Update application details
Read-only Form	Allows users to view record details	View service request status
Multistep Form	Breaks a long form process into multiple steps	Application process with personal, document, and confirmation stages

The examples are educational. Microsoft Learn explicitly supports creating and modifying forms in Data workspace and using those forms as form components on Power Pages pages. [4](https://learn.microsoft.com/en-us/power-pages/configure/data-workspace-forms)

Lists in Power Pages

A list in Power Pages displays Dataverse records on a page. Lists are commonly used when users need to browse submitted records, view request status, or open a record for more details.

Microsoft Learn’s Dataverse tutorial includes adding a list to a page and updating the list so users can navigate to pages to create records and view or edit records. [1](https://learn.microsoft.com/en-us/power-pages/getting-started/tutorial-dataverse-website)

Microsoft Learn also states that views are the foundation of the list component that can be added to pages. [3](https://learn.microsoft.com/en-us/power-pages/getting-started/use-data-workspace)

Dataverse Table
        |
        v
Dataverse View
        |
        v
Power Pages List
        |
        v
Website User views records

List Scenario	Dataverse Source	User Experience
My Requests	Service Request table view	User views submitted requests
Course Registrations	Registration table view	Organizer reviews submitted registrations
Applications	Application table view	User checks application records

CRUD Operations in Power Pages

CRUD means Create, Read, Update, and Delete. In Power Pages, Dataverse integration often focuses on allowing users to create, read, and update Dataverse records through pages, lists, and forms.

Microsoft Learn’s Power Pages Dataverse tutorial specifically says learners build a web application that allows users to create, read, and update Dataverse records. The same tutorial includes creating a Dataverse table, view, and form, configuring table permissions, adding a list to a page, and adding pages with forms to create and view or edit records. [1](https://learn.microsoft.com/en-us/power-pages/getting-started/tutorial-dataverse-website)

CRUD Operation	Meaning	Power Pages Example
Create	Add a new record	User submits a registration form
Read	View records	User views a list of submitted requests
Update	Edit an existing record	User updates application information
Delete	Remove a record	Only allow if the business scenario and permissions require it

The Create, Read, and Update examples are directly aligned with Microsoft Learn’s tutorial scope. Delete is included as a general CRUD concept, but learners should enable it only when the business and permission design requires it. [1](https://learn.microsoft.com/en-us/power-pages/getting-started/tutorial-dataverse-website)

Table Permissions for Dataverse Integration

Dataverse integration must be secured carefully because website users may be external users. Power Pages does not simply expose Dataverse records automatically.

Microsoft Learn states that access to Dataverse records is automatically restricted in Power Pages when using forms, lists, Liquid, the Portals Web API, and other components accessing Dataverse tables. To allow access to Dataverse records, makers need to configure table permissions and associate those table permissions to web roles. [5](https://learn.microsoft.com/en-us/power-pages/security/table-permissions)

Security Item	Purpose	Example
Table Permission	Controls access to a Dataverse table	Allow Customer role to read Service Request records
Web Role	Groups users for access control	Customer, Partner, Manager, Administrator
Privilege	Defines the allowed operation	Read, Create, Write, Delete
Access Type	Defines the record scope	Global, Contact, Account, Self

Table Permission Access Types

Microsoft Learn explains that the design studio shows four table permission access types: Global access, Contact access, Account access, and Self access. [5](https://learn.microsoft.com/en-us/power-pages/security/table-permissions)

Access Type	Meaning	Example Use
Global access	Applies selected table permission and privileges to users from selected roles for all records.	Administrator can view all records.
Contact access	Applies selected table permission and privileges to users associated to the signed-in user.	Customer views records related to their contact.
Account access	Applies selected table permission and privileges to users associated to the signed-in user’s account.	Partner user views account-related records.
Self access	Applies selected table permission and privileges only for the user’s own Contact record.	User updates their own profile information.

The access type meanings are based on Microsoft Learn’s table permissions documentation; the examples are beginner-friendly illustrations of those meanings. [5](https://learn.microsoft.com/en-us/power-pages/security/table-permissions)

Dataverse Integration Architecture

A typical Power Pages and Dataverse integration architecture contains website pages, lists, forms, Dataverse views, Dataverse forms, Dataverse tables, table permissions, and web roles.

Website User
   |
   v
Power Pages Page
   |
   +-- List Component
   |       |
   |       v
   |   Dataverse View
   |
   +-- Form Component
           |
           v
       Dataverse Form
           |
           v
Dataverse Table and Records
           |
           v
Table Permissions + Web Roles

This architecture is a teaching representation based on Microsoft Learn’s explanation that Power Pages can use Dataverse tables, forms, views, lists, and table permissions for creating, reading, updating, and securing Dataverse information on pages. [1](https://learn.microsoft.com/en-us/power-pages/getting-started/tutorial-dataverse-website)[3](https://learn.microsoft.com/en-us/power-pages/getting-started/use-data-workspace)[5](https://learn.microsoft.com/en-us/power-pages/security/table-permissions)

Example: Course Registration Website with Dataverse

A course registration website can use Dataverse to store learner registrations. Visitors or authenticated users can submit a registration form, and organizers can view the records through a list or back-office app.

Course Registration Page
        |
        v
Registration Form
        |
        v
Dataverse Course Registration Table
        |
        v
Registration List / Organizer View

Component	Purpose
Course Registration Table	Stores submitted registration records.
Registration Form	Allows users to submit registration details.
Registration View	Defines which registration columns appear in the list.
Registration List	Displays submitted registration records.
Table Permissions	Controls which users can create, read, or update registration records.

This scenario is a teaching example based on Microsoft Learn’s documented pattern of using Dataverse tables, views, forms, lists, and table permissions in Power Pages. [1](https://learn.microsoft.com/en-us/power-pages/getting-started/tutorial-dataverse-website)[5](https://learn.microsoft.com/en-us/power-pages/security/table-permissions)

Example: Customer Service Request Portal

A customer service request portal can use Dataverse to store customer requests. Customers can submit new requests, view submitted requests, and update details if allowed by permissions.

Customer logs in
        |
        v
Submit Service Request Form
        |
        v
Dataverse Service Request Table
        |
        v
My Requests List
        |
        v
View or Edit Request Details

Dataverse Object	Example Content
Service Request Table	Request title, category, description, status, submitted date
My Requests View	Columns such as request title, status, and submitted date
Request Form	Fields needed for creating or editing a request
Table Permission	Controls which request records the user can access

This scenario is a learning example based on Microsoft Learn’s explanation that Power Pages users can create, read, and update Dataverse records and that table permissions are required to allow Dataverse record access. [1](https://learn.microsoft.com/en-us/power-pages/getting-started/tutorial-dataverse-website)[5](https://learn.microsoft.com/en-us/power-pages/security/table-permissions)

Integration with Other Power Platform Services

Dataverse data used in Power Pages can also be used by other Power Platform services.

Microsoft Learn states that information tracked in Dataverse can be accessed by other Power Platform services such as Power Apps, Power Automate, or Power BI. [1](https://learn.microsoft.com/en-us/power-pages/getting-started/tutorial-dataverse-website)

Power Platform Service	How It Can Work with Dataverse Data
Power Pages	Displays and collects Dataverse data through pages, forms, and lists.
Power Apps	Can use the same Dataverse data for business applications.
Power Automate	Can use Dataverse data in workflows and automation.
Power BI	Can use Dataverse data for reporting and analytics.

The table is based on Microsoft Learn’s statement that Dataverse information can be accessed by Power Apps, Power Automate, and Power BI, alongside Power Pages. [1](https://learn.microsoft.com/en-us/power-pages/getting-started/tutorial-dataverse-website)

Dataverse Integration Design Process

A good Dataverse integration should be designed carefully before building forms and lists. The maker should identify the data model, pages, user roles, permissions, and user actions.

Identify business data
        |
        v
Create Dataverse table and columns
        |
        v
Create Dataverse views
        |
        v
Create Dataverse forms
        |
        v
Add lists and forms to Power Pages
        |
        v
Configure table permissions
        |
        v
Test create, read, and update scenarios

This workflow is based on Microsoft Learn’s Power Pages Dataverse tutorial, which includes creating a table, view, form, configuring table permissions, adding a list, and adding pages with forms to create and view or edit records. [1](https://learn.microsoft.com/en-us/power-pages/getting-started/tutorial-dataverse-website)

Dataverse Integration Checklist

Checklist Area	Question to Ask
Business Data	What information should the website collect or display?
Table Design	Which Dataverse tables are required?
Columns	Which fields are needed for each table?
Views	Which rows and columns should appear in website lists?
Forms	Which forms are needed for create, read-only, or edit scenarios?
Lists	Where should users view records on pages?
Permissions	Which table permissions and web roles are required?
Testing	Can users create, read, and update records as expected?

This checklist is a teaching tool based on Microsoft Learn’s documented Dataverse integration concepts for Power Pages: tables, views, forms, lists, and table permissions. [1](https://learn.microsoft.com/en-us/power-pages/getting-started/tutorial-dataverse-website)[3](https://learn.microsoft.com/en-us/power-pages/getting-started/use-data-workspace)[5](https://learn.microsoft.com/en-us/power-pages/security/table-permissions)

Best Practices for Dataverse Integration

Design the Dataverse table structure before creating website pages.
Create meaningful columns that match the business process.
Use views to control which records and columns appear in lists.
Use forms to control how users create or edit records.
Configure table permissions before exposing Dataverse data through lists or forms.
Associate table permissions with the correct web roles.
Test the website using different user roles and access scenarios.
Use Dataverse as a shared data source when Power Apps, Power Automate, or Power BI also need the same data.

These recommendations are based on Microsoft Learn’s Power Pages Dataverse tutorial, Data workspace documentation, and table permissions documentation. [1](https://learn.microsoft.com/en-us/power-pages/getting-started/tutorial-dataverse-website)[3](https://learn.microsoft.com/en-us/power-pages/getting-started/use-data-workspace)[5](https://learn.microsoft.com/en-us/power-pages/security/table-permissions)

Common Mistakes Beginners Make

Creating website pages before planning the Dataverse data model.
Adding forms without confirming which Dataverse table and form should be used.
Adding lists without creating a proper Dataverse view.
Forgetting to configure table permissions for Dataverse records.
Assuming authenticated users automatically have access to all Dataverse data.
Using too many fields on a form and making the user experience confusing.
Not testing create, read, and update behavior after adding permissions.
Not documenting which table, view, form, and permission is used on each page.

These are teaching cautions based on Microsoft Learn’s explanation that Dataverse access is restricted by default in Power Pages and requires table permissions associated with web roles, and that forms, views, and lists are created through Dataverse and the Data workspace. [5](https://learn.microsoft.com/en-us/power-pages/security/table-permissions)[3](https://learn.microsoft.com/en-us/power-pages/getting-started/use-data-workspace)

Dataverse Integration Terms to Remember

Term	Simple Meaning
Dataverse Integration	Connecting Power Pages with Dataverse data for forms, lists, and records.
Data Workspace	Power Pages area used to manage tables, forms, and lists for the site.
Table	Dataverse structure used to store business records.
Column	A field inside a Dataverse table.
View	A query-like structure that defines rows and columns displayed in lists.
Form	A structure used to create, view, or update Dataverse records.
List	A Power Pages component that displays Dataverse records on a page.
Table Permission	Security rule that allows access to Dataverse records through Power Pages.
Web Role	User role associated with permissions for Power Pages access.
CRUD	Create, Read, Update, and Delete data operations.

Important Points to Remember

Dataverse integration is one of the key features of Power Pages.
Power Pages users can create, read, and update Dataverse records through web pages.
The Data workspace helps manage business data for the site using tables, forms, and lists.
All data and changes in the Data workspace are stored in Microsoft Dataverse.
Dataverse views are used as the foundation of list components in Power Pages.
Dataverse forms can be used to add form components to Power Pages pages.
Access to Dataverse records is automatically restricted when using forms, lists, Liquid, Web API, and other components.
Table permissions must be configured and associated with web roles to allow Dataverse record access.
Dataverse data used in Power Pages can also be accessed by Power Apps, Power Automate, and Power BI.

These points summarize Microsoft Learn’s Dataverse integration, Data workspace, and table permission guidance for Power Pages. [1](https://learn.microsoft.com/en-us/power-pages/getting-started/tutorial-dataverse-website)[3](https://learn.microsoft.com/en-us/power-pages/getting-started/use-data-workspace)[5](https://learn.microsoft.com/en-us/power-pages/security/table-permissions)

Simple Summary

Dataverse Integration in Power Pages means using Microsoft Dataverse as the data source for a website. Dataverse stores the business data, while Power Pages displays and collects that data through pages, forms, lists, and secured components.

Microsoft Learn explains that Power Pages users can create, read, and update Dataverse records, and that the Data workspace helps makers manage tables, forms, and lists for the site. [1](https://learn.microsoft.com/en-us/power-pages/getting-started/tutorial-dataverse-website)[3](https://learn.microsoft.com/en-us/power-pages/getting-started/use-data-workspace)

For beginners, the most important idea is: first design the Dataverse table, then create views and forms, then add lists and forms to Power Pages, and finally configure table permissions so the right users can access the right data.

Conclusion

Dataverse Integration is a core Power Pages topic because most real business websites need to work with data. A static website can show information, but a Dataverse-connected website can collect registrations, display requests, update applications, and support business processes.

A strong Dataverse integration depends on good data modeling, clear views, well-designed forms, meaningful lists, and secure table permissions. Microsoft Learn clearly shows that Dataverse records are restricted by default in Power Pages and that table permissions must be configured and associated with web roles to allow access. [5](https://learn.microsoft.com/en-us/power-pages/security/table-permissions)

After learning this topic, learners can move to Power Pages Forms, Lists & Table Permissions, where they will understand how to build secure data-driven pages that create, display, and update Dataverse records.