Customization, Extensions & Integration: Extending Business Central Capabilities

Part 5 of 8 in the Business Central Implementation Series

Published: December 2025 | Reading Time: 15 minutes

Introduction

While Business Central provides extensive out-of-the-box functionality, every business has unique requirements that may not be fully addressed by standard features. This is where customization, extensions, and integrations come into play—allowing you to tailor Business Central to your specific needs while maintaining upgrade compatibility and system integrity.

The modern approach to extending Business Central has evolved significantly. Gone are the days of directly modifying base application code. Today's extensibility model, based on AL language extensions, enables powerful customization while preserving your ability to receive updates and new features from Microsoft seamlessly.

This comprehensive guide explores the full spectrum of Business Central extensibility—from understanding when customization is necessary, to developing AL extensions, leveraging AppSource applications, and integrating with external systems.

Understanding Business Central Extensibility Model

Microsoft has built Business Central on a modern, extension-based architecture designed for cloud-first operations.

The Extension Framework

Why Extensions Matter:

Traditional ERP customization required modifying source code, creating several problems:

• Upgrade complexity and potential breakage

• Vendor support complications

• Testing burden for every update

• Code conflicts between customizations

Business Central's extension model solves these issues:

• Isolation: Extensions don't modify base code

• Upgrade Safety: Microsoft updates don't break extensions

• Maintainability: Clear separation between standard and custom

• Portability: Extensions can be installed/uninstalled cleanly

Extension Capabilities:

Extensions can:

• Add new pages, reports, and objects

• Extend existing tables with new fields

• Subscribe to events in base application

• Modify page layouts and add fields

• Create custom business logic

• Integrate with external services

• Add new APIs

Extensions cannot:

• Delete or modify base objects directly

• Override standard business logic (must use events)

• Access private methods or variables

AL Language Fundamentals

Business Central extensions are written in AL (Application Language)—a modern, structured language purpose-built for business applications.

AL Basics:

Object Types:

• Tables: Data structures for storing information

• Pages: User interface for data entry and viewing

• Reports: Document generation and data analysis

• Codeunits: Business logic containers

• Queries: Data retrieval and analysis

• XMLPorts: Data import/export

• Enums: Enumeration types for option fields

Development Environment:

• Visual Studio Code with AL Language extension

• AL Language extension provides IntelliSense, debugging, compilation

• Git or Azure DevOps for source control

• Docker containers for local development environments

Example AL Code Structure:

tableextension 50100 CustomerExt extends Customer
{
    fields
    {
        field(50100; "Customer Tier"; Option)
        {
            OptionMembers = Bronze,Silver,Gold,Platinum;
            OptionCaption = 'Bronze,Silver,Gold,Platinum';
            DataClassification = CustomerContent;
        }
        field(50101; "Loyalty Points"; Integer)
        {
            DataClassification = CustomerContent;
        }
    }
}

pageextension 50100 CustomerCardExt extends "Customer Card"
{
    layout
    {
        addafter(Name)
        {
            field("Customer Tier"; "Customer Tier")
            {
                ApplicationArea = All;
            }
            field("Loyalty Points"; "Loyalty Points")
            {
                ApplicationArea = All;
            }
        }
    }
}

Standard Customization Options vs. Custom Development

Before building custom solutions, explore configuration-based customization.

Configuration-Based Customization

Business Central offers extensive customization without code:

Page Personalization:

• Users customize their own page layouts

• Show/hide fields and columns

• Rearrange sections

• Filter and sort preferences

• Saved per user

Profile Configuration:

• Administrators design role-specific layouts

• Define default views for user groups

• Configure navigation and actions

• Embed reports and charts

Report Layouts:

• Modify existing report layouts using Word or RDLC

• Customize forms, invoices, statements

• Add logos and branding

• Adjust formatting and sections

• Multiple layouts per report for different purposes

Workflow Configuration:

• Define approval workflows without code

• Configure notification rules

• Set up automated responses

• Establish escalation procedures

Custom Report Selection:

• Assign custom layouts to documents

• Configure per-customer/vendor layouts

• Multi-language document support

When Configuration Is Enough:

• Cosmetic changes (colors, fonts, layouts)

• User interface rearrangement

• Report formatting adjustments

• Workflow routing modifications

• Role-based view customization

When Custom Development Is Needed

Indicators for Custom Development:

New Business Logic:

• Complex calculations not available in standard

• Industry-specific business rules

• Custom validation requirements

• Automated process orchestration

Additional Data Storage:

• Tracking information not in standard tables

• Related entity relationships

• Historical audit trails

• Custom categorizations

External System Integration:

• Real-time data synchronization

• API-based connectivity

• Custom file format processing

• Legacy system interfacing

Unique Reporting Needs:

