Study guide
5.1: Page Types, Anatomy & Control Structure
Microsoft Dynamics 365 Business Central Developer MB-820
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Business Central Architecture & Platform Foundation
1.1 Business Central Architecture & Extensions Model 1.2 Customization Lifecycle: Cloud (SaaS) vs. On-Premises 1.3 Base Application, System Application & AppSource
2 Chapter 2: Development Environment & Configuration
2.1: Development Environment Setup: VS Code, AL: Go! Projects & Sandboxes 2.2: AL Configuration Files: app.json & launch.json Parameters 2.3: Multi-Root Workspaces & Project Dependencies
3 Chapter 3: Extension Lifecycle: Debugging, Deployment, Multilanguage & Maintenance
3.1 Debugging & Snapshot Debugging in Visual Studio Code 3.2 Extension Deployment & Schema Synchronization Modes 3.3 Multilanguage Development with XLIFF & Translation Files 3.4 Extension Maintenance, Deprecation & Breaking Changes
4 Chapter 4: Tables, Table Extensions & Data Modeling
4.1: Building Tables, Fields, Keys & Data Types 4.2: Table Extensions & Table Modifications 4.3: FlowFields, FlowFilters & Table Relations 4.4: Enums, Enum Extensions & Extensible Types
5 Chapter 5: Pages, Page Extensions & Role Centers
5.1: Page Types, Anatomy & Control Structure 5.2: Building Card, List & Document Pages 5.3: Page Extensions & Page Customizations 5.4: Role Centers, Headlines & Cue Data Modeling
6 Chapter 6: Reports & Document Generation
6.1 Report Architecture, DataItems & Dataset Design 6.2 Report Layouts: RDLC, Word, Excel & Multilanguage 6.3 Document Reports & Request Page Programming 6.4 Processing-Only Reports & Report Substitutions
7 Chapter 7: XMLports & Data Exchange
7.1 XMLport Architecture, Formats & Properties 7.2 XMLport Node Hierarchy, Triggers & Stream Manipulation
8 Chapter 8: Codeunits, Events, Triggers & Interfaces
8.1 Codeunit Types, Execution & SingleInstance Codeunits 8.2 Events, Publishers, Subscribers & Event Isolation 8.3 Interfaces, Polymorphism & Dynamic Codeunit Invocation 8.4 Installation & Upgrade Codeunits, Data Transfer & Archive
9 Chapter 9: Entitlements, Permissions & Queries
9.1 Permission Sets & Permission Set Extensions 9.2 Inherent Permissions, Inherent Entitlements & Security Scoping 9.3 Query Objects: Joins, Aggregation & Query as Report Data Source
10 Chapter 10: UI Customization, User Assistance & Onboarding
10.1 Profile Objects & Custom Page Views in AL 10.2 User Assistance: ToolTips, Teaching Tips & In-App Tours 10.3 Assisted Setup, Guided Experience & Onboarding Checklists
11 Chapter 11: Business Central Design Patterns & Data Process Model
11.1 Functional Table Types: Master Data, Supplemental & Setup Patterns 11.2 Document Standards: Header, Line, History & Journal Architectures 11.3 Data Process Model & Posting Routine Architecture
12 Chapter 12: AL Language Fundamentals, Data Types & Variables
12.1 AL Syntax, Variable Scope, Primitive & Complex Data Types 12.2 Expressions, Control Flow Statements & Built-in Functions 12.3 Access Modifiers (Public, Internal, Local) & Code Scoping
13 Chapter 13: Data Manipulation, Streams & Error Handling
13.1 Record Operations: Get, FindSet, ModifyAll & Filter Functions 13.2 Streams, File Management & TempBlob 13.3 Error Handling: ErrorInfo, TryFunctions & Collectible Errors
14 Chapter 14: Testing, Test Toolkit & Automation
14.1 Testing Architecture & the Test Toolkit 14.2 Authoring Test Codeunits & UI Handler Functions
15 Chapter 15: Telemetry, Performance Optimization & Analyzers
15.1 Telemetry Configuration & Azure Application Insights 15.2 Custom Telemetry Signals with Session.LogMessage & KQL 15.3 Performance Profiler, SetLoadFields & Query Optimization 15.4 AL Analyzers: CodeCop, AppSourceCop, UICop & PTECop
16 Chapter 16: REST Web Services & JSON in AL
16.1 HttpClient, HttpRequestMessage & REST API Consumption 16.2 JSON Processing: JsonObject, JsonArray, JsonValue & JsonToken
17 Chapter 17: API Pages, OData, Read Scale-Out & OAuth
17.1 API Pages (PageType=API), OData Web Services & REST Endpoints 17.2 Bound and Unbound OData Actions with [ServiceEnabled] 17.3 Read Scale-Out Architecture & DataAccessIntent Configuration 17.4 Microsoft Entra ID App Registrations & OAuth 2.0 Integration
5.1: Page Types, Anatomy & Control Structure
Key Takeaways Explain This Topic AI
AL pages represent the visual presentation tier of Business Central, categorized by PageType into master cards, multi-record lists, documents, worksheets, subparts, dialogs, assisted setup wizards (NavigatePage), and AI prompt dialogs (PromptDialog).
The layout hierarchy consists of distinct functional containers: area(Content) for primary business data and FastTabs, area(FactBoxes) for contextual sidebars, and area(Prompting) for generative AI Copilot workflows.
The modern actions container organizes user commands into specialized functional areas (Processing, Creation, Navigation, Reporting, PromptActions) and exposes them via the area(Promoted) modern action bar using actionref controls.
Page discoverability via Tell Me search (Alt+Q) requires configuring a non-None UsageCategory (such as Lists, Tasks, Administration, Documents, History, ReportsAndAnalysis) paired with an active ApplicationArea.
Essential data concurrency and execution properties including DelayedInsert = true, SourceTableTemporary, SourceTableView, CardPageId, RefreshOnActivate, and CRUD permissions (InsertAllowed, ModifyAllowed, DeleteAllowed) govern page runtime behavior.
Last updated: August 2026
5.1 Page Types, Anatomy & Control Structure
In Microsoft Dynamics 365 Business Central, Pages represent the visual presentation and interaction tier of the application. Every user interaction—from viewing customer lists and entering sales orders to configuring system setup and interacting with AI Copilot prompts—occurs through a page object. For the MB-820 certification exam, developers must master the comprehensive taxonomy of page types, understand the structural containers of page definitions, configure modern action ribbons, and apply page properties that govern searchability, performance, and data manipulation.
1. Comprehensive Taxonomy of Page Types
The AL programming language provides a rich set of page types specified via the PageType object property. The selected PageType dictates how the Web Client renders the user interface, how records are displayed, and which interactive features are available.
PageType Typical Use Case Key Characteristics & Architecture
Card Master entities (e.g., Customer Card , Item Card , Vendor Card ) Displays a single record across collapsible sections called FastTabs . Optimized for viewing and editing detailed entity attributes.
List Multi-record entity browsing (e.g., Customer List , Item List ) Displays records in a tabular grid using a repeater() control. Supports searching, column sorting, filtering, and row-level drilldown to an associated CardPageId .
ListPlus Multi-grid relationships and matrix forms (e.g., Item Availability by Location ) Combines two or more distinct repeater() controls or a header with multiple sub-grids on a single display canvas.
Document Master-detail transactional records (e.g., Sales Order , Purchase Invoice ) Composed of a master Card header FastTab combined with an embedded ListPart subform for line items.
Worksheet Batch line processing and journal entry (e.g., General Journal , Payment Reconciliation Journal ) Grid-oriented line entry interface with specialized header filters, batch posting actions, and footer balance totals.
ListPart Embedded grid subpages (e.g., Sales Order Subform , Lines ) A lightweight list intended to be embedded within a parent Document , Card , or RoleCenter via a part() control. Linked to the header via SubPageLink .
CardPart Contextual sidebars (FactBoxes) and Activity Cues A lightweight card embedded within area(FactBoxes) on cards/lists or within area(RoleCenter) on Role Centers to display summarized metrics, cues, or related details.
HeadlinePart Role Center dynamic greeting and insight banners Specialized part page rendering rotating text banners and business insight notifications at the top of a Role Center. Formatted via XML payload syntax.
ConfirmationDialog Modal user confirmation dialogs Simple modal window displaying a message prompt with standard Yes / No action buttons. Suppresses menus and navigation chrome.
StandardDialog Lightweight input parameter dialogs (e.g., Batch Change Parameters ) Modal pop-up window presenting fields for user parameter entry without an action bar or navigation menu. Confirmed with OK / Cancel .
NavigatePage Multi-step Assisted Setup Wizards Guided setup wizard container that renders step-by-step sequential panes with built-in Back , Next , and Finish navigation buttons. Suppresses standard action ribbons.
PromptDialog Generative AI Copilot interactions Specialized dialog container for Microsoft 365 Copilot experiences. Features dedicated prompt input, output generation, and confirmation action surfaces ( Keep it , Discard , Regenerate ).
API OData REST API endpoints Non-visual page object exposed exclusively as a RESTful web service entity for external integrations. Does not render in the Web Client UI.
Exam Watch: On the MB-820 exam, pay close attention to the distinction between StandardDialog , NavigatePage , and PromptDialog . A multi-step wizard guiding an administrator through setup steps must use NavigatePage . Quick parameter entry dialogs use StandardDialog . Generative AI prompt-and-response flows use PromptDialog .
Loading diagram... Business Central Page Structural Hierarchy & Container Layout
2. Structural Containers: Layout and Areas
A page object definition in AL contains two mandatory top-level blocks: layout and actions (plus an optional views block). The layout block defines the visual data controls presented on the screen, organized into dedicated areas :
1. area(Content)
The primary container where the core business data controls reside:
On a Card page, area(Content) contains one or more group() containers that render as collapsible FastTabs (e.g., General , Invoicing , Shipping ).
On a List page, area(Content) contains a single repeater() control that renders the multi-record data grid.
On a Document page, area(Content) contains header group() FastTabs and embedded part() controls representing line subforms.
2. area(FactBoxes)
The secondary container located on the right side of the screen (the FactBox pane) that provides contextual, real-time insights regarding the selected record without requiring the user to navigate away:
Custom FactBoxes: Declared using part(Name; PageIdentifier) bound to the active record via the SubPageLink property.
System FactBoxes: Declared using systempart(Name; SystemPartType) :
systempart(Links; Links) : Displays attached URL hyperlinks and document shortcuts.
systempart(Notes; Notes) : Displays internal user notes and record commentary.
systempart(MyNotes; MyNotes) : Displays legacy user-specific personal notes.
3. area(Prompting)
Introduced for AI Copilot experiences ( PageType = PromptDialog ). It hosts input prompt fields where users specify natural language instructions and displays AI-generated output previews.
4. area(RoleCenter)
The root layout container exclusively utilized when PageType = RoleCenter . It hosts modular part pages including HeadlinePart , CardPart (Cues and Activities), and embedded operational list parts.
3. Actions Container & The Modern Promoted Action Bar
The actions block defines the ribbon commands, buttons, and menus available to the user. Actions are organized into standard functional action areas:
Action Area Purpose & Visual Placement
area(Processing) Core operational actions (e.g., Post , Calculate , Release , Reopen ). Located on the Process tab of the action bar.
area(Creation) Actions that instantiate new related documents or records (e.g., New Sales Quote , New Order ).
area(Navigation) Actions that open related entity cards, ledger entries, statistics, or dimensions (e.g., Customer Ledger Entries , Dimensions ). Located under the Navigate / Related menu.
area(Reporting) Actions that print or preview business documents and analytical reports (e.g., Print Statement , Sales Summary ).
area(PromptActions) Dedicated actions for generative AI prompt flows ( Generate , Regenerate , Keep it , Discard ).
area(Embedding) Navigation menu links rendered on the top navigation bar of Role Center pages.
The Modern Promoted Actions Architecture ( area(Promoted) )
In modern Business Central development, the legacy method of promoting actions (using Promoted = true; PromotedCategory = Process; on individual action blocks) is obsolete. Developers must define an area(Promoted) container within the actions block and reference actions using actionref controls grouped inside group(Category_...) : actions
- {
- area(Processing)
- {
- action(PostInvoice)
- {
- ApplicationArea = All;
- Caption = 'Post';
- ToolTip = 'Finalize and post the sales invoice.';
- Image = PostOrder;
- trigger OnAction()
- begin
- Codeunit.Run(Codeunit::"Sales-Post", Rec);
- end;
- }
- }
- area(Promoted)
- {
- group(Category_Process)
- {
- Caption = 'Process';
- actionref(PostInvoice_Promoted; PostInvoice)
- {
- }
- }
- }
- }
4. Essential Page Properties and Discoverability
Page properties configure execution rules, search visibility, and data integrity:
Discoverability: UsageCategory and ApplicationArea
To make a page discoverable in the Tell Me search box (keyboard shortcut: Alt+Q ), two properties must be configured simultaneously:
ApplicationArea : Must match an active application area enabled in the user's tenant (commonly All , Basic , Suite ).
UsageCategory : Dictates the Tell Me search classification. Valid values include:
Lists : Tabular master and transactional lists.
Tasks : Operational worksheets and task cards.
Administration : Setup and configuration pages.
Documents : Transactional headers and orders.
History : Posted documents and historical archives.
ReportsAndAnalysis : Analytical reports and financial queries.
None : Excludes the page from Tell Me search (default).
Exam Rule: Subpages ( ListPart , CardPart ) and FactBoxes must never specify UsageCategory (leave as None ). Setting a UsageCategory on a subpart causes compilation warnings and clutters Tell Me with unusable partial pages.
Data Manipulation and Concurrency Properties
Property Value Type Architectural Effect
SourceTable Table Identifier Binds the page dataset to a physical or temporary table buffer.
SourceTableTemporary Boolean When true , the page operates on an in-memory temporary record buffer isolated from the SQL database.
SourceTableView Filter Expression Enforces immutable baseline filters and sorting (e.g., where("Document Type" = const(Order)) ).
CardPageId Page Identifier On a List page, specifies the Card page opened when double-clicking a row or clicking Edit / View .
Editable Boolean Controls whether fields on the page can be modified by the user ( true by default).
DelayedInsert Boolean When true , the OnInsertRecord trigger and SQL INSERT do not fire until the user enters values and navigates away from the primary key fields or active row. Mandatory on List and Worksheet repeaters to prevent premature empty record creation.
InsertAllowed / ModifyAllowed / DeleteAllowed Boolean Restricts specific CRUD operations at the UI layer without requiring table-level permissions changes.
RefreshOnActivate Boolean Forces the page to re-execute OnAfterGetRecord and refresh dataset values whenever the user switches back to the browser tab or page view.
5. Complete AL Page Definition Example
The following code demonstrates a robust AL Card page definition illustrating properties, layout areas, FastTabs, FactBoxes, and modern promoted actions: page 50100 "Equipment Card"
- {
- PageType = Card;
- SourceTable = "Equipment Item";
- Caption = 'Equipment Card';
- UsageCategory = None;
- RefreshOnActivate = true;
- layout
- {
- area(Content)
- {
- group(General)
- {
- Caption = 'General';
- field("No."; Rec."No.")
- {
- ApplicationArea = All;
- ToolTip = 'Specifies the unique identifier for the equipment.';
- Importance = Promoted;
- }
- field(Description; Rec.Description)
- {
- ApplicationArea = All;
- ToolTip = 'Specifies a descriptive title for the equipment.';
- Importance = Promoted;
- }
- field("Serial No."; Rec."Serial No.")
- {
- ApplicationArea = All;
- ToolTip = 'Specifies the manufacturer serial number.';
- }
- field(Status; Rec.Status)
- {
- ApplicationArea = All;
- ToolTip = 'Specifies the current operational readiness status.';
- Importance = Promoted;
- }
- }
- group(Maintenance)
- {
- Caption = 'Maintenance & Service';
- Importance = Additional;
- field("Last Service Date"; Rec."Last Service Date")
- {
- ApplicationArea = All;
- ToolTip = 'Specifies the date of the most recent service inspection.';
- }
- field("Warranty Expiry Date"; Rec."Warranty Expiry Date")
- {
- ApplicationArea = All;
- ToolTip = 'Specifies when the factory warranty coverage ends.';
- }
- }
- }
- area(FactBoxes)
- {
- part(EquipmentPicture; "Equipment Picture FactBox")
- {
- ApplicationArea = All;
- SubPageLink = "No." = field("No.");
- }
- systempart(Links; Links)
- {
- ApplicationArea = RecordLinks;
- }
- systempart(Notes; Notes)
- {
- ApplicationArea = Notes;
- }
- }
- }
- actions
- {
- area(Processing)
- {
- action(ScheduleMaintenance)
- {
- ApplicationArea = All;
- Caption = 'Schedule Maintenance';
- ToolTip = 'Create a new maintenance work order for this equipment.';
- Image = ServiceOrder;
- trigger OnAction()
- var
- MaintMgmt: Codeunit "Equipment Maintenance Mgmt";
- begin
- MaintMgmt.CreateWorkOrder(Rec);
- end;
- }
- }
- area(Promoted)
- {
- group(Category_Process)
- {
- Caption = 'Process';
- actionref(ScheduleMaintenance_Promoted; ScheduleMaintenance)
- {
- }
- }
- }
- }
- }