Study guide

1.2 Table Relationships & Cascading Rules

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.2 Table Relationships & Cascading Rules

Key Takeaways Explain This Topic AI

Dataverse supports 1:N (One-to-Many), N:1 (Many-to-One), and N:N (Many-to-Many) relationships, establishing relational integrity across business entities.

Native N:N relationships utilize a hidden system-managed intersect table storing only primary keys, whereas Manual Intersect tables enable storing custom transactional metadata.

Relationship behaviors govern cascading lifecycle actions: Parental cascades all operations, Referential preserves child lifecycles, and Referential Restrict Delete blocks parent deletion if child records exist.

Dataverse executes 7 distinct cascading actions: Assign, Share, Unshare, Reparent, Delete, Merge, and Rollup View.

Cascading configurations enforce strict validation constraints: Delete cannot be set to Cascade User-Owned or Cascade Active, while Reparent cannot be set to Restrict Delete.

Last updated: August 2026

Table Relationships & Cascading Rules

Relational integrity is the bedrock of enterprise application architecture. In Microsoft Dataverse, relationships define how records in one table link to records in another. Beyond simple foreign key constraints, Dataverse relationships incorporate sophisticated cascading behaviors that automatically propagate security, assignment, reparenting, and deletion operations down complex parent-child hierarchies. Mastering these behaviors is vital for passing the PL-200 exam and preventing unintended data loss or security exposure in production.

1. Relationship Types in Dataverse

Dataverse supports three core relationship structures: +-----------------------------------------------------------------------------+

  • | DATAVERSE RELATIONSHIP TYPES |
  • | |
  • | [1:N / N:1 RELATIONSHIP] |
  • | Account (1) ------------< (N) Contact |
  • | - Foreign key lookup column created on the Child (N) table |
  • | |
  • | [NATIVE N:N RELATIONSHIP] |
  • | Student (N) >--- [Hidden Intersect: student_course] ---< (N) Course |
  • | - System-managed table, stores only StudentID + CourseID |
  • | |
  • | [MANUAL INTERSECT TABLE (JUNCTION)] |
  • | Student (1) --< (N) Enrollment (N) >-- (1) Course |
  • | - Custom table with metadata: Grade, Term, Status, PaidDate |
  • +-----------------------------------------------------------------------------+
  • 1. One-to-Many (1:N) and Many-to-One (N:1)

A 1:N relationship represents a primary parent table linked to multiple child records (e.g., one Account has many Contacts).

An N:1 relationship is simply the reciprocal view from the child table looking back to its single parent.

Mechanism: Dataverse creates a Lookup column on the child table that stores the 128-bit GUID of the parent record.

2. Native Many-to-Many (N:N)

Links multiple records in Entity A to multiple records in Entity B (e.g., Events and Attendees).

Hidden Intersect Table: Dataverse automatically provisions and manages a hidden physical intersect table in the database. This table contains only two columns: the Primary Key GUID of Table A and the Primary Key GUID of Table B.

Limitations: Users cannot add custom columns, forms, views, or business logic to a native N:N intersect table.

3. Manual Intersect (Junction) Table Pattern

When business requirements dictate that metadata must be captured about the relationship itself, consultants must implement a Manual Intersect Table (also known as a junction or bridge table).

Structure: A custom table is created that sits between the two primary entities. The junction table contains two separate N:1 lookup columns (one pointing to Table A, one pointing to Table B).

Metadata Payloads: The junction table can contain custom columns such as EnrollmentDate , FinalGrade , Role , CertificationStatus , or AssignedBy .

  • Criteria Native N:N Relationship Manual Intersect Table
  • Intersect Table Visibility Hidden system table Visible custom entity in Maker Portal
  • Custom Attributes None (Only 2 GUIDs) Unlimited custom columns
  • Business Logic Support None Full support (Business Rules, Power Automate, Plugins)
  • Form & View Customization Subgrid only Full Forms, Views, and Dashboards
  • Security & Ownership Inherited from related entities Independent User/Team or Org ownership
  • 2. Relationship Behaviors

