Study guide

3.2 Report Layout Management & Copilot AI Capabilities

Microsoft Dynamics 365 Business Central Functional Consultant MB-800

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Company Creation & Data Migration

1.1 Creating Companies & Assisted Setup Wizards 1.2 Configuration Packages & RapidStart Worksheets 1.3 Opening Balances & Data Migration Strategies

2 Chapter 2: Security, Profiles & Auditing

2.1 Users, User Setup & Role Center Profiles 2.2 Permission Sets & Security Group Management 2.3 Security Filters, Change Log & Security Auditing

3 Chapter 3: Core System Configuration, Number Series & Copilot

3.1 Company Information, Number Series & Job Queues 3.2 Report Layout Management & Copilot AI Capabilities

4 Chapter 4: Dimensions Architecture & Governance

4.1 Dimension Concepts & Dimension Values 4.2 Global Dimensions vs Shortcut Dimensions 4.3 Default Dimensions, Combinations & Priorities

5 Chapter 5: Workflows & Approvals

5.1 Native Workflow Templates & Approval Hierarchy 5.2 Workflow User Groups & Notification Configuration

6 Chapter 6: Financial Setup, Periods & Currencies

6.1 General Ledger Setup & Accounting Periods 6.2 Payment Terms, Payment Methods & Deferrals 6.3 Multi-Currency Setup & Exchange Rates

7 Chapter 7: Chart of Accounts, Categories & Allocations

7.1 Chart of Accounts Structure & G/L Account Cards 7.2 Account Categories, Subcategories & Financial Reporting 7.3 General Ledger Allocation Accounts & Sharing

8 Chapter 8: Posting Groups & Posting Setup

8.1 Specific Posting Groups: Customer, Vendor, Bank & Inventory 8.2 General Posting Groups & General Posting Setup Matrix 8.3 Inventory Posting Setup & Alternative Posting Groups

9 Chapter 9: General Journals & Recurring Methods

9.1 Bank Account Cards & Posting Setup 9.2 General Journal Templates, Batches & Number Series 9.3 Recurring General Journals & Allocation Methods

10 Chapter 10: Accounts Payable & Accounts Receivable Setup

10.1 Purchases & Payables Setup & Vendor Master 10.2 Sales & Receivables Setup & Customer Master 10.3 Payment Journals, Cash Receipts & Payment Registration Setup

11 Chapter 11: Fixed Assets Setup & Depreciation Books

11.1 Fixed Asset Setup, Classes & Depreciation Books 11.2 Fixed Asset Cards, Main/Component Assets & Depreciation Methods

12 Chapter 12: Inventory Setup, Costing & Locations

12.1 Inventory Setup, Item Types, Categories & Variants 12.2 Costing Methods (FIFO, LIFO, Average, Standard) & Ledger Architecture 12.3 Locations, Transfer Routes & Stockkeeping Units (SKUs)

13 Chapter 13: Logistics Master Data, Pricing & Discounts

13.1 Shipping Agents, Locations & Vendor Lead Times 13.2 Sales Prices, Purchase Prices & Price Lists 13.3 Line Discounts, Invoice Discounts & Thresholds

14 Chapter 14: User Interface, Views, Inspection & Excel

14.1 Personalization, Profile Customization & Designer 14.2 Searching, Advanced Filters, Saved Views & Page Inspection 14.3 Edit in Excel, OneDrive & Data Analysis Mode

15 Chapter 15: Purchase & Sales Order Execution

15.1 Purchase Orders, Receiving, Over-Receipt & Undo 15.2 Purchase Invoicing, Recurring Lines & Blanket Orders 15.3 Sales Quotes, Availability Checks & Order Conversion 15.4 Sales Shipping, Invoicing, Undo & Blanket Orders

16 Chapter 16: Invoices, Credit Memos & Document Corrections

16.1 Direct Invoices, Credit Memos & Document Reopening 16.2 Correct, Cancel & Corrective Credit Memo Procedures 16.3 Combined Shipments/Receipts & Prepayment Workflows

17 Chapter 17: Cash Management, Bank Reconciliation & Ledger Applications

17.1 Processing Payment Journals & Cash Receipt Registrations 17.2 Applying, Unapplying & Reversing Customer/Vendor Entries 17.3 Bank Account Reconciliation & Statement Matching Rules

