Working with apps
Working with apps covers how to configure and package Business Central extensions in AL: app identity in app.json, runtime version choice, bundled resources, data added at install, and library and dependency apps. It answers setup and manifest questions for extension developers.
Path: Development > Development environment > Working with apps · tier official · system administration · narrative reviewed (checked by Opus)
Overview
This section is about the app-level settings and contents of a Business Central extension, mostly driven by the app.json manifest. It covers who the app is (ID, name, publisher, version, scope), which runtime version it targets, and what it carries with it (resources and data).
Start with App identity and Choose runtime version in AL, since they define the manifest basics. Then use Adding and Accessing Resources and Adding data for Extensions when the app needs to ship files or install-time data. The FAQ on library and dependency apps explains shared code across Marketplace apps and how dependencies get installed.
Key points
- App identity describes the app.json fields for app ID (GUID), version, name, publisher and scope (Global/Tenant), and when it is acceptable to change them.
- The runtime version is set in app.json (for example “runtime”: “18.0”); an extension can be published to servers with an equal or later runtime version.
- Resources are packaged with resourceFolders and publicResourceFolders in app.json; private resources are used locally, public ones can be read by other extensions.
- Resource limits are 16 MB per file, 128 MB per folder and 256 files; resources require runtime version 18.0.
- Extensions can include permission sets, web services, table data and custom report layouts to be imported during installation.
- The NavApp.LoadPackageData procedure is part of loading packaged table data.
- Library apps hold shared code for multiple Marketplace apps and are installed automatically as dependencies.
- The FAQ also touches on version control and technical validation of library apps.
Learn pages
- Adding and Accessing Resources in Business Central extensions: Describes how to package, share, and access resources, such as sample data, images, and schemas, across Business Central extensions.
- Adding data for Extensions: How you can add data such as permisisons, web services, and table data for an extension.
- App identity: Describes what makes up the app identity of an app for Business Central.
- Choose runtime version in AL: How to choose runtime in AL for Business Central.
- FAQ about Library & Dependency Apps in Business Central: Get answers to some of your questions about library apps and dependency apps in Dynamics 365 Business Central
Source: Microsoft Learn (CC BY 4.0). Descriptions are Learn’s own.