When configuring a 1:N relationship, the consultant must define the Type of Behavior . This setting controls how operational events performed on the parent record propagate to related child records. +-----------------------------------------------------------------------------+

  • | RELATIONSHIP BEHAVIOR TYPES |
  • | |
  • | +-------------------+ +-------------------+ +-------------------+ |
  • | | PARENTAL | | REFERENTIAL | | REFERENTIAL (REST)| |
  • | | - Deep cascade | | - Independent | | - Restrict Delete | |
  • | | - Delete parent | | - Delete parent | | - Blocks parent | |
  • | | deletes children| | leaves children | | deletion if | |
  • | | - 1 parent limit | | - Link removed | | children exist | |
  • | +-------------------+ +-------------------+ +-------------------+ |
  • | | |
  • | v |
  • | +-------------------+ |
  • | | CONFIGURABLE | |
  • | | - Granular tuning | |
  • | | - Custom action | |
  • | | by action rules | |
  • | +-------------------+ |
  • +-----------------------------------------------------------------------------+
  • 1. Parental

In a Parental relationship, the child record's lifecycle is completely bound to the parent record. Any action taken on the parent record (Assign, Delete, Share, Unshare, Reparent) automatically cascades to all related child records.

Strict Constraint: A table can have only ONE Parental relationship where it acts as the child entity. A table cannot have two distinct parental parents (e.g., if an Order Item is parented by Order, it cannot also be parented by Product).

2. Referential

In a Referential relationship, records are linked for navigation and lookup purposes, but each record maintains an independent lifecycle.

If the parent record is deleted, the relationship link on the child record is cleared (Remove Link), but the child record remains active in the database.

3. Referential, Restrict Delete

In this behavior, the system prevents the parent record from being deleted as long as any related child records exist.

Enterprise Use Case: Preventing a Customer Account from being deleted if open Invoices or active Contracts exist.

4. Configurable Cascading

Allows the functional consultant to customize each cascading action individually to meet precise business rules.

3. The 7 Cascading Actions and Option Rules

Dataverse evaluates cascading rules across 7 distinct operations executed on a parent record: +-----------------------------------------------------------------------------+

  • | THE 7 DATAVERSE CASCADING ACTIONS |
  • | |
  • | 1. ASSIGN ---> Reassigning owner of parent propagates to children. |
  • | 2. SHARE ---> Sharing parent record grants access to children. |
  • | 3. UNSHARE ---> Revoking share on parent revokes access to children. |
  • | 4. REPARENT ---> Changing parent lookup updates child security scope. |
  • | 5. DELETE ---> Deleting parent cascades, removes link, or restricts. |
  • | 6. MERGE ---> Merging master/subordinate parent combines children. |
  • | 7. ROLLUP VIEW ---> Surfacing child activities in parent timeline grid. |
  • +-----------------------------------------------------------------------------+
  • Cascading Option Matrix

Option Value Description Supported Actions

Cascade All The action is applied to all related child records, regardless of state or ownership. Assign, Share, Unshare, Reparent, Delete, Merge

Cascade Active The action is applied only to active ( statecode = 0 ) child records. Inactive child records remain untouched. Assign, Share, Unshare, Reparent, Merge

Cascade User-Owned The action is applied only to child records owned by the same user who owns the parent record. Assign, Share, Unshare, Reparent, Merge

Cascade None The action is not applied to any related child records. Assign, Share, Unshare, Reparent, Merge, Rollup View

Remove Link The lookup field on the child record is set to null (unlinked), leaving child records intact. Delete ONLY

Restrict Delete If any related child records exist, the deletion of the parent record is blocked and throws an error . Delete ONLY

Warning

Critical Cascading Validation Rules for PL-200:

Delete Operation Restrictions: The Delete action supports only three options: Cascade All , Remove Link , or Restrict . Setting Delete to Cascade Active or Cascade User-Owned is invalid and rejected by the platform.

Reparent / Assign / Share Restrictions: Remove Link and Restrict Delete are ONLY valid for the Delete action. They cannot be applied to Assign, Share, Unshare, or Reparent.

Rollup View Options: Rollup View supports only Cascade All or Cascade None .

Practical Scenario: Cascading Assign vs. Ownership Exposure

Consider a sales organization where an Account is assigned from Sales Rep A to Sales Rep B:

If the Account-to-Opportunity relationship has Assign = Cascade All , all Opportunities (including closed/lost deals owned by other team members) are reassigned to Rep B.

If configured as Assign = Cascade User-Owned , only Opportunities currently owned by Rep A transfer to Rep B. Opportunities owned by technical specialists or secondary reps remain untouched.

If configured as Assign = Cascade None , no Opportunities transfer ownership.