18 Chapter 18: Operational Adjustments, Inventory & Asset Accounting

18.1 Exchange Rate Adjustments & Dimension Corrections 18.2 Inventory Adjustments, Transfers & Physical Counting 18.3 Fixed Asset Acquisitions, Depreciation Runs & Disposals

3.2 Report Layout Management & Copilot AI Capabilities

Key Takeaways Explain This Topic AI

Report Selection tables map document transaction types (Quotes, Invoices, Shipments) to AL report objects and designate specific custom layouts for PDF attachments and HTML email bodies.

Business Central supports Word, RDLC, and Excel report layouts — Word for customer-facing branded documents, built through the XML Mapping Pane with repeating line rows enclosed in a Repeating Section Content Control, RDLC for complex grouped reporting, and Excel for analytical data contracts.

Copilot is a system feature that cannot be switched on or off tenant-wide; administrators activate or deactivate individual capabilities on the Copilot & agent capabilities page, and since update 25.0 both data movement and all features are on by default.

Copilot access is granted per capability — the Copilot Sys Features permission set (or system objects 9680/9690/9700/9710) plus feature-specific page permissions — and Business Central has no single "Copilot" permission set.

Business Central distinguishes Copilot capabilities, which assist a user inside a page, from agents (Sales Order Agent, Payables Agent, Expense Agent), which hold their own licensed user and work a task to a human review checkpoint.

Last updated: September 2026

Report Layout Management & Copilot AI Capabilities

Exam Focus: The blueprint objective "Set up core functionality" was rewritten as a Major change in the June 30, 2026 update, and "Enable Copilot and agent capabilities" is the bullet that arrived with it. Expect questions on report routing via Report Selection tables and on the differences between Word, RDLC, and Excel layouts — but also on where Copilot is governed (there is no tenant-wide on/off switch), when the Allow data movement toggle even appears, which permission each capability needs, and how a Copilot capability differs from an agent .

Modern enterprise reporting demands flexibility ranging from pixel-perfect customer-facing invoices to dynamic analytical spreadsheets, while emerging generative AI capabilities drive unprecedented automation across daily accounting routines. This section covers how Business Central separates reporting datasets from visual presentations and how to configure and govern built-in Copilot capabilities.

1. Report Layout Architecture & Document Routing

In Dynamics 365 Business Central, report execution is built on a decoupled architecture:

Report Object (AL Code) : Defines the underlying data structure, business logic, calculated columns, and dataitem hierarchies (such as linking the Sales Header table to child Sales Line records). The report dataset remains consistent regardless of how data is rendered.

Report Layout : Defines the visual presentation layer (fonts, positioning, tables, brand colors, and page pagination). A single report object can have multiple layouts tailored for different operational contexts.

Report Selection Setup

Document routing is governed by dedicated Report Selection configuration pages across functional application areas:

  • Report Selection - Sales ( Page 306 )
  • Report Selection - Purchase ( Page 347 )
  • Report Selection - Bank Account ( Page 385 )

Report Selection - Cash Receipts / Inventory +-----------------------------------------------------------------------------------------+

  • | Usage: S.Invoice (Sales Invoice) |
  • |-----------------------------------------------------------------------------------------|
  • | Sequence | Report ID | Report Caption | Use for Email Body | Email Body Layout |
  • | :--- | :--- | :--- | :--- | :--- |
  • | 1 | 1306 | Standard Sales - Inv.| Yes | Custom Word HTML |
  • | 2 | 1306 | Standard Sales - Inv.| No | (Attached as PDF) |
  • +-----------------------------------------------------------------------------------------+
  • Key Columns on Report Selection Pages

Setting / Column Functional Role

Usage Identifies the specific document event trigger (e.g., Quote , Order , Invoice , Credit Memo , Shipment , Work Order , Customer Statement ).

Sequence Defines the execution order if multiple reports are assigned to a single transaction event.

Report ID The numerical identifier of the AL report object to execute (e.g., Report 1306 Standard Sales - Invoice ).

Use for Email Body Indicates whether the output of this report execution should be converted into the rich HTML body of an outbound transactional email.

Email Body Layout Code Designates the specific Word layout used to format the HTML message body.

Use for Email Attachment Directs Business Central to generate the report as an attached document (typically a rendered PDF file) within the outgoing email.