• Complex data aggregation

• Custom analytical reports

• Regulatory compliance reporting

• Industry-specific documentation

Process Automation:

• Scheduled background jobs

• Triggered automation

• Cross-module orchestration

• Mass update capabilities

Creating Custom Reports and Layouts

Reports are among the most common customization needs.

Report Development Approaches:

Custom Report Layouts (No Code)

Word Layouts:

• Best for forms and documents (invoices, POs, packing slips)

• Drag-and-drop design in Word

• Use standard Word formatting

• Insert Business Central data fields

• Add images, logos, tables

• Support for multiple languages

Creating Word Layout:

1. Export existing layout as starting point

2. Open in Word

3. Modify design using Custom XML part fields

4. Save and import back to Business Central

5. Assign to report/document

RDLC Layouts:

• Best for complex analytical reports

• Pixel-perfect formatting control

• Charts, graphs, matrices

• Advanced grouping and calculations

• Created using Visual Studio Report Designer

Custom Report Development (AL Code)

When to Build Custom Reports:

• Unique data combinations not available in standard reports

• Complex calculations or algorithms

• Integration with external data

• Performance optimization for large datasets

Report Structure:

report 50100 "Custom Sales Analysis"
{
    UsageCategory = ReportsAndAnalysis;
    ApplicationArea = All;
    Caption = 'Custom Sales Analysis';
    DefaultLayout = RDLC;
    RDLCLayout = './CustomSalesAnalysis.rdl';

    dataset
    {
        dataitem(Customer; Customer)
        {
            column(No_; "No.")
            {
            }
            column(Name; Name)
            {
            }
            dataitem(SalesLine; "Sales Line")
            {
                DataItemLink = "Sell-to Customer No." = FIELD("No.");
                column(Amount; Amount)
                {
                }
                column(Quantity; Quantity)
                {
                }
            }
        }
    }

    requestpage
    {
        layout
        {
            area(content)
            {
                group(Options)
                {
                    field(DateFilter; DateFilter)
                    {
                        ApplicationArea = All;
                        Caption = 'Date Filter';
                    }
                }
            }
        }
    }
}

Best Practices:

• Start with existing similar reports

• Optimize data retrieval for performance

• Provide user-friendly parameters

• Test with production data volumes

• Document report purpose and usage

• Consider localization needs

Developing Custom Pages and Extensions

Extend user interface to support custom processes.

Page Extension Example:

Adding fields to existing pages:

pageextension 50101 ItemCardExt extends "Item Card"
{
    layout
    {
        addafter(Description)
        {
            field("Brand Name"; "Brand Name")
            {
                ApplicationArea = All;
                ToolTip = 'Brand name for this item';
            }
        }
        
        addafter("Base Unit of Measure")
        {
            field("Eco Friendly"; "Eco Friendly")
            {
                ApplicationArea = All;
            }
        }
    }

    actions
    {
        addafter(Prices)
        {
            action(CalculateMargin)
            {
                ApplicationArea = All;
                Caption = 'Calculate Margin';
                Image = Calculate;
                
                trigger OnAction()
                var
                    ItemMgt: Codeunit "Item Management";
                begin
                    ItemMgt.CalculateMargin(Rec);
                end;
            }
        }
    }
}

Custom Page Development:

Creating entirely new pages:

page 50100 "Customer Loyalty Card"
{
    PageType = Card;
    SourceTable = Customer;
    Caption = 'Customer Loyalty';

    layout
    {
        area(content)
        {
            group(General)
            {
                field("No."; "No.")
                {
                    ApplicationArea = All;
                }
                field(Name; Name)
                {
                    ApplicationArea = All;
                }
                field("Customer Tier"; "Customer Tier")
                {
                    ApplicationArea = All;
                }
            }
            group(Loyalty)
            {
                field("Loyalty Points"; "Loyalty Points")
                {
                    ApplicationArea = All;
                }
                field("Points This Year"; PointsThisYear)
                {
                    ApplicationArea = All;
                    Editable = false;
                }
            }
        }
    }
}

Integration Architecture and Options

Connect Business Central with external systems and services.

Power Platform Integration

Microsoft's Power Platform provides powerful low-code/no-code integration capabilities.

Power BI Integration:

Built-in Capabilities:

• Embedded Power BI reports in Business Central pages

• Direct connector to Business Central data

• Real-time data refresh

• Role-based report distribution

• Mobile Power BI app access

Implementation:

1. Create Power BI workspace

2. Connect to Business Central using connector

3. Build reports and dashboards

4. Publish to Power BI service

5. Embed in Business Central pages

Use Cases:

• Executive dashboards

• Sales analytics

• Financial reporting

• Operational metrics

• Predictive analytics

Power Automate Integration:

Automation Scenarios:

• Approval workflow notifications

• Document routing

• Data synchronization

• Email automation

• Social media posting

Example Flow:

Power Apps Integration:

Mobile App Development:

• Custom data entry forms

• Field service applications

• Inspection checklists

• Time tracking

• Expense reporting

Canvas Apps: Pixel-perfect custom design Model-Driven Apps: Data-centric applications

Microsoft 365 Integration

Seamless integration with Office applications.

Outlook Integration:

• Contact synchronization

• Attach Business Central documents to emails

• Track email conversations by customer

• Convert emails to sales opportunities

• Schedule follow-ups

Excel Integration:

• Edit in Excel functionality

• Export lists and reports

• Excel-based data import

• Financial report designer using Excel

• Budget worksheets

Teams Integration:

• Share Business Central records in Teams chats

• Collaborate on documents

• Search Business Central from Teams

• Notifications and alerts in Teams

• Embed Business Central tabs in Teams channels

SharePoint Integration:

• Document attachments stored in SharePoint

• Approval workflows

• Document libraries

• Version control

• Collaborative document editing

Third-Party Integrations

Connect Business Central with external applications.

Common Integration Scenarios:

CRM Integration (Salesforce, HubSpot):

• Customer and contact synchronization

• Opportunity to quote conversion

• Order status visibility

• Customer service case tracking

E-Commerce Integration (Shopify, Magento, WooCommerce):

• Product catalog synchronization

• Real-time inventory updates

• Order import from web store

• Fulfillment status updates

• Customer data synchronization

Shipping Integration (FedEx, UPS, DHL):

• Rate calculation

• Label generation

• Tracking number assignment

• Shipment status updates

• Address validation

Banking Integration:

• Bank statement import (OFX, BAI)

• Payment file export (ACH, SEPA, ISO20022)

• Positive pay file generation

• Lockbox processing

• Cash position reporting

Payment Gateway Integration (Stripe, PayPal, Authorize.net):

• Credit card processing

• Payment tokenization

• Refund processing

• Recurring billing

• Payment reconciliation

API and Web Services

Technical integration methods for system-to-system connectivity.

Business Central API Types:

OData Web Services:

• RESTful API access

• Query Business Central data

• CRUD operations (Create, Read, Update, Delete)

• Filter and search capabilities

• Paging for large datasets

SOAP Web Services:

• Legacy integration method

• Still supported for backward compatibility

• Expose pages and codeunits

• XML-based messaging

API Pages (v2.0):

• Modern RESTful APIs

• Standard endpoints for common entities

• Optimized for performance

• OAuth2 authentication

• Well-documented

Common API Entities:

• Customers, Vendors, Items

• Sales Orders, Purchase Orders, Invoices

• General Ledger Entries

• Inventory

• Financial statements

API Integration Example:

GET https://api.businesscentral.dynamics.com/v2.0/{tenant}/Production/api/v2.0/companies({companyId})/customers
Authorization: Bearer {access_token}

Response:
{
    "value": [
        {
            "id": "guid",
            "number": "10000",
            "displayName": "Adatum Corporation",
            "type": "Company",
            "email": "contact@adatum.com",
            "balance": 15000.00
        }
    ]
}

Integration Middleware:

Consider middleware platforms for complex integrations:

• Azure Logic Apps: Cloud-based integration workflows

• Azure Functions: Serverless integration code

• Dell Boomi: Enterprise integration platform

• Jitterbit: Hybrid integration solution

• MuleSoft: API-led connectivity

AppSource Extensions and Add-ons

Leverage pre-built solutions from Microsoft's marketplace.

AppSource Overview:

Microsoft AppSource offers thousands of pre-built extensions:

• Validated by Microsoft

• Maintained by vendors

• Subscription or perpetual licensing

• Often cheaper than custom development

• Regular updates and support

Popular AppSource Categories:

Industry-Specific Solutions:

• Manufacturing MES

• Retail POS

• Professional services project management

• Construction job costing

• Healthcare compliance

Functional Extensions:

• Advanced warehouse management

• EDI integration

• Quality management

• Lot traceability

• Advanced pricing

Integration Extensions:

• Salesforce connector

• Shopify integration

• Amazon marketplace

• PayPal payments

• DocuSign

Reporting and Analytics:

• Advanced financial reports

• Consolidation tools

• Budgeting and forecasting

• Management reporting

Productivity Tools:

• Document management

• Barcode scanning

• Mobile applications

• Automated workflows

Evaluating AppSource Extensions:

Selection Criteria:

• Functionality: Does it meet your requirements?

• Reviews and Ratings: What do other users say?

• Vendor Reputation: Is the vendor established and reliable?

• Support: What support options are available?

• Pricing: License cost and ongoing fees?

• Updates: How frequently is it updated?

