Study guide
1.3 Base Application, System Application & AppSource
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
1.3 Base Application, System Application & AppSource
Key Takeaways Explain This Topic AI
The Business Central standard application layer is bifurcated into the modular System Application (low-level technical services) and the Base Application (domain ERP business logic).
The System Application is open-source on GitHub, built with a strictly decoupled facade design pattern where public codeunits expose APIs while implementation codeunits remain internal.
Microsoft AppSource validation requires 100% compliance with AppSourceCop rules, zero breaking changes against baseline versions, and full UI/Help metadata.
Developers must register and prepend/append a unique 3-to-4 character prefix or suffix to all object names, field names, actions, and enum values to prevent global collision.
Every AL extension is uniquely defined in app.json by its immutable App ID (GUID), Name, Publisher, and a 4-part Version string (Major.Minor.Build.Revision).
Last updated: August 2026
1.3 Base App, System App & AppSource Publishing Process
To build scalable, certified enterprise applications for Dynamics 365 Business Central, developers must understand the foundational structure of Microsoft's first-party application packages and navigate the rigorous technical validation pipeline required for Microsoft AppSource certification.
1. System Application vs. Base Application Architecture
Historically, the legacy Dynamics NAV application was a monolithic codebase where technical platform utilities and complex accounting logic were intertwined in massive objects (e.g., Codeunit 1 ApplicationManagement ). Modern Business Central architecture splits the first-party application layer into two distinct packages: +-----------------------------------------------------------------------+
- | CUSTOM EXTENSIONS & APP-SOURCE APPS |
- +-----------------------------------------------------------------------+
- │ Depends on
- ▼
- +-----------------------------------------------------------------------+
- | BASE APPLICATION (BaseApp.app) |
- | - General Ledger, Accounts Receivable, Accounts Payable |
- | - Inventory Valuation, Warehousing, Supply Chain |
- | - Sales & Purchase Document Posting Pipelines (Codeunit 80 / 90) |
- | - Manufacturing, Jobs/Projects, Service Management, Fixed Assets |
- +-----------------------------------------------------------------------+
- │ Depends on
- ▼
- +-----------------------------------------------------------------------+
- | SYSTEM APPLICATION (SystemApp.app) |
- | - Cryptography & Hashing (AES, SHA, RSA, X509 Certificates) |
- | - Communication & Email (SMTP, Microsoft Graph, Exchange) |
- | - Identity & Security (Azure AD User, User Permissions, OAuth2) |
- | - Data Formats & IO (JSON, XML, CSV, TempBlob, Base64, Zip) |
- | - Client Enhancements (Camera, Geolocation, Barcode Scanner) |
- | - Diagnostics & Upgrade (Telemetry, Feature Management, Upgrades) |
- +-----------------------------------------------------------------------+
- The System Application
The System Application is a modular, domain-agnostic layer that provides low-level technical capabilities and operating system abstractions:
Modular Architecture: Composed of dozens of self-contained modules (e.g., Cryptography Management , Email , Azure AD Authentication , Guided Experience , Environment Information ).
The Facade Pattern: Each module exposes a single public API codeunit (the "Facade") that developers interact with, while internal logic is encapsulated within internal codeunits ( Access = Internal ). This prevents external extensions from coupling to volatile internal implementation details.
Open Source on GitHub: Microsoft publishes the complete source code of the System Application on GitHub ( microsoft/ALAppExtensions ). The developer community can inspect code, report issues, and submit pull requests (contributing new features or bug fixes directly to the core platform).
The Base Application
The Base Application contains the complete enterprise business logic, accounting rules, posting state machines, and reporting models that define Business Central as an ERP system. It depends directly on the System Application for all underlying technical services.
Loading diagram... System App Facade Pattern & AppSource Validation Pipeline
2. Extension Manifest Anatomy: app.json
Every AL extension is declared and governed by a root configuration manifest file named app.json . This file establishes the unique cryptographic identity, dependencies, platform runtime targets, and security properties of the package. {
- "id": "7c28f114-699e-4e4b-9e4a-569d251d7e29",
- "name": "Advanced Automated Logistics",
- "publisher": "Contoso Solutions Inc.",
- "version": "24.1.1004.0",
- "brief": "Streamlined warehouse logistics and automated package tracking for Business Central.",
"description": "Comprehensive logistics management solution featuring real-time carrier tracking, automated shipping label generation, and advanced warehouse bin optimization.",
- "privacyStatement": "https://www.contoso.com/privacy",
- "EULA": "https://www.contoso.com/eula",
- "help": "https://www.contoso.com/support/logistics",
- "url": "https://www.contoso.com",
- "logo": "assets/contoso_logo_300x300.png",
- "dependencies": [],
- "screenshots": [],
- "platform": "24.0.0.0",
- "application": "24.0.0.0",
- "idRanges": [
- {
- "from": 50100,
- "to": 50149
- }
- ],
- "contextSensitiveHelpUrl": "https://www.contoso.com/help/{0}",
- "showMyCode": false,
- "runtime": "13.0",
- "target": "Cloud"
- }
- Critical Manifest Properties
id (GUID): The immutable, globally unique identifier (UUID v4) of the application. Once published, this GUID can never change, or the system will treat the package as a completely unrelated new application.
name & publisher : Human-readable solution name and organization. The combination of id , name , and publisher forms the unique identity triplet.
version : A 4-part semantic version string formatted as Major.Minor.Build.Revision (e.g., 24.1.1004.0 ). Incremented on each deployment.
idRanges : Defines the permitted integer ID range for custom objects (tables, pages, reports, codeunits, XMLports). Per-Tenant Extensions typically operate in the 50000..99999 range; AppSource ISVs purchase dedicated registered ranges (e.g., 1000000..1099999 ) from Microsoft.
target : Specifies the compilation target. Must be set to "Cloud" for all AppSource apps and SaaS PTEs.
application (not dependencies ): Since Business Central 2020 release wave 2, the System Application and Base Application must not be listed as explicit dependencies . Reference them through the single "application" version property instead; dependencies is reserved for third-party and partner libraries. AppSourceCop enforces this with AS0085 ( Use the 'application' property instead of specifying explicit dependencies ) and AS0100 ( The 'application' property must be specified in the app.json file ).
3. AppSource Technical Validation & AppSourceCop Rules
Publishing an extension to Microsoft AppSource requires passing an automated and manual certification pipeline. Automated technical validation is enforced by the AppSourceCop code analyzer.
1. Mandatory Prefix and Suffix Reservation
To prevent global naming collisions across multiple ISV extensions installed on the same tenant, Microsoft requires all AppSource developers to register a 3-to-4 character prefix or suffix in Microsoft Partner Center (e.g., ABC or CONT ).
Enforcement Rules ( AS0011 , AS0013 ): Every object name, table field, page action, global variable, and enum value must start or end with the registered prefix/suffix.
Valid Table Extension Field: field(50100; "ABC_CarrierTrackingNo"; Code[30]) { ... }
Invalid Table Extension Field: field(50100; "CarrierTrackingNo"; Code[30]) { ... } (Fails AppSourceCop with rule AS0011 ) .
2. Strict Prevention of Breaking Changes
When publishing version updates to an existing AppSource application, AppSourceCop compares the new source code against the previous baseline version ( baselinePackage in settings.json ). The analyzer immediately rejects the package if breaking changes are detected:
AppSourceCop Rule Prohibited Breaking Action Compliant Migration Alternative
AS0001 Tables and table extensions that have been published must not be deleted. Mark the table with ObsoleteState = Pending; and ObsoleteReason = '...'; .
AS0002 Fields must not be deleted. Mark the field with ObsoleteState = Pending; and remove it only after the deprecation window.
AS0004 Fields must not change type (e.g., Text[30] to Code[30] ). Create a new field with the desired type and write an upgrade codeunit to migrate the data.
AS0009 Key fields must not be changed (primary-key structure or order). Never alter primary keys; add a secondary key instead.
AS0018 A procedure belonging to the public API cannot be removed. Keep the procedure and mark it Pending ; add a new overload alongside it.
AS0023 / AS0024 A return type cannot be modified / Parameters cannot be removed or added in external procedures. Add a new procedure rather than changing an existing signature.
3. Additional Quality Analyzers
CodeCop : Enforces AL coding guidelines, naming conventions, and variable scoping.
UICop : Verifies that all page fields and actions have non-empty ToolTip properties and appropriate ApplicationArea assignments for search discovery.
PTECop : Used for Per-Tenant Extensions to ensure compatibility with tenant data isolation rules.