10.1 Profile Objects & Custom Page Views in AL

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

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.

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:

1. 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.
2. 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.
3. 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().
4. 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

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.