• Dependencies: Does it require other extensions?

Trial and Testing:

• Request trial in sandbox environment

• Test with realistic data and scenarios

• Evaluate performance impact

• Assess user experience

• Verify documentation quality

• Test vendor support responsiveness

Best Practices for Maintaining Upgrade Compatibility

Ensure your customizations survive Business Central updates.

Extension Development Best Practices:

Use Events, Not Direct Modifications:

• Subscribe to published events for custom logic

• Don't modify base tables or code

• Request new events from Microsoft if needed

Follow Naming Conventions:

• Use unique prefixes for custom objects

• Number ranges: 50000-99999 for custom objects

• Descriptive, consistent naming

Respect Data Classification:

• Classify all custom fields appropriately

• Customer Content, Company Confidential, etc.

• Required for GDPR compliance

Version Control:

• Use Git or Azure DevOps

• Commit frequently with meaningful messages

• Branch strategy for different environments

• Tag releases

Automated Testing:

• Write test codeunits for custom logic

• Automated regression testing

• Test after each Business Central update

• CI/CD pipeline integration

Documentation:

• Document extension purpose and functionality

• Maintain changelog

• Document dependencies

• API documentation for integration points

Version Control and ALM (Application Lifecycle Management)

Professional development practices for extension management.

Source Control with Git:

Repository Structure:

Branching Strategy:

• main: Production-ready code

• develop: Integration branch for development

• feature/*: Individual feature development

• hotfix/*: Emergency production fixes

Development Workflow:

1. Development:

   • Create feature branch

   • Develop and test in sandbox

   • Commit regularly

   • Create pull request

2. Code Review:

   • Peer review of changes

   • Automated testing

   • Approval required

3. Integration:

   • Merge to develop branch

   • Deploy to integration environment

   • Integration testing

4. Release:

   • Merge to main branch

   • Create release tag

   • Deploy to production

   • Monitor and support

CI/CD Pipelines:

Azure DevOps Pipeline Example:

trigger:
  - main

pool:
  vmImage: 'windows-latest'

steps:
- task: ALOpsDockerCreate@1
  inputs:
    artifactversion: 'current'
    
- task: ALOpsDockerStart@1

- task: ALOpsAppCompiler@1
  inputs:
    nav_app_version: '1.0.0.0'
    
- task: ALOpsAppPublish@1

- task: ALOpsAppTest@1

- task

Benefits of ALM:

• Repeatable deployments

• Version tracking

• Rollback capability

• Quality assurance

• Team collaboration

• Audit trail

Deliverables: Customization & Integration Phase Outputs

Complete this phase with extensions and integrations in place:

1. Extension Development Checklist

Documentation of all customizations:

• Custom tables and table extensions

• Custom pages and page extensions

• Custom reports

• Integration endpoints

• AppSource extensions installed

2. Integration Architecture Diagrams

Visual documentation showing:

• System integration landscape

• Data flow directions

• Integration methods used

• Security and authentication

• Error handling approaches

3. API Documentation Standards

Complete API documentation:

• Endpoint definitions

• Request/response formats

• Authentication requirements

• Rate limits and throttling

• Error codes and handling

4. Customization Approval Workflow

Governance documentation:

• Change request process

• Development standards

• Testing requirements

• Approval authorities

• Deployment procedures

Conclusion: Extending Business Central Power

Customization, extensions, and integrations transform Business Central from a powerful standard platform into a solution precisely tailored to your unique business needs. The modern extensibility model ensures you can leverage these capabilities while maintaining upgrade safety and system stability.

Key Takeaways:

✓ Leverage Standard First: Explore configuration options before custom development

✓ Use Extensions, Not Modifications: AL extensions maintain upgrade compatibility

✓ Explore AppSource: Pre-built solutions often meet needs faster than custom development

✓ Integrate Thoughtfully: Choose integration methods appropriate to requirements

✓ Maintain Professionally: Source control, testing, and documentation are essential

✓ Plan for the Long Term: Build maintainable, scalable solutions

With your customized, integrated Business Central solution taking shape, you're ready for the next exciting phase: AI & Copilot Capabilities, where you'll explore how artificial intelligence enhances Business Central functionality.

Next in Series: Blog 6: AI & Copilot Capabilities in Business Central - Discover how AI and Copilot features transform daily operations with intelligent assistance.

Download Resources:

• Extension Development Checklist

• Integration Architecture Template

• API Documentation Template

• ALM Best Practices Guide

Questions or Comments? Share your customization and integration experiences in the comments below.

This is Part 5 of an 8-part series on Business Central Implementation. Subscribe to receive notifications when new articles are published.

Tags: #BusinessCentral #ALDevelopment #Extensions #Integration #API #PowerPlatform #CustomDevelopment