Email Attachment Layout Code Designates the specific layout used to render the attached PDF document.

2. Layout Technologies: Word vs. RDLC vs. Excel

The Report Layouts page ( Page 9660 ) is the administrative hub where consultants create, review, export, and assign default layouts for every report in the system. Business Central supports three distinct layout engines:

Comprehensive Technology Comparison Matrix

Attribute Word Layouts ( .docx ) RDLC Layouts ( .rdl / .rdlc ) Excel Layouts ( .xlsx )

Primary Authoring Tool Microsoft Word (Desktop) Microsoft Report Builder / Visual Studio Microsoft Excel (Desktop)

Target Audience Business Consultants, End Users Technical Developers, Power BI Specialists Financial Analysts, Accountants

Data Schema Interface XML Mapping Pane (Custom XML Part) Report Datasets & Expression Builder Data Contract Table ( Data Sheet)

Repeating Section Tool Repeating Section Content Control Tablix / Group Header & Details Rows Native Excel Tables / PivotTables

Calculation Power Very Limited (basic Word totals) Advanced (VB.NET, aggregations, code) Extensive (Native Excel formulas, DAX)

Interactive Analytics None (Static Document Output) None (Static Document Output) High (Slicers, PivotCharts, Filters)

Best Use Cases Invoices, Quotes, POs, Remittances High-density trial balances, stock reports Financial reviews, inventory aging audits

  • In-Depth Layout Authoring Mechanics
  • 1. Microsoft Word Layouts

Word layouts are the preferred choice for customer-facing documents due to their intuitive typography, simple margin management, and accessibility to non-developers.

Enabling Developer Mode : To edit a layout, open Microsoft Word and enable the Developer tab via Word Options > Customize Ribbon.

Mapping Fields : Open the XML Mapping Pane on the Developer tab. In the Custom XML Part dropdown, select the Business Central schema namespace ( urn:microsoft-dynamics-nav/reports/... ).

Single Value Fields : Highlight placeholder text (such as customer name or document date) in the Word document, right-click the corresponding XML element in the pane, and select Insert Content Control > Plain Text .

Repeating Line Tables (Crucial Rule) : To render repeating transactional lines (such as sales order lines), select the entire table row containing the item fields, right-click the repeating parent line element (e.g., SalesLine ) in the XML Mapping Pane, and select Insert Content Control > Repeating Section . If a designer inserts plain text controls without the repeating section wrapper, only the first line item will render on the output invoice.

2. RDLC Layouts

RDLC (Report Definition Language Client-side) is engineered for high-density, multi-page administrative documents. RDLC layouts support complex grouping logic, group-level subtotals, dynamic visibility toggles, and multi-pass page-count calculations ( Globals!PageNumber of Globals!TotalPages ). However, because Business Central flattens hierarchical datasets into flat Cartesian recordsets before passing them to the RDLC engine, developers must use custom expressions (e.g., First() , Sum() , or custom VB code) to prevent duplicate sums across parent-child joins.

3. Excel Layouts

Excel layouts enable rapid, code-free business intelligence directly from report datasets. When an Excel layout runs:

Business Central streams raw dataset rows into a protected, hidden worksheet named Data structured as an official Excel Table.

The report designer creates additional visible worksheets containing native Excel PivotTables, interactive slicers, Excel formulas (e.g., XLOOKUP , SUMIFS ), and charts referencing the Data table.

Whenever an end user runs the report, Business Central repopulates the Data table and triggers an automatic refresh of all dependent pivot tables and charts.

Critical Rule : Designers must never rename or restructure the Data worksheet, or the automated data binding contract will break.

3. Managing and Deploying Custom Layouts

To manage layouts in modern Business Central:

Search for Report Layouts ( Page 9660 ).

Filter by the desired Report ID (e.g., 1306 ).

Click New Layout to insert a new definition. Specify the Layout Name , select the Type ( Word , RDLC , or Excel ), and choose the target Report ID.

Click Export Layout to download the template file to your local computer for editing in Word, Report Builder, or Excel.

Once modified, return to Business Central and select Replace Layout to upload the finalized file.

Choose Set as Default to enforce the layout for all users in the current company, or assign it conditionally within Report Selection - Sales .

4. Enabling & Governing Copilot and AI Capabilities

Dynamics 365 Business Central embeds next-generation generative AI powered by Azure OpenAI Service , built strictly according to Microsoft Responsible AI standards.

There Is No Copilot On/Off Master Switch

The single most common misconception — and a reliable distractor on the exam — is that an administrator turns Copilot on or off for the tenant. Microsoft's guidance is explicit: Copilot is a system feature and an integral part of Business Central , and like most system features you cannot turn it on or off . What administrators actually control is narrower and more specific:

Whether data may move across geographies (only when the environment requires it).

Whether each individual capability or agent is Active or Inactive.

Which users hold the permissions that each capability requires.

Since update 25.0 , data movement across geographies is enabled by default and all features are activated, so a new environment is Copilot-ready with no configuration unless you deliberately deactivate something.

Data Privacy & Regulatory Compliance Governance

Tenant Isolation : Customer business data, prompts, and completions are isolated to the customer's enterprise boundary. Operational ERP data is never used to train or refine base foundation models.

Geographic Data Movement : The Azure OpenAI Service that Copilot uses is not hosted in every geography where Business Central runs. The Allow data movement toggle appears at the top of the Copilot & agent capabilities page only when your environment's geography differs from the Azure OpenAI geography it would use . If you instead see the "How do I govern my copilot data?" link, the toggle does not apply to your environment and there is nothing to authorize.

When the toggle is present, switching it off deactivates Copilot and all features.

Once an Azure OpenAI Service becomes available in your environment's geography, the environment is connected automatically and the toggle disappears.

In-App Governance: The Copilot & Agent Capabilities Page

Within Business Central, search for the Copilot & agent capabilities page ( Page 7775 ):

Individual Capability Control : The page lists every available Copilot and AI feature with a status of Active or Inactive , split into a preview section and a generally available section. Select a feature and choose Activate or Deactivate . Features are active by default once they become available.

Enable Bing Search : A toggle that lets supported features search the web for broader answers, such as Chat questions about installed add-on apps and extensions.

Rollout Behaviour : Some changes take effect immediately; others require users to sign out and sign back in. To force changes through, cancel user sessions from the Business Central administration center.

Administrator Requirement : Configuring these settings requires SUPER permission or one of the admin licenses (Delegated Admin/Helpdesk agent - Partner, Internal Admin, Internal BC Administrator, Dynamics 365 Administrator). Business Central does not yet offer granular, object-level permissions for configuring Copilot.

Granting User Access: Permissions Are Per Capability

There is no single "Copilot" permission set . Access is granted feature by feature, mostly through ordinary Business Central permission sets and objects:

  • Copilot or agent capability Required permission
  • Chat Copilot Sys Features permission set, or execute permission on system object 9690 Allow Copilot Chat
  • Summarize Copilot Sys Features , or execute permission on system object 9680 Allow Copilot Summary
  • Autofill Copilot Sys Features , or execute permission on system object 9700 Allow Copilot Autofill

Analysis assist Copilot Sys Features (or system object 9710 ), plus Data Analysis - Exec. and Add Related Fields

Bank reconciliation assist Permission on page 7250 Bank Acc. Rec. AI Proposal and page 7252 Trans. To GL Acc. AI Proposal

  • Marketing text suggestions Permission on page 5836 Copilot Marketing Text
  • Sales line suggestions Permission on pages 7275 / 7276 Sales Line AI Suggestions
  • Suggest substitute items Permission on pages 7410 / 7411 Item Subst. Suggestion

No. series suggestions No permission gate — anyone who can set up number series can use it when the feature is active

Sales Order Agent / Payables Agent / Expense Agent Configured on each agent's own setup page (see below), not through a shared permission set

5. Copilot Capabilities vs. Agents (MB-800 Focus)

The blueprint objective is "Enable Copilot and agent capabilities," and the exam draws a hard line between the two words. Keep them separate:

A Copilot capability assists a person who is already doing the work — it suggests, drafts, matches, or summarizes inside a page the user opened. Bank reconciliation assist, marketing text suggestions, and Chat are capabilities.

An agent is assigned its own Business Central user licence and works through a task on its own, pausing for a human to review or approve at defined checkpoints. Agents appear on the Agents page, where an administrator sets the agent's user, its permissions, and which users may review its work.

The built-in agents are the Sales Order Agent , the Payables Agent , and the Expense Agent ; a custom agent design/coding experience is additionally available in preview. All of them appear alongside the capabilities on the Copilot & agent capabilities page for activation, but their user access is managed on each agent's own setup page rather than through a permission set.

  • Copilot Capabilities
  • 1. Bank Account Reconciliation Matching Assistance

Bank reconciliation is traditionally an error-prone, manual operational task. Standard Business Central automated matching relies on strict rules (matching exact transaction amount and statement date within tolerance). However, imported bank statement descriptions frequently contain scrambled vendor names, reference prefixes, or deducted wire fees that fail standard rules.

Copilot Semantic Matching : Powered by Azure OpenAI, Copilot analyzes unmatched statement lines and open Bank Account Ledger Entries, performing semantic interpretation on payment descriptions, date ranges, and combined amounts.

Match Categorization : Copilot groups suggestions into confidence tiers with clear textual reasoning (e.g., "Matched based on invoice number 1024 appearing inside the unstructured description text despite slight payee name variation" ).

Human-in-the-Loop Principle : Copilot never directly posts or reconciles entries autonomously. All proposed matches are highlighted in the Bank Account Reconciliation worksheet for the accounting clerk to review, modify, accept, or reject.

2. Marketing Text Suggestions for Items

Retailers and distributors must create compelling, search-engine-optimized product copy for eCommerce portals and sales catalogs.

Contextual Generation : Located directly on the Item Card , clicking the Marketing Text action prompts Copilot to read structured item master attributes, including Description , Item Category Code , Color , Material , Dimensions , and vendor specifications.

Stylistic Control : Users can configure the desired Tone of Voice (Formal, Casual, Inspiring, Creative, or Educational) and emphasize specific product attributes.

Review and Commit : The resulting marketing text is presented in a modal preview window. The merchandiser can edit the draft directly before saving it to the item record.

3. Chat with Copilot & Natural Language Inquiries

End users can leverage natural language conversational chat to query business data ( "Show me top 5 overdue customers" ), navigate system configuration pages ( "How do I set up number series?" ), or understand application error messages. Chat requires the Copilot Sys Features permission set or execute permission on system object 9690, and can optionally search the web when Enable Bing Search is turned on.

Built-In Agents

Agent What it does Where access is configured

Sales Order Agent Monitors an inbound mailbox for customer sales requests, drafts the quote or sales order from the message, and hands it to a reviewer before it is confirmed. Sales Order Agent setup page — assign the agent user and the users allowed to review its work

Payables Agent Works the accounts payable queue: picks up incoming vendor invoices, matches them to purchase orders and receipts, and prepares them for a human to approve. Payables Agent setup page — agent permissions and user access are managed there

Expense Agent Processes submitted expenses and prepares the resulting entries for review. Expense Agent configuration page

Custom agents (preview) Partners and customers design or code their own agents with the agent SDK/design experience. Agent design experience and the agent SDK

Note

Because an agent holds its own licensed Business Central user, its actions are attributable in the change log and audit trail exactly like a human user's. The reviewer checkpoint, not the model, is what keeps an agent inside your approval controls — the same human-in-the-loop principle that governs the Copilot capabilities above.

6. Common Implementation Pitfalls & Exam Traps

Pitfall 1: Missing Repeating Section Control in Word. Placing plain text XML fields directly inside a Word table row without wrapping the row in a Repeating Section Content Control. The rendered document will output only a single item row regardless of how many sales lines exist.

Pitfall 2: Renaming the Data Sheet in Excel Layouts. Modifying the name or table header bindings of the Data sheet in an Excel report layout. Business Central fails to stream dataset records into the workbook, throwing a runtime layout contract error.

Pitfall 3: Assuming Copilot Auto-Posts Transactions. Believing that enabling Copilot for Bank Reconciliation eliminates clerk oversight. Business Central architecture strictly enforces that AI generates recommendations —a human user must validate and post the reconciliation.

Pitfall 4: Neglecting Cross-Region Authorization. Attempting to troubleshoot why Copilot features are missing in European or Asia-Pacific tenants without checking the Allow data movement across regions toggle in the Admin Center.

Loading diagram... Copilot AI Architecture and Human-in-the-Loop Governance Flow