Study guide
4.3 View Configuration, System Views, Personal Views & Filters
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
4.3 View Configuration, System Views, Personal Views & Filters
Key Takeaways Explain This Topic AI
Dataverse Views define how tabular records are queried, filtered, sorted, and presented across entity home grids, subgrids, lookup dialogs, and interactive dashboards.
Views are architecturally divided into Public Views (solution-aware, available to all app users), System Views (special-purpose platform views), and Personal Views (user-created and managed).
The five special-purpose System Views are: Default Public View (primary grid), Advanced Find View (query template), Associated View (related navigation), Lookup View (search modal), and Quick Find View (grid search index).
Quick Find Views utilize 'Find Columns' to define which attributes are searched when users enter keywords into the grid search box and 'View Columns' to define what data is displayed in the search results.
Personal Views can be created by any user with Read access to a table, customized using the modern Edit Filters engine, and securely shared, assigned, or exported via FetchXML.
Last updated: August 2026
4.3 View Configuration, System Views, Personal Views & Filters
In Microsoft Dataverse, Views define how sets of records for a specific table are queried, structured, filtered, sorted, and displayed. Rather than writing raw SQL queries or building bespoke table components, customizers and end users leverage Dataverse views to present data consistently across entity home grids, subgrids, lookup search modals, and interactive dashboards.
For a functional consultant preparing for the PL-200 exam, understanding the architectural classifications of views, configuring the five special-purpose System Views, mastering the Modern View Designer, and constructing advanced FetchXML filter conditions are essential skills.
1. Architectural View Classifications: Public, System & Personal Views
In Dataverse, views are stored as structured query definitions in two distinct database tables: savedquery (for System and Public Views) and userquery (for Personal Views). +-----------------------------------------------------------------------------------+
- | DATAVERSE VIEW TAXONOMY |
- | |
- | +---------------------------------------------------------------------------+ |
- | | 1. PUBLIC VIEWS (Stored in `savedquery` table) | |
- | | - General-purpose shared views accessible to all users in an app | |
- | | - Solution-aware; authored in Maker Portal and deployed via ALM | |
- | | - Examples: 'Active Accounts', 'My Open Opportunities', 'Inactive Leads'| |
- | +---------------------------------------------------------------------------+ |
- | | 2. SYSTEM VIEWS (Special-Purpose Platform Views in `savedquery`) | |
- | | - Built-in views required for core platform behavior | |
- | | - Cannot be deleted; customized to tailor lookup and search behavior | |
- | | - [Default Public] [Quick Find] [Lookup] [Associated] [Adv Find] | |
- | +---------------------------------------------------------------------------+ |
- | | 3. PERSONAL VIEWS (Stored in `userquery` table) | |
- | | - Created by individual end users using 'Edit filters' / 'Save as View'| |
- | | - Stored in user space; not solution-aware | |
- | | - Can be explicitly Shared or Assigned to other Users / Teams | |
- | +---------------------------------------------------------------------------+ |
- +-----------------------------------------------------------------------------------+
- In-Depth View Classification Comparison
View Type Underlying Table Solution-Aware? Who Can Create / Edit? Visibility Scope Deletable?
Public View savedquery Yes (ALM Supported) System Customizers & System Administrators All users who have Read access to the table in the app Yes (Except if set as default)
System View savedquery Yes (ALM Supported) System Customizers & System Administrators System-wide operational contexts No (Core system artifacts)
Personal View userquery No (User Space) Any user with Read privilege on the table Owner only (unless explicitly Shared with colleagues/teams) Yes (By view owner or admin)
2. The 5 Special-Purpose System Views
Every standard and custom table in Dataverse is automatically provisioned with five specialized System Views that power platform-level interactions: +-----------------------------------------------------------------------------------+
- | THE 5 SPECIAL-PURPOSE SYSTEM VIEWS |
- | |
- | 1. DEFAULT PUBLIC VIEW ====> Primary landing grid when user opens entity |
- | 2. QUICK FIND VIEW ====> Powers grid search box: Find Columns & View Cols |
- | 3. LOOKUP VIEW ====> Layout displayed in lookup search dropdown/modal |
- | 4. ASSOCIATED VIEW ====> Rendered when viewing records via 'Related' nav |
- | 5. ADVANCED FIND VIEW ====> Default template loaded during ad-hoc querying |
- +-----------------------------------------------------------------------------------+
- Detailed Analysis of Special System Views
Default Public View:
The primary view displayed when a user navigates to an entity home page via the Site Map.
Any Public View can be promoted to become the Default Public View via the Maker Portal. Only one view per table can serve as the default.
Quick Find View (Search Engine):
Powers the search box located in the upper-right corner of the entity grid.
Contains two distinct column configuration sets:
Find Columns (Indexed Attributes): The specific columns evaluated when a user types a search term (e.g., searching by Account Name , Account Number , or City ). Adding too many text columns to Find Columns can degrade search performance.
View Columns (Display Attributes): The columns rendered in the search results grid when matching records are returned.
Quick Find filter criteria define the baseline query filter (e.g., only searching across statecode = Active ).
Lookup View:
Defines the columns and sorting order displayed when a user clicks on a Lookup field search modal or dropdown on a form.
Typically configured to display primary identifier columns (e.g., Full Name , Email , Company ) to help users disambiguate between records with similar names.
Associated View:
Rendered when a user opens a parent record, clicks the Related tab in the form navigation, and selects a 1:N related table.
Optimized to show related context without duplicating parent identifiers.
Advanced Find View:
Serves as the default base template when users open Advanced Find or export data queries.
3. Modern View Designer & Column Configuration
The Modern View Designer in the Power Apps Maker Portal ( make.powerapps.com ) provides a visual WYSIWYG environment for customizing view columns, sorting, and widths. +-----------------------------------------------------------------------------------+
- | MODERN VIEW DESIGNER ARCHITECTURE |
- | |
- | +-----------------------------------------------------------------------------+ |
- | | VIEW: Active Accounts | Filter: Status = Active | Sort: Created On (Desc) | |
- | +-----------------------------------------------------------------------------+ |
- | | [Account Name ^] | [Primary Contact] | [Email (Contact)]* | [Annual Revenue] | |
- | | (Width: 200px) | (Width: 150px) | (Width: 180px) | (Width: 120px) | |
- | |------------------+-------------------+--------------------+------------------| |
- | | Contoso Ltd | John Doe | john@contoso.com | $1,500,000 | |
- | | Fabrikam Inc | Jane Smith | jane@fabrikam.com | $4,200,000 | |
- | +-----------------------------------------------------------------------------+ |
- | * Email (Contact) is a RELATED COLUMN added via 1:N / N:1 Table Traversal! |
- +-----------------------------------------------------------------------------------+
- Key View Configuration Capabilities
Adding Related Table Columns: Customizers can add columns not only from the primary table but also from any table linked via an N:1 Lookup Relationship (e.g., displaying the Parent Account's Credit Limit directly on a Contact view).
Column Width Configuration: Column widths can be specified in exact pixels (e.g., 150px ) or adjusted visually by dragging column borders.
Multi-Level Sorting: Views support primary and secondary sorting criteria (e.g., sort primarily by City Ascending , then secondarily by Annual Revenue Descending ).
App-Level View Selection: Inside the Modern App Designer, makers can selectively include specific public views in a model-driven app while excluding others, ensuring users are not overwhelmed by unnecessary views.
4. Filter Criteria & FetchXML Logic
Every view in Dataverse is powered by a FetchXML query that encapsulates the filtering criteria and table joins. +-----------------------------------------------------------------------------------+
- | FETCHXML QUERY FILTER LOGIC |
- | |
- | LOGICAL OPERATOR: [AND] |
- | +---> Condition 1: Status Equals 'Active' |
- | +---> Condition 2: Annual Revenue Is Greater Than '$1,000,000' |
- | +---> LOGICAL OPERATOR: [OR] (Nested Group) |
- | +---> Sub-Condition A: Address 1: City Equals 'Seattle' |
- | +---> Sub-Condition B: Address 1: City Equals 'Portland' |
- | |
- | RELATED TABLE FILTER (Link-Entity Join): |
- | +---> Related Table (Contact): Contains Data |
- | +---> Contact Status Equals 'Active' |
- +-----------------------------------------------------------------------------------+
- Modern Edit Filters Panel Capabilities
Standard Comparison Operators: Equals , Does Not Equal , Contains , Does Not Contain , Begins With , Contains Data (not null), Does Not Contain Data (null).
Date & Time Relative Operators: Today , Yesterday , This Week , Last Month , Older Than X Days , Next X Months .
Grouping Conditions ( AND vs OR ): Makers can select multiple conditions and group them using AND (all conditions must evaluate to true) or OR (any single condition evaluates to true).
Hierarchical & Relationship Joins: Querying across relationships using "Under" / "Not Under" (for self-referencing hierarchies) or filtering based on attributes in related 1:N or N:1 tables.
5. Personal View Lifecycle: Creation, Sharing, Assigning & Pinning
End users can create personalized views to track their daily work without requiring administrator intervention. +-----------------------------------------------------------------------------------+
- | PERSONAL VIEW LIFECYCLE MANAGEMENT |
- | |
- | 1. CREATE: User opens Public View -> Clicks 'Edit filters' -> Adds criteria |
- | Clicks 'Save as new view' -> Names it 'My High Priority Leads' |
- | |
- | 2. PIN: User clicks View Selector -> Clicks Pin icon next to personal view |
- | View becomes the user's personal default landing view! |
- | |
- | 3. SHARE: User clicks 'Manage and share views' -> Selects 'Share' |
- | Grants Read/Write permissions to 'Sales Team' Owner Team |
- | |
- | 4. ASSIGN: User transfers complete ownership of the view to another manager |
- +-----------------------------------------------------------------------------------+
- Personal View Governance Rules
Sharing Personal Views:
The owner of a personal view can share it with individual users or teams.
Granular permissions can be granted during sharing: Read , Write , Delete , Assign , and Share .
If a personal view is shared with an Entra ID Group Team or Owner Team, all team members immediately gain access to the view in their view selector.
Assigning Personal Views:
Assigning a personal view permanently transfers ownership ( ownerid in userquery ) to the recipient user or team. The original creator loses administrative control unless granted access by the new owner.
Pinning Views:
Any user can pin any Public or Personal view as their personal default view. This preference is stored per user and does not alter the system-wide Default Public View for other users.