Study guide

5.2 Form Component Controls & Specialized UX Elements

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

5.2 Form Component Controls & Specialized UX Elements

Key Takeaways Explain This Topic AI

The Form Component Control renders a fully interactive Main Form of a related entity directly inline on a host record form, enabling simultaneous cross-table CRUD editing.

Form Component Controls bind to lookup columns and are defined via form XML parameters specifying the target table and form GUID or name.

Dataverse strictly enforces a one-level nesting limitation on Form Component Controls: nested form components inside child forms will not render.

Power Apps Component Framework (PCF) controls replace basic text/numeric inputs with tactile controls including Sliders, Linear Gauges, Arc Knobs, Toggles, Star Ratings, and Pen Inputs.

The modern Power Apps Grid control upgrades subgrids with inline cell editing, nested child subgrids, column filtering, aggregations (Sum/Avg), and custom cell renderers across Web, Tablet, and Phone clients.

Last updated: August 2026

Form Component Controls & Specialized UX Elements

Delivering high-efficiency user interfaces in Microsoft Dataverse requires minimizing unnecessary navigation and presenting complex data in intuitive, actionable formats. Traditional model-driven forms often suffer from excessive clicks: viewing or editing a parent record requires opening separate tabs or popups, while standard text fields offer plain data entry rather than rich visual input.

To overcome these UX bottlenecks, Power Platform provides Form Component Controls for inline related-record editing and Power Apps Component Framework (PCF) controls for rich visual interactions. Mastering these components is essential for the PL-200 exam and enterprise application architecture.

1. Form Component Control Architecture & Inline Editing

In standard model-driven forms, Quick View forms allow users to view read-only data from a related parent record. However, when users need to modify that parent data (e.g., updating a Contact's mobile phone while logging a Case), they previously had to navigate away to the parent record.

The Form Component Control solves this problem by embedding a complete, fully interactive Main Form of a related lookup table directly inline inside a section on the host form. +-----------------------------------------------------------------------------------+

  • | FORM COMPONENT CONTROL INLINE EDITING |
  • | |
  • | [HOST FORM: Case (Incident)] |
  • | +------------------------------------------------------------------------------+ |
  • | | Ticket Title: Server Connectivity Failure | |
  • | | Priority: High | Status: Active | |
  • | | | |
  • | | +-- SECTION: Customer Details (Form Component on 'Customer' Lookup) -------+ | |
  • | | | Account Name: Contoso Enterprises | | |
  • | | | Main Phone: +1 (555) 019-2834 [Editable Inline] | | |
  • | | | Primary Email: support@contoso.com [Editable Inline] | | |
  • | | | Billing Tier: Enterprise Gold [Editable Inline] | | |
  • | | +--------------------------------------------------------------------------+ | |
  • | | | |
  • | | Description: Customer reported switch offline since 08:00 AM... | |
  • | +------------------------------------------------------------------------------+ |
  • | | |
  • | +---> Single [Save] button commits changes to BOTH Case & Account! |
  • +-----------------------------------------------------------------------------------+
  • Key Capabilities

Full CRUD Editing: Users can modify parent record columns directly inside the host form section without navigating away.

Unified Transactional Save: When the user clicks Save on the host form, Dataverse validates and saves changes on both the host record and the embedded form component record synchronously.

Business Logic Execution: Business Rules, Form Scripts (JavaScript), and PCF controls configured on the embedded child form execute normally within the embedded section.

Configuration Mechanics

To configure a Form Component Control:

Open the host table form in the modern Form Designer or classic solution explorer.

Select the Lookup Column pointing to the target entity (e.g., parentcustomerid or primarycontactid ).

In the column properties, add the Form Component Control ( MscrmControls.Form.FormComponentControl ).

  • Configure the XML parameter specifying the target table name and form unique identifier: <FormsDisplay>
  • <NativeForms>
  • <Form id="a1b2c3d4-e5f6-7890-abcd-ef1234567890"
  • entityName="contact"
  • formMode="edit"
  • name="Contact Inline Edit Form" />
  • </NativeForms>
  • </FormsDisplay>
  • Critical Restrictions & Governance Rules

Caution

Strict 1-Level Nesting Limit: Dataverse supports only one level of Form Component nesting. If Form A embeds Form B via a Form Component Control, and Form B contains a Form Component Control for Form C, Form C will NOT render inside Form A. Multi-level recursive nesting is blocked to prevent circular rendering loops and performance degradation.

Polymorphic Lookups: Multi-table lookups (such as Customer , which can link to either an Account or a Contact ) require specific multi-form XML mappings to handle both target entity types dynamically.

Read-Only Enforcements: If a user lacks edit privileges on the related record via Dataverse Security Roles, the embedded form component renders as read-only for that user automatically.

2. Power Apps Component Framework (PCF) Overview

Power Apps Component Framework (PCF) empowers developers and functional consultants to replace standard HTML textboxes and dropdowns with rich, responsive UI elements built on modern web standards (HTML5, TypeScript, React, and Fluent UI). +-----------------------------------------------------------------------------------+

  • | PCF CONTROL BINDING ARCHITECTURE |
  • | |
  • | [Dataverse Column / Field] <====== Two-Way Property Binding ======> [PCF UI] |
  • | - Whole Number (Rating: 4) <-------------------------------------> [Star UI] |
  • | - Boolean (Value: True) <-------------------------------------> [Toggle UI] |
  • | - Multiple Lines (Base64) <-------------------------------------> [Pen Input] |
  • | - Multiple Lines (HTML) <-------------------------------------> [Rich Text] |
  • | |
  • | [Form Factor Targeting] |
  • | - Web Browser: Enabled - Tablet Client: Enabled - Mobile Phone: Enabled |
  • +-----------------------------------------------------------------------------------+
  • Client Form Factor Targeting

Every PCF control can be targeted independently across three client endpoints:

Web: Desktop web browsers running modern model-driven app shells.

Tablet: Power Apps mobile client optimized for tablet screen dimensions.

Phone: Power Apps mobile client optimized for compact smartphone viewports.

3. Core Out-of-the-Box PCF Controls

Dataverse includes a robust suite of native, out-of-the-box PCF controls that require no custom code or external solution imports. +-----------------------------------------------------------------------------------+

  • | SPECIALIZED PCF CONTROLS OVERVIEW |
  • | |
  • | [TOGGLE SWITCH] [STAR RATING] [PEN INPUT] |
  • | Active: [ (O) ON ] Rating: [ * * * * o ] Signature: [ ~JohnDoe~] |
  • | (Two Options / Boolean) (Whole Number 1-5) (Signature / Base64) |
  • | |
  • | [NUMBER SLIDER] [ARC KNOB] [RICH TEXT EDITOR] |
  • | Volume: [---|-----] 65% Dial: ( 75% ) [B] [I] [U] [Link] |
  • | (Whole / Decimal Number) (Numeric Percentage) Formatted HTML text... |
  • +-----------------------------------------------------------------------------------+
  • 1. Rich Text Editor (RTE)

Bound Column Type: Multiple Lines of Text (Plain Text / Rich Text format).

Features: Provides a full WYSIWYG formatting toolbar with bold, italics, underline, bullet/numbered lists, font sizing, hyperlinks, table insertion, and inline image pasting.

Configuration Web Resource: Behavior can be customized by linking a JSON configuration web resource to configure custom toolbars, specify allowed HTML tags, and define font whitelists.

Storage: Stores content internally as sanitized HTML markup within the Dataverse text column (up to 1,048,576 characters).

2. Pen Input / Signature Capture

Bound Column Type: Multiple Lines of Text or Image column.

Features: Provides a smooth drawing canvas for capturing digital signatures, sketches, and handwritten notes on touchscreens and mobile devices.

Storage: Encodes the drawing as a Base64 PNG image string or stores it natively in the Dataverse image blob store.

3. Toggle (Flip Switch)

Bound Column Type: Two Options (Boolean: Yes/No, True/False).

Features: Replaces classic radio buttons or checkboxes with modern iOS/Android-style sliding toggle switches, dramatically improving touch-device usability.

4. Star Rating

Bound Column Type: Whole Number (Integer values 0 through 5).

Features: Renders interactive 5-star visual rating controls. Clicking a star immediately updates the underlying integer value (1 to 5).

Use Cases: Customer satisfaction (CSAT) surveys, lead grading, and performance evaluations.

5. Number Input Slider, Linear Gauge & Arc Knob

Bound Column Type: Whole Number, Decimal Number, or Floating Point.

Features: Provides draggable slider bars, linear gauges, or circular rotary dials with configurable minimum, maximum, and step intervals (e.g., min: 0, max: 100, step: 5).

4. Subgrid Controls: Power Apps Grid Control vs. Classic Editable Grid

Displaying and manipulating child records inside a parent form is a frequent functional requirement. Model-driven apps provide modern grid controls to enable rapid inline data entry. +-----------------------------------------------------------------------------------+

  • | POWER APPS GRID CONTROL FEATURES |
  • | |
  • | +------------------------------------------------------------------------------+ |
  • | | [+] New Item | [X] Delete | [Filter] | Columns: [Name, Qty, Unit Price, Total] | |
  • | +------------------------------------------------------------------------------+ |
  • | | > Line 1: Industrial Widget A | Qty: [ 10 ] | Price: [$150.00] | $1,500.00 | |
  • | | +-- [Nested Child Grid: Serial Numbers / Sub-assemblies] ------------------+ | |
  • | | | Serial #SN-9012 | Inspected: True | Warehouse: Seattle-01 | | |
  • | | +--------------------------------------------------------------------------+ | |
  • | | > Line 2: Heavy Duty Cable B | Qty: [ 25 ] | Price: [ $40.00] | $1,000.00 | |
  • | +------------------------------------------------------------------------------+ |
  • | | TOTAL AGGREGATIONS: Total Quantity = 35 | Grand Total = $2,500.00 | |
  • | +------------------------------------------------------------------------------+ |
  • +-----------------------------------------------------------------------------------+
  • The Modern Power Apps Grid Control

The Power Apps Grid Control represents the state-of-the-art subgrid and view control in Dataverse, superseding the legacy Classic Editable Grid :

Inline Cell Editing: Users edit text, numeric, date, and lookup values directly within grid rows without opening individual forms.

Infinite Scrolling: Eliminates legacy 50-row pagination buttons, delivering smooth infinite scrolling through large datasets.

Nested Grids: Supports expanding a row to reveal a hierarchical child subgrid (e.g., expanding an Order Line to view associated Serial Numbers).

Column Aggregations: Computes and displays column-level totals (Sum, Average, Min, Max, Count) in a dedicated footer bar.

Custom PCF Cell Renderers: Allows embedding custom PCF visualizers inside individual grid cells (e.g., rendering priority as colored badges or ratings as stars inside the grid).

  • Grid Feature Read-Only Grid (Default) Classic Editable Grid Modern Power Apps Grid Control
  • Inline Data Editing No (Double click opens form) Yes Yes (Fluent UI optimized)
  • Infinite Scrolling No (Page buttons 1-50) No (Page buttons 1-50) Yes
  • Nested Child Subgrids No No Yes
  • Footer Aggregations No No Yes (Sum, Avg, Min, Max, Count)
  • Custom Cell Renderers No No Yes (PCF custom cell controls)
  • Accessibility Standard Legacy Full WCAG 2.1 Compliance
  • 5. PCF Control Configuration & Best Practices

Control Name Bound Data Type Configurable Properties Primary Enterprise Use Case

Form Component Lookup Column Target Entity, Form ID, Form Mode Inline editing of parent Account/Contact on Case/Order form.

Rich Text Editor Multiple Lines (Text) Custom Configuration Web Resource Rich formatted emails, knowledge articles, case resolution notes.

Pen Input Multiple Lines / Image Output Format (PNG/Base64), Stroke Mobile field service signature sign-off and inspection acceptance.

Toggle Two Options (Boolean) On/Off Labels, Display Mode Touch-friendly status flags (e.g., "VIP Customer", "Active").

Star Rating Whole Number (1-5) Max Stars (Default: 5) Customer feedback scores, lead qualification ratings.

Number Slider Integer / Decimal Minimum, Maximum, Step Value Percentage discounts, progress tracking, volume thresholds.

Power Apps Grid Subgrid / View Dataset Enable Editing, Enable Filtering, Nested Grid Order line items, project milestone tracking with inline edits.