Study guide
1.1 Dataverse Table Types, Properties & Ownership
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
1.1 Dataverse Table Types, Properties & Ownership
Key Takeaways Explain This Topic AI
Dataverse categorizes tables into Standard, Custom, Activity, and Virtual tables, each serving distinct architectural storage and extensibility requirements.
Activity tables utilize the specialized activityparty schema to model multi-party participants and aggregate dynamically across regarding records in model-driven timelines.
Virtual tables provide real-time CRUD access to external OData v4 or SQL data sources without replicating data into Dataverse storage, but they do not support auditing, rollup columns, change tracking, or offline sync.
Table ownership is strictly immutable post-creation: User/Team ownership supports 4-level hierarchical security depth, whereas Organization ownership applies uniform tenant-wide security.
Dataverse feature enablement follows strict governance rules: Auditing requires a 3-tier activation hierarchy (Environment -> Table -> Column), while Change Tracking enables downstream Azure Synapse Link and Fabric replication.
Last updated: August 2026
Dataverse Table Types, Properties & Ownership
Microsoft Dataverse serves as the intelligent, secure, and scalable relational data backbone of the Microsoft Power Platform. Built on enterprise-grade Azure infrastructure, Dataverse abstracts underlying relational storage (Azure SQL Database, Cosmos DB, and Azure Blob/Data Lake storage) behind a unified, metadata-driven business layer. As a Power Platform Functional Consultant preparing for the PL-200 exam, understanding how tables are classified, how records are owned, and how foundational table properties govern enterprise data behavior is essential for designing resilient data architectures.
1. Dataverse Table Classifications
Dataverse organizes structured business data into distinct table categories. Choosing the correct table type directly impacts system capabilities, performance, and application user experience. +-----------------------------------------------------------------------------+
- | DATAVERSE TABLE CLASSIFICATIONS |
- | |
- | +-------------------+ +-------------------+ +-------------------+ |
- | | STANDARD TABLES | | CUSTOM TABLES | | ACTIVITY TABLES | |
- | | - Common Data Mod | | - Custom schemas | | - activityparty | |
- | | - Account, Contact| | - Publisher prefix| | - Timeline rollup | |
- | | - Extensible | | - User/Org owned | | - Immutable type | |
- | +-------------------+ +-------------------+ +-------------------+ |
- | | |
- | v |
- | +-------------------+ |
- | | VIRTUAL TABLES | |
- | | - External OData | |
- | | - No native store | |
- | | - No audit/rollup | |
- | +-------------------+ |
- +-----------------------------------------------------------------------------+
- 1. Standard Tables
Standard tables are out-of-the-box business entities included with the Dataverse environment, aligned with the open-source Common Data Model (CDM) . Examples include Account , Contact , Lead , Opportunity , and Case (Incident).
Extensibility: Standard tables can be extended with custom columns, forms, views, relationships, and business logic.
Restrictions: Core system columns and baseline system tables cannot be deleted. Display names can be customized to match organizational terminology (e.g., renaming Account to Company ), but the underlying schema name remains constant.
2. Custom Tables
Custom tables are created by functional consultants and solution architects to fulfill bespoke business requirements not satisfied by the standard CDM schema.
Naming Conventions: Custom tables automatically receive a solution publisher customization prefix (e.g., cr123_Equipment , contoso_InspectionLog ) separated by an underscore.
Schema vs. Display Name: The Display Name (singular/plural) can be modified at any time, but the Schema Name and Logical Name are permanently fixed upon table creation.
3. Activity Tables
Activity tables represent time-based, actionable interactions or tasks performed by users or automated processes. Built-in activity tables include Email , Phone Call , Task , Appointment , and Letter .
The ActivityParty Model: Activity tables utilize a specialized multi-party relationship model ( activityparty ). This allows a single activity record to link to multiple sender, recipient, CC, BCC, and organizer records across different tables (e.g., Accounts, Contacts, Leads, System Users) simultaneously.
The Regarding ( regardingobjectid ) Polymorphic Lookup: Every activity table includes a standard polymorphic lookup column called Regarding. When an activity is linked to a parent record (such as an Account), the activity automatically appears in that record's timeline control.
Timeline Aggregation & Rollup: Activities roll up hierarchically. If an activity is linked regarding an Opportunity, it surfaces on the Opportunity timeline, the parent Account timeline, and the primary Contact timeline.
Immutability: Once a table is created as an Activity table, it CANNOT be converted into a standard table. Conversely, a standard table cannot be converted into an Activity table.
4. Virtual Tables (Virtual Entities)
Virtual tables enable Dataverse to surface, query, and manipulate data stored in external data sources (such as Azure SQL, SharePoint lists, SAP, or RESTful endpoints via OData v4) as if the records resided natively inside Dataverse.
Architecture: Data remains residing in the external system. When a user opens a view or form in Power Apps, Dataverse makes a real-time call through an OData v4 Data Provider, SQL Provider, or Custom Plug-in Data Provider.
Full CRUD Support: Virtual tables support Create, Read, Update, and Delete operations if the underlying data provider and external API support them.
Platform Limitations: Because virtual data is not physically stored or indexed within the Dataverse relational database engine, virtual tables have specific functional limitations:
No native Dataverse Auditing.
No Change Tracking support for Azure Synapse Link / Microsoft Fabric.
No Rollup column calculations aggregating virtual child records.
No offline synchronization in Power Apps mobile apps.
Cannot be enabled for Business Process Flows without custom background synchronizations.
Table Dimension Standard Tables Custom Tables Activity Tables Virtual Tables
Storage Location Native Dataverse Store Native Dataverse Store Native Dataverse Store External System (via API)
Customization Prefix None / Microsoft Publisher Prefix (e.g., cr123_ ) Publisher Prefix (e.g., cr123_ ) Publisher Prefix (e.g., cr123_ )
- ActivityParty Model No No Yes (Multi-party links) No
- Timeline Rollup Target of regarding Target of regarding Source of activities No
- Auditing & Change Tracking Supported Supported Supported Not Supported
- Offline Mobile Sync Supported Supported Supported Not Supported
- Post-Creation Type Change Locked Locked Locked (Immutable) Locked
- 2. Table Ownership Architecture
When creating a custom table in Dataverse, the consultant must choose between two distinct ownership models: User or Team ownership and Organization ownership. This setting establishes how the Dataverse security engine evaluates record-level access privileges. +-----------------------------------------------------------------------------+
- | TABLE OWNERSHIP ARCHITECTURES |
- | |
- | [USER OR TEAM OWNED] [ORGANIZATION OWNED] |
- | - Granular 4-level security depth - Binary security access |
- | - User / BU / Parent-Child / Org - Organization-wide or None |
- | - Has 'Owner' & 'OwningBusinessUnit' - No 'Owner' column |
- | - Reassignable, shareable - Shared global reference data |
- | - Example: Projects, Invoices, Leads - Example: Tax Codes, Zip Codes |
- +-----------------------------------------------------------------------------+
- User or Team Owned
Mechanics: Each individual record contains system-managed foreign key columns: OwnerId (pointing to a System User or Owner Team) and OwningBusinessUnit .
Security Depth: Supports all four security role privilege depths:
User (Basic): User can access only records they own or share.
Business Unit (Local): User can access records owned by anyone within their business unit.
Parent-Child Business Unit (Deep): User can access records in their business unit and all subordinate child business units.
Organization (Global): User can access all records across the entire tenant environment.
Collaboration: Records can be assigned, shared, reassigned, and managed across dynamic access teams and Entra ID security groups.
Best For: Core transactional business entities requiring department segregation, sales territories, case assignments, and individual ownership (e.g., Work Orders, Contracts, Claims).
Organization Owned
Mechanics: Records belong globally to the entire organization. There is no Owner or OwningBusinessUnit column.
Security Depth: Security roles provide only binary access: either Organization (Global) access or None .
Best For: Global reference data, lookup tables, configuration parameters, and company-wide catalogs that apply uniformly to all users regardless of department (e.g., Country Codes, Tax Rates, Currency Lists, Product Categories).
Caution
Ownership Setting Immutability: The Table Ownership model is defined during initial table provisioning and is permanently immutable . Once a table is saved as User/Team owned or Organization owned, this property cannot be modified. If an incorrect ownership model is selected, the table must be deleted and recreated.
3. Primary Name and Primary Key Identifiers
Every Dataverse table is automatically generated with two essential identifier columns:
Primary Key (GUID):
A unique 128-bit Globally Unique Identifier (e.g., a1b2c3d4-e5f6-7890-abcd-ef1234567890 ).
Schema name follows the convention <tablename>id (e.g., accountid , cr123_inspectionid ).
System-managed, auto-generated upon record insertion, immutable, and indexed as the primary clustered key in SQL storage.
Primary Name Column:
A text column representing the human-readable label of the record.
Used as the display value in lookup fields, header controls, search results, and navigation links.
By default, Dataverse names this column Name (or cr123_name ).
Can be configured with single-line text formatting (maximum length up to 4,000 characters; default is 100 characters).
Requirement level can be set to Business Required , Business Recommended , or Optional .
4. Enterprise Table Properties & Feature Enablement
When provisioning tables in the Power Apps Maker Portal or through solution XML, several advanced enterprise capabilities can be enabled. Some properties can be toggled on or off freely, while others are one-way activations that cannot be disabled once turned on. +-----------------------------------------------------------------------------+
- | DATAVERSE 3-TIER AUDITING HIERARCHY |
- | |
- | [TIER 1: ENVIRONMENT LEVEL] ---> Must enable global tenant auditing |
- | | |
- | v |
- | [TIER 2: TABLE LEVEL] ---> Must enable auditing on specific table |
- | | |
- | v |
- | [TIER 3: COLUMN LEVEL] ---> Must enable auditing on specific column |
- | (Logs attribute changes to audit log) |
- +-----------------------------------------------------------------------------+
- 1. Auditing (3-Tier Hierarchy)
Dataverse provides enterprise auditing to track record creation, updates, deletions, and security role assignments. Auditing operates on a strict 3-tier hierarchical structure :
Environment Level: Auditing must be turned on in Power Platform Admin Center ( Settings > Audit and logs > Audit settings ).
Table Level: Auditing must be checked in the table properties.
Column Level: Auditing must be enabled on the individual columns requiring change tracking.
Important
Auditing Rule for PL-200: If Auditing is enabled at the Environment level and Table level, but disabled on a specific Column, changes to that column will NOT be captured. Conversely, if a column has auditing enabled but the parent table has auditing disabled, no logs are created. All three tiers must be active for attribute logging.
2. Change Tracking
Change Tracking allows external applications and data pipelines to detect and synchronize incremental data modifications (inserts, updates, and deletes) without performing expensive full-table scans.
Downstream Dependencies: Change Tracking is a mandatory prerequisite for enabling Azure Synapse Link for Dataverse , Microsoft Fabric Link , and custom data integration export services.
One-Way Setting: Once downstream export services lock Change Tracking, it cannot be disabled without removing the service link.
3. Duplicate Detection
Duplicate Detection evaluates incoming and modified records against predefined Duplicate Detection Rules.
Prerequisites: Duplicate detection must be enabled at the Environment level and Table level.
Execution Points: Triggers during manual record creation/updates in model-driven apps, bulk data imports, and when records are synchronized via Server-Side Synchronization.
4. Document Management (SharePoint Integration)
Enabling Document Management allows Dataverse records to automatically provision linked document folders within SharePoint document libraries.
Creates a seamless document grid on the model-driven form, allowing users to upload, view, and collaborate on Office documents associated with a specific record.
5. Connections
Enabling Connections allows users to establish ad-hoc, semantic relationships between records across any connection-enabled tables (e.g., linking a Contact to another Contact as 'Spouse', 'Attorney', or 'Colleague') without creating formal 1:N or N:N database schema relationships.