4.2 Form Types: Main, Quick Create, Quick View & Card Forms

4.2 Form Types: Main, Quick Create, Quick View & Card Forms

Forms in Microsoft Dataverse provide the primary user interface through which users interact with, create, update, and review business records. Rather than building bespoke data-entry forms from scratch, Dataverse provides a structured Form Architecture consisting of four distinct form types: Main Forms, Quick Create Forms, Quick View Forms, and Card Forms.

Each form type is engineered for a specific operational context, viewport size, and data density requirement. For the PL-200 exam, a functional consultant must understand the technical capabilities, layout rules, configuration prerequisites, and security governance models associated with each form type.

---

1. Dataverse Form Types Taxonomy & Comparison Matrix

+-----------------------------------------------------------------------------------+
|                         DATAVERSE FORM TYPES TAXONOMY                             |
|                                                                                   |
|  +--------------------------+  +--------------------------+                       |
|  | 1. MAIN FORM             |  | 2. QUICK CREATE FORM     |                       |
|  |  - Full CRUD interface   |  |  - Lightweight flyout    |                       |
|  |  - Tabs, Columns, Grids  |  |  - Rapid data entry      |                       |
|  |  - BPF, Header, Timeline |  |  - Retains parent context|                       |
|  +--------------------------+  +--------------------------+                       |
|                                                                                   |
|  +--------------------------+  +--------------------------+                       |
|  | 3. QUICK VIEW FORM       |  | 4. CARD FORM             |                       |
|  |  - Read-Only embedded    |  |  - Compact micro-layout  |                       |
|  |  - Bound to Parent Lookup|  |  - Used in mobile streams|                       |
|  |  - Shows live parent data|  |  - Interactive Dashboards|                       |
|  +--------------------------+  +--------------------------+                       |
+-----------------------------------------------------------------------------------+

Comprehensive Form Types Comparison

---

2. Main Form Anatomy & Advanced UI Components

The Main Form is the workhorse of model-driven apps. It provides a rich container for complex business data, enterprise business processes, subgrids, and collaboration tools.

+-----------------------------------------------------------------------------------+
|                             MAIN FORM ANATOMY                                     |
|                                                                                   |
|  +-----------------------------------------------------------------------------+  |
|  | HEADER: [Record Title: Contoso Corp] | Status: Active | Owner: Sarah | Rev: $2M |  |
|  +-----------------------------------------------------------------------------+  |
|  | BUSINESS PROCESS FLOW (BPF): [Qualify] ===> [Develop] ---> [Propose]        |  |
|  +-----------------------------------------------------------------------------+  |
|  | TABS: [General]  [Details]  [Contacts]  [Invoices]  [Related (1:N)]         |  |
|  | +------------------------------------+ +----------------------------------+ |  |
|  | | SECTION 1 (2-Column Layout)        | | SECTION 2 (Timeline Control)      | |  |
|  | |  - Account Name: Contoso           | |  - Phone Call completed (Today)   | |  |
|  | |  - Primary Contact: John Doe       | |  - Note added by Sarah (Yesterday)| |  |
|  | |  - Website: https://contoso.com    | |  - Email sent to John (Aug 14)    | |  |
|  | +------------------------------------+ +----------------------------------+ |  |
|  | | SUBGRID: Related Opportunities     | | QUICK VIEW: Primary Contact Info  | |  |
|  | | [Opp Name | Est. Value | Close]    | |  - Email: john@contoso.com        | |  |
|  | | [Cloud Migration | $150k | 9/30]   | |  - Direct Phone: 555-0199         | |  |
|  | +------------------------------------+ +----------------------------------+ |  |
|  +-----------------------------------------------------------------------------+  |
|  | FOOTER: Record Status: Open | Unsaved Changes Indicator                     |  |
|  +-----------------------------------------------------------------------------+  |
+-----------------------------------------------------------------------------------+

Detailed Main Form Anatomy Breakdown

1. High-Density Form Header:

   • Sits at the top of the form and remains permanently visible during scrolling.
   • Holds up to 4 high-density fields (e.g., Status, Owner, Total Value, Rating).
   • Can be configured as Read-Only or Editable directly within the header flyout.

2. Business Process Flow (BPF) Integration:

   • Visual chevron bar guiding users through defined organizational stages (e.g., Lead-to-Opportunity Sales Process).
   • Binds directly to the entity and persists stage progress in Dataverse.

3. Tabs & Sections:

   • Tabs organize the form into distinct thematic pages (e.g., Summary, Details, Financials). Tabs can have 1, 2, or 3 columns and can be dynamically hidden/shown via Business Rules or JavaScript.
   • Sections partition tabs into logical groupings. Section layouts support 1 to 4 columns for field arrangement.

4. Subgrid Controls:

   • Display lists of related records (1:N or N:N) directly within the parent form (e.g., displaying related Contacts or Open Cases on an Account form).
   • Customizers can set the Default View, enable the View Selector, allow Inline Search, and configure whether subgrids display all records or only related records.

5. Timeline Control:

   • Centralized collaboration feed displaying Activities (Tasks, Emails, Phone Calls, Appointments), Notes (with file attachments), and System Posts.
   • Supports advanced card configuration, activity filtering, keyword search, and rich text notes.

---

3. Quick Create & Quick View Form Mechanics

Quick Create Forms: Fast-Paced Record Creation

Quick Create forms solve the problem of context disruption. When a user is logging an Opportunity and realizes a new Contact does not exist, they should not have to leave the Opportunity form, open the Contact grid, create the Contact, and navigate back.

+-----------------------------------------------------------------------------------+
|                         QUICK CREATE FORM WORKFLOW                                |
|                                                                                   |
|   1. User clicks '+' on Account Subgrid -> [Add New Contact]                      |
|   2. System opens Quick Create Drawer on the right side of the screen             |
|   3. User fills: First Name, Last Name, Email, Mobile Phone                       |
|   4. User clicks [Save and Close]                                                 |
|   5. Contact record created -> Subgrid refreshes immediately                      |
|   * USER NEVER LEAVES THE ACCOUNT RECORD FORM!                                    |
+-----------------------------------------------------------------------------------+

[!IMPORTANT] Quick Create Enablement Prerequisite: A Quick Create form will only open if the target table has the "Allow quick create" option enabled under Table Properties in the Maker Portal. If this property is disabled, clicking '+' will force a full Main Form navigation, losing the user's background page context.

Quick View Forms: Contextual Parent Visibility

Quick View forms eliminate redundant data entry and unnecessary custom lookup columns. Consider a Case (Incident) form that contains a lookup to a parent Contact:

• Instead of creating redundant columns on the Case table (such as Contact Email, Contact Mobile Phone, and Contact Job Title) and writing workflows to sync them, the customizer creates a Quick View Form on the Contact table containing those three fields.
• On the Case Main Form, the customizer inserts a Quick View Control, binds it to the customerid lookup column, and selects the Contact's Quick View Form.
• When a user opens a Case, Dataverse dynamically reads live values from the referenced Contact record and renders them as a read-only card. If the contact's email changes, the Case form reflects the update immediately.

---

4. Form Security Roles, Form Order & Fallback Logic

In enterprise implementations, different departments require tailored views of the same business entity. For example, a Sales Representative requires financial metrics on an Account form, whereas a Field Technician requires service level agreements and physical asset details.

Dataverse allows multiple Main Forms per table, governed by Form Security Roles, Form Order, and the mandatory Fallback Form.

+-----------------------------------------------------------------------------------+
|                     FORM SECURITY & FALLBACK RESOLUTION LOGIC                     |
|                                                                                   |
|   User opens Account Record:                                                      |
|                                                                                   |
|   Step 1: Evaluate User's Assigned Security Roles against Form Role Assignments:  |
|           - Form A ('Sales Account Form')     -> Restricted to 'Sales Rep' Role   |
|           - Form B ('Service Account Form')   -> Restricted to 'Service Tech' Role|
|           - Form C ('Standard Account Form')  -> FALLBACK FORM (Enabled for All)  |
|                                                                                   |
|   Step 2: Matching Evaluation:                                                    |
|           * If User has 'Sales Rep' Role        ===> Serves Form A (Sales Form)   |
|           * If User has 'Service Tech' Role     ===> Serves Form B (Service Form) |
|           * If User has 'Auditor' Role (Neither)===> Serves Form C (FALLBACK FORM)|
|                                                                                   |
|   Step 3: User Form Selector:                                                     |
|           * If User holds BOTH Sales & Service Roles, Form Order dictates the     |
|             initial form served, and the user can toggle via the Form Selector.   |
+-----------------------------------------------------------------------------------+

Form Governance Mechanics

1. Form Security Role Assignment:

   • By default, every form is set to "Enabled for everyone".
   • Customizers can restrict a form to "Enabled for specific security roles" (e.g., only granting the Executive Summary Form to the Executive VP security role).

2. Form Order (Display Priority):

   • When a user qualifies for multiple Main Forms, Dataverse evaluates the Form Order list from top to bottom. The form with the highest priority (rank 1) is served as the initial default.
   • Most Recently Used (MRU) Memory: Once a user manually switches to a different form using the Form Selector dropdown, Dataverse remembers that user's selection and defaults to it on subsequent record visits.

3. The Fallback Form Requirement:

   • Every Dataverse table must have at least one Main Form designated as the Fallback Form.
   • If a user's assigned security roles do not match any of the role-restricted forms, Dataverse automatically routes the user to the Fallback Form, preventing application crashes or unauthorized lockouts.