What is Business Central app.json?

Definition

Business Central app.json is the application manifest file used in a Business Central AL project to define essential metadata and configuration for an extension. It tells the development environment and Business Central how the extension is identified, versioned, and related to the target application and platform.

The file is written in JSON and typically sits at the root of an AL extension project. Its properties can specify information such as the extension name, publisher, unique identifier, version, supported application version, runtime version, and dependencies. Accurate configuration helps establish a predictable foundation for developing, packaging, deploying, and maintaining Business Central extensions.

Table of Contents

Core Properties of app.json

The app.json file contains properties that describe the extension and its compatibility requirements. Each property has a specific purpose, so developers should configure values according to the target Business Central environment and the extension's architecture.

  • id: Provides the unique identifier for the extension.
  • name: Defines the extension's display name.
  • publisher: Identifies the organization or developer publishing the extension.
  • version: Specifies the extension's release version.
  • application: Identifies the Business Central application version against which the extension is designed.
  • platform: Specifies the supported platform version when applicable to the project configuration.
  • runtime: Defines the AL runtime version required by the extension.
  • dependencies: Lists other applications that the extension requires.

How app.json Supports AL Development

During development, app.json connects the AL source code with the intended Business Central environment. When an extension references objects supplied by another application, dependency information in the manifest helps the compiler resolve those references against the available application symbols.

The file also establishes important version information. Developers can use it to align the extension with the appropriate Business Central application and runtime capabilities before compiling and packaging the project. This makes app.json an important part of extension lifecycle management rather than simply a descriptive project file.

For teams extending ERP functionality, understanding How ERP and Business Processes Work Together can provide useful context for how AL extensions fit into broader ERP integration and finance workflows.

Dependencies and Compatibility

The dependencies section of app.json identifies applications required by the extension. A dependency can provide tables, pages, codeunits, interfaces, enums, events, or other functionality referenced by AL code. The required applications must be available in compatible versions for the extension to build and operate correctly.

Version properties should also be reviewed when moving an extension between Business Central environments or preparing for an application upgrade. Changes to supported APIs, objects, runtime capabilities, or application versions can influence the configuration required in app.json.

For procurement extensions, developers may need to connect standard Business Central functionality with requisitions, approvals, and a purchase order. The manifest should accurately identify any additional application dependencies required to support those processes.

app.json and Finance Operations

Although app.json is a technical configuration file, its settings can influence extensions used by finance teams. An extension supporting financial workflows may depend on applications that provide accounting objects, approval functionality, reporting capabilities, or integrations with external systems.

Cash-related integrations also require attention to the applications and services connected to the extension. When designing processes around liquidity, working capital, forecasting, or treasury decisions, maintaining reliable cash flow information is an important business consideration.

For organizations working with contractor billing processes, the Contractor Invoice Guide can provide educational context on creating, managing, and automating contractor invoices, which may be relevant when an extension connects invoice workflows with Business Central.

app.json in Enterprise ERP Architecture

Business Central extensions can form part of a larger ERP architecture involving finance applications, integrations, reporting services, and specialized business systems. The app.json dependency configuration helps make those relationships explicit within the AL application.

Organizations using centralized financial processes may also need to understand Central Finance as a broader finance architecture concept. This can help teams distinguish the technical configuration of an individual Business Central extension from the organizational design of centralized financial operations.

Currency-sensitive finance processes can require reliable reference rates. Central Bank Exchange Rates provides useful terminology for understanding externally published exchange-rate information and its relevance to financial workflows and currency calculations.

Similarly, organizations subject to external financial data requirements can distinguish application configuration from reporting processes such as Central Bank Reporting, which addresses reporting workflows rather than extension metadata itself.

Best Practices for Managing app.json

Effective app.json management combines precise metadata with disciplined version and dependency governance. Developers should review the manifest whenever an extension is created, upgraded, moved to another Business Central version, or connected to additional applications.

  • Use a unique extension identity: Keep the ID, name, and publisher information consistent with the extension's ownership.
  • Manage versions deliberately: Apply a clear versioning approach when releasing extension updates.
  • Declare dependencies accurately: Include required applications and compatible versions without unnecessary references.
  • Align runtime requirements: Ensure the runtime setting matches the intended Business Central development environment.
  • Validate compatibility: Compile the extension against the target application symbols before deployment.
  • Review configuration during upgrades: Reassess application, platform, runtime, and dependency settings when the target environment changes.

app.json and Connected Finance Automation

Business Central extensions can connect finance workflows with intelligent processing, approvals, tax validation, and payment activities. The manifest provides the technical foundation for declaring applications that support these connected capabilities.

A Flexible Workflow can support policy-driven accrual approval workflows customized by business unit, department, and thresholds. When such capabilities integrate with Business Central, developers should ensure that the required application dependencies and runtime requirements are appropriately represented.

Late Payment Recommendations can support vendor payment scheduling by aligning payment timing with business priorities and cash flow objectives. Where payment functionality is connected through an extension, its application dependencies should be reviewed alongside the related integration.

The Hyperbots Platform can support industry-specific workflows and tax validation using line-level context and business rules. Business Central integration reviews should verify that the extension configuration, dependencies, and exchanged data support the intended finance workflow.

Summary

Business Central app.json is the central AL application manifest that defines key extension metadata, version information, compatibility requirements, runtime settings, and application dependencies. Proper configuration supports reliable compilation, packaging, deployment, upgrades, and integration. For finance-focused Business Central solutions, maintaining accurate app.json settings helps keep extension architecture aligned with accounting, procurement, reporting, cash management, and connected ERP processes.