Study guide

10.1 Profile Objects & Custom Page Views in AL

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

10.1 Profile Objects & Custom Page Views in AL

Key Takeaways Explain This Topic AI

AL profile objects define role-tailored workspaces by binding a Role Center page, default page customizations, and metadata settings like Promoted and Enabled.

The Customizations property associates pagecustomization objects with a profile, applying declarative layout modifications strictly to users operating within that profile.

A pagecustomization object is strictly declarative, allowing control reordering and property modifications, but strictly prohibiting AL variables, procedures, triggers, event subscribers, or adding new fields.

The views section in pageextension objects adds predefined filtered views to list pages, supporting Filters, OrderBy, and SharedLayout properties.

Setting SharedLayout = false decouples a page view's layout from the base list page, allowing an independent layout block to show, hide, reorder, or freeze columns specifically for that view tab.

Last updated: August 2026

10.1 Profile Objects & Custom Page Views in AL

In Microsoft Dynamics 365 Business Central, user experience is fundamentally role-driven. Rather than presenting a monolithic, one-size-fits-all interface to every employee, the platform tailors pages, navigation menus, action bars, cues, and data filters to specific job functions. For the MB-820 certification exam, developers must master the declarative AL constructs that drive this role-tailored experience: the profile object , associated pagecustomization objects , profileextension objects , and Page Views ( views ) declared in page extensions.

1. Profile Objects ( profile ) in AL

A profile object in AL defines an individual role workspace in Business Central. Profiles represent job titles or organizational roles—such as Order Processor , Business Manager , Warehouse Worker , or an ISV-specific role such as Quality Assurance Inspector . When a user selects a profile in My Settings (or when an administrator assigns a default profile to a user or user group), Business Central configures their home Role Center page and applies all declarative UI layout customizations tied to that profile.

  • Profile Syntax and Core Properties profile "Loyalty Manager"
  • {
  • Caption = 'Loyalty Program Manager';

ProfileDescription = 'Provides access to loyalty member accounts, point ledgers, reward tiers, and promotional campaigns.';

  • RoleCenter = page "Loyalty Manager Role Center";
  • Customizations = "Loyalty Customer Card Customization", "Loyalty Sales Order Customization";
  • Promoted = true;
  • Enabled = true;
  • }
  • Profile Object Properties Breakdown

Property Type Description & Runtime Behavior

Caption Text / Label The user-facing display name of the profile displayed in the My Settings page and the Role Explorer . Can be localized using .xlf translation files.

ProfileDescription Text A detailed explanation of the role's responsibilities and workflows. Visible to administrators when managing profiles in the Web Client.

RoleCenter Page Identifier Specifies the Page ID of type RoleCenter (e.g., page "Order Processor Role Center" ) that serves as the root home page when the user operates under this profile.

Customizations Comma-delimited list Specifies the names of one or more pagecustomization objects defined in AL that automatically apply to pages when the profile is active.

Promoted Boolean When set to true , the profile is featured prominently in the Role Explorer and highlighted in the top section of the profile selection dialog. Defaults to false .

Enabled Boolean Controls whether the profile is selectable by end users. When set to false , the profile cannot be assigned or chosen in My Settings , though administrators can still inspect it. Defaults to true .

Extending Existing Profiles with profileextension

Developers frequently need to enhance standard out-of-the-box profiles provided by Microsoft Base Application (such as "BUSINESS MANAGER" or "SALES ORDER PROCESSOR" ) by attaching custom page customizations without creating duplicate profiles. AL provides the profileextension object for this exact purpose: profileextension "Loyalty Business Mgr Ext" extends "BUSINESS MANAGER"

  • {
  • Customizations = "Loyalty Customer Card Customization", "Loyalty Item Card Customization";
  • }

Note

A profileextension object can only modify the Customizations property of an existing profile. It cannot reassign the RoleCenter page or change the Caption of base profiles.

Loading diagram... Role-Tailored Architecture: Profiles, Role Centers, and Page Customizations

2. Page Customization Objects ( pagecustomization )

A pagecustomization object in AL defines declarative UI modifications for a specific existing page. Unlike a pageextension —which applies globally to all users across all profiles—a pagecustomization applies only when a user accesses that page while logged in under the profile that binds the customization in its Customizations property.

Page Customization Syntax & Structure pagecustomization "Loyalty Customer Card Customization" customizes "Customer Card"

  • {
  • layout
  • {
  • // Hide non-essential financial fields for loyalty managers
  • modify("Credit Limit (LCY)")
  • {
  • Visible = false;
  • }
  • // Place loyalty-relevant fields prominently on the General FastTab
  • moveafter(Name; "Balance (LCY)")
  • // Rename group or alter group visual appearance
  • modify(General)
  • {
  • Caption = 'Customer & Loyalty Details';
  • }
  • }
  • actions
  • {
  • // Hide transactional posting actions irrelevant to loyalty administration
  • modify(Post)
  • {
  • Visible = false;
  • }
  • // Promote loyalty navigation actions
  • modify(CustomerLedgerEntries)
  • {
  • Visible = true;
  • }
  • }
  • }
  • Critical Restrictions on pagecustomization Objects

Understanding what a pagecustomization can and cannot do is one of the most heavily tested areas on the MB-820 certification exam:

Strictly Declarative (No AL Code) : You cannot declare global or local variables, custom procedures, triggers (such as OnOpenPage , OnAfterGetRecord , or OnValidate ), or event subscribers inside a pagecustomization object. Doing so is a compilation error.

No Schema Expansion : You cannot add new fields, parts, or controls that do not already exist on the target page. To add a new database field or new action to a page, you must use a pageextension .

Permitted Layout Operations : Modifications are limited to adjusting properties on existing controls (e.g., Visible , Caption , Importance , Enabled ) and reordering existing controls using movefirst() , movebefore() , moveafter() , and movelast() .

No Action Creation : You cannot declare new action() blocks inside pagecustomization ; you may only modify() or move existing actions defined in the base page or page extensions.

3. Predefined Page Views in AL ( views )

On list pages in Business Central, users frequently filter records to focus on specific operational subsets (for example, Open Sales Orders , Urgent Shipments , or Blocked Customers ). In AL, developers can define permanent, out-of-the-box filtered views within a page or pageextension object using the views section.

Predefined views appear as persistent tabs at the top of the filter pane on the list page, allowing users to switch contexts with a single click. pageextension 50110 "Sales Order List Views Ext" extends "Sales Order List"

  • {
  • views
  • {
  • addfirst
  • {
  • // View 1: Standard shared layout view
  • view(OpenHighValueOrders)
  • {
  • Caption = 'Open High-Value Orders';
  • Filters = where(Status = const(Open), "Amount Including VAT" = filter(> 50000));
  • OrderBy = descending("Order Date");
  • SharedLayout = true;
  • }
  • // View 2: Dedicated custom layout view
  • view(ExpeditedShippingOrders)
  • {
  • Caption = 'Expedited Shipments';
  • Filters = where("Shipment Method Code" = const('EXPRESS'), "Completely Shipped" = const(false));
  • OrderBy = ascending("Promised Delivery Date");
  • SharedLayout = false;
  • layout
  • {
  • modify("Shipment Method Code")
  • {
  • Visible = true;
  • }
  • modify("Promised Delivery Date")
  • {
  • Visible = true;
  • }
  • movefirst(Control1; "Promised Delivery Date")
  • }
  • }
  • }
  • }
  • }
  • Page View Properties Breakdown

Caption : The user-facing label rendered on the view tab in the Web Client filter pane.

Filters : A static where(...) clause defining record filtering criteria applied automatically when the view tab is selected. Supports const() literals, filter() expressions (e.g., >50000 , 'A*|B*' ), and multiple field conditions combined with commas ( AND ).

OrderBy : Sets the default sorting key and direction ( ascending(...) or descending(...) ).

SharedLayout : A critical boolean property governing how UI layout changes behave across views:

SharedLayout = true (Default) : The view shares the column layout, column order, and column visibility of the default list page. If a user personalizes column widths or visible columns on the list, those layout changes apply across all shared views.

SharedLayout = false : The view maintains an independent layout . Developers can define a dedicated layout block inside the view to show, hide, or reposition specific columns (e.g., placing Promised Delivery Date first) strictly when this specific view is active without altering the standard list layout.

4. UI Customization & Personalization Hierarchy

In Business Central, the user interface rendered in the browser is the result of a multi-layer composition pipeline. When multiple modifications target the same page element, Business Central resolves them in a deterministic order of precedence: Base Page (AL)

  • └── + Page Extensions (AL - Global for all users)
  • └── + Predefined Views (AL - Tab-specific filters & layouts)
  • └── + Page Customizations (AL - Bound to active Profile)
  • └── + Admin Customizations (Web Client - Profile mode)
  • └── + User Personalizations (Web Client - Individual user)
  • Comparison: UI Modification Methods

Dimension Developer AL ( views / pagecustomization ) Admin Customization (Profile Mode) User Personalization (Web Client)

Defined By Developer in Visual Studio Code via AL objects Tenant Admin in Web Client via "Customize Pages" Individual End User in Web Client via "Personalize"

Scope Global (all tenants) or Profile-specific Assigned Profile (all users with that role) Individual user account only

Storage Compiled extension package ( .app ) Tenant database system tables Tenant database user metadata tables

AL Code / Triggers views in pageextension can trigger AL code; pagecustomization cannot No AL code (declarative UI only) No AL code (declarative UI only)

Maintenance Version-controlled in Git repository Exportable / Importable XML/JSON profiles Managed in User Personalizations page

Extensibility Can introduce new schema (via pageextension ) Cannot introduce new fields not in dataset Cannot introduce new fields not in dataset

Exam Traps & Best Practices

Trap 1: Attempting code in pagecustomization : If an exam question presents a scenario where business logic must execute when a specific role opens a page, the solution is NOT a pagecustomization . The developer must use a pageextension with conditional logic checking the active user's assigned profile ( UserPersonalization.Get(UserSecurityId()) ).

Trap 2: SharedLayout defaults : By default, SharedLayout is true . To give a view its own column order or visible fields, SharedLayout = false must be explicitly specified alongside an inner layout block.

Trap 3: Profile Assignment : Setting Enabled = false on a profile object prevents users from selecting it in My Settings , but does not delete the profile definition from the database.