Study guide
5.4: Role Centers, Headlines & Cue Data Modeling
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.4: Role Centers, Headlines & Cue Data Modeling
Key Takeaways Explain This Topic AI
Role Center pages (PageType = RoleCenter) act as persona-tailored homepages in Business Central, aggregating Headline insights, Cue activity tiles, navigation menus, and quick action shortcuts without binding to a single source table.
The Role Center layout is defined within area(RoleCenter), hosting modular subpage parts such as HeadlinePart, CardPart (Cues and Activities), and embedded operational list parts.
Activity Cue tables store singleton records containing integer and decimal FlowFields that dynamically aggregate real-time counts and sums across business transaction tables.
Cue tiles support dynamic visual thresholds using the Style and StyleExpr properties (Favorable [green], Unfavorable [red], Ambiguous [yellow], Subordinate [grey]), combined with DrillDownPageId for instant list navigation.
Headline parts (PageType = HeadlinePart) display rotating greetings and business highlights formatted using the <qualifier>...</qualifier><payload>...</payload> XML markup pattern.
Last updated: August 2026
5.4 Role Centers, Headlines & Cue Data Modeling
In Microsoft Dynamics 365 Business Central, the Role Center is the initial landing page presented to users upon login. Rather than presenting a flat menu of tables, a Role Center is an operational dashboard tailored to a specific user persona (e.g., Business Manager , Order Processor , Warehouse Worker ). It consolidates real-time business metrics ( Cues ), daily greetings and high-priority alerts ( Headlines ), operational charts, and quick-action shortcuts into a single workspace. Mastering Role Center layout composition, Activity Cue tables, singleton initialization patterns, and Headline XML markup is vital for passing the MB-820 exam.
1. Role Center Page Architecture & Layout Composition
A Role Center page is defined with PageType = RoleCenter . Unlike Card or List pages, a Role Center page is not bound to a SourceTable ( SourceTable is omitted). Instead, it acts as a host canvas composed of modular subpage parts declared inside area(RoleCenter) .
Navigation Areas on Role Centers
The actions container on a Role Center provides distinct areas for configuring the user's top-level navigation structure:
area(Embedding) : Renders direct links on the top navigation bar (e.g., Items , Customers , Vendors , Sales Orders ).
area(Sections) : Organizes hierarchical navigation menus and grouped category links accessible from the navigation bar.
area(Processing) : Renders quick-create actions and processing commands directly accessible in the top-right ribbon (e.g., New Sales Quote , Post Batch ). page 50130 "Equipment Manager Role Center"
- {
- PageType = RoleCenter;
- Caption = 'Equipment Manager';
- layout
- {
- area(RoleCenter)
- {
- part(Headlines; "Equipment Manager Headline")
- {
- ApplicationArea = All;
- }
- part(Activities; "Equipment Manager Activities")
- {
- ApplicationArea = All;
- }
- part(OverdueList; "Overdue Maintenance ListPart")
- {
- ApplicationArea = All;
- }
- }
- }
- actions
- {
- area(Embedding)
- {
- // Top navigation bar menu links
- action(EquipmentList)
- {
- ApplicationArea = All;
- Caption = 'Equipment Items';
- RunObject = page "Equipment List";
- }
- action(RentalOrders)
- {
- ApplicationArea = All;
- Caption = 'Rental Orders';
- RunObject = page "Equipment Rental Orders";
- }
- }
- area(Processing)
- {
- // Quick-action buttons in the ribbon
- action(NewWorkOrder)
- {
- ApplicationArea = All;
- Caption = 'New Work Order';
- RunObject = page "Maintenance Work Order";
- RunPageMode = Create;
- Image = New;
- }
- }
- }
- }
Loading diagram... Role Center Layout and Subpage Modular Composition
2. Designing Cues and Activity Parts
Cues are visual, interactive square tiles that present aggregated metrics (e.g., "12 Open Orders" , "$45,000 Overdue Invoices" ). Clicking a Cue immediately drills down into a pre-filtered list of the underlying transactional records.
Data Modeling Architecture for Cues
Building Cues involves two distinct AL components:
The Cue Table: A dedicated normal table containing integer or decimal FlowFields configured with CalcFormula = count(...) or CalcFormula = sum(...) .
The Activities Page: A CardPart page ( PageType = CardPart ) containing a cuegroup container bound to the Cue table.
The Singleton Pattern on Cue Pages
Because Cue tables represent aggregated session data, the table must contain exactly one record (the singleton record). On the Activities page, developers initialize this record inside OnOpenPage : table 50131 "Equipment Cue"
- {
- Caption = 'Equipment Cue';
- DataClassification = CustomerContent;
- fields
- {
- field(1; "Primary Key"; Code[10])
- {
- Caption = 'Primary Key';
- }
- field(2; "Overdue Maintenance"; Integer)
- {
- Caption = 'Overdue Maintenance';
- FieldClass = FlowField;
- CalcFormula = count("Equipment Item" where (Status = const(Overdue)));
- }
- field(3; "Active Rentals"; Integer)
- {
- Caption = 'Active Rentals';
- FieldClass = FlowField;
- CalcFormula = count("Rental Header" where (Status = const(Active)));
- }
- }
- keys
- {
- key(PK; "Primary Key")
- {
- Clustered = true;
- }
- }
- }
- page 50131 "Equipment Manager Activities"
- {
- PageType = CardPart;
- SourceTable = "Equipment Cue";
- Caption = 'Activities';
- RefreshOnActivate = true;
- layout
- {
- area(Content)
- {
- cuegroup(MaintenanceCues)
- {
- Caption = 'Maintenance Operations';
- field("Overdue Maintenance"; Rec."Overdue Maintenance")
- {
- ApplicationArea = All;
- ToolTip = 'Specifies equipment units requiring urgent service.';
- DrillDownPageId = "Equipment List";
- StyleExpr = OverdueStyle;
- }
- field("Active Rentals"; Rec."Active Rentals")
- {
- ApplicationArea = All;
- ToolTip = 'Specifies the number of units currently on active rental.';
- DrillDownPageId = "Equipment Rental Orders";
- }
- }
- }
- }
- var
- OverdueStyle: Text;
- trigger OnOpenPage()
- begin
- // Singleton record initialization pattern
- Rec.Reset();
- if not Rec.Get() then begin
- Rec.Init();
- Rec.Insert();
- end;
- end;
- trigger OnAfterGetRecord()
- begin
- // Set dynamic visual style threshold
- if Rec."Overdue Maintenance" > 5 then
- OverdueStyle := 'Unfavorable'
- else if Rec."Overdue Maintenance" > 0 then
- OverdueStyle := 'Ambiguous'
- else
- OverdueStyle := 'Favorable';
- end;
- }
- Cue Styles and Threshold Formatting
Cues support visual styling to alert users to operational thresholds via the Style or StyleExpr property:
Favorable : Renders a green indicator bar (positive state, zero errors, on-track metric).
Unfavorable : Renders a red indicator bar (critical state, overdue tasks, budget exceeded).
Ambiguous : Renders a yellow/orange indicator bar (warning, pending approval, attention needed).
Subordinate : Renders a neutral grey indicator (informational or secondary metric).
None : Default neutral presentation without accent coloring.
3. Headline Parts and Dynamic Payload Formatting
Headline Parts are specialized PageType = HeadlinePart; pages rendered as dynamic banner strips at the very top of Role Centers. They display rotating greetings, congratulations, and significant business insights (e.g., "Awesome! You posted 15 orders today." ).
Headline Text Formatting and Payload Syntax
Headlines use structured XML tags to format text and highlight critical data words in the Web Client:
<qualifier>...</qualifier> : Renders small uppercase text above the main headline (e.g., TOP CUSTOMER , ALERT , GREETING ).
<payload>...</payload> : Renders the primary text banner.
<emphasize>...</emphasize> : Highlights specific metrics or names in bold colored accent text inside the payload. page 50132 "Equipment Manager Headline"
- {
- PageType = HeadlinePart;
- Caption = 'Headlines';
- RefreshOnActivate = true;
- layout
- {
- area(Content)
- {
- group(General)
- {
- ShowCaption = false;
- // Greeting headline
- field(GreetingText; HeadlineGreetingText)
- {
- ApplicationArea = All;
- }
- // Business Insight headline
- field(InsightText; HeadlineInsightText)
- {
- ApplicationArea = All;
- }
- }
- }
- }
- var
- HeadlineGreetingText: Text;
- HeadlineInsightText: Text;
GreetingLbl: Label '<qualifier>GOOD MORNING</qualifier><payload>Welcome back to <emphasize>Equipment Management</emphasize>.</payload>', Locked = true;
InsightLbl: Label '<qualifier>CRITICAL ALERT</qualifier><payload>You have <emphasize>%1 equipment units</emphasize> requiring immediate inspection.</payload>', Comment = '%1 = Overdue Count';
- trigger OnOpenPage()
- var
- EquipItem: Record "Equipment Item";
- OverdueCount: Integer;
- begin
- HeadlineGreetingText := GreetingLbl;
- EquipItem.SetRange(Status, EquipItem.Status::Overdue);
- OverdueCount := EquipItem.Count();
- HeadlineInsightText := StrSubstNo(InsightLbl, OverdueCount);
- end;
- }