{"title":"Development in AL","url":"https://jonas-paprotka.de/docs/dev-itpro/developer/devenv-dev-overview/","by":"JOP-AL","license":"Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-dev-overview, MicrosoftDocs/dynamics365smb-devitpro-pb at 828b6ee (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact.","credit":"Microsoft Corporation, CC BY 4.0","origin":"https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-dev-overview","source":{"name":"Business Central developer and IT pro docs","repo":"https://github.com/MicrosoftDocs/dynamics365smb-devitpro-pb","commit":"828b6ee72fcd75755627cd6011f3d20899217ab2","date":"2026-11-19"},"checked":"2026-11-19","description":"Overview of the development experience for building extensions using the AL language.","date":"2026-03-19","meta":{"topic":"overview"},"outline":[{"level":1,"title":"Development in AL","slug":"development-in-al","at":0,"chars":7309},{"level":2,"title":"Understanding objects in the development environment","slug":"understanding-objects-in-the-development-environment","at":914,"chars":2132},{"level":2,"title":"Developing extensions in Visual Studio Code","slug":"developing-extensions-in-visual-studio-code","at":3046,"chars":1251},{"level":2,"title":"Extending the functionality of Business Central","slug":"extending-the-functionality-of-business-central","at":4297,"chars":623},{"level":2,"title":"Designer","slug":"designer","at":4920,"chars":286},{"level":2,"title":"Compiling and deploying","slug":"compiling-and-deploying","at":5206,"chars":374},{"level":2,"title":"Instrumenting your app with telemetry","slug":"instrumenting-your-app-with-telemetry","at":5580,"chars":361},{"level":2,"title":"Evaluating AL coding agents with BC-Bench","slug":"evaluating-al-coding-agents-with-bc-bench","at":5941,"chars":323},{"level":2,"title":"Submitting your app","slug":"submitting-your-app","at":6264,"chars":470},{"level":2,"title":"Related information","slug":"related-information","at":6734,"chars":575}],"text":"# Development in AL\n> NOTE\n> We're working to improve the onboarding experience for AL developers. If you have feedback about this article, use the Feedback section at the bottom of the article to tell us what you'd like to see.\n> We also welcome contributions to our documentation. Learn more about contributing in Contribute to the help<../help/contributor-guide#contributing>.\nExtensions are a programming model where you define functionality as an addition to existing objects. You can use extensions to define how they're different or modify the behavior of the solution. This section explains how you can develop extensions by using the development environment for Dynamics 365 Business Central.\nIf you're new to building extensions, read this document to get an understanding of the basics and terms you encounter while working. Next, follow the Get Started with AL<devenv-get-started> to set up the tools.\n## Understanding objects in the development environment\nAll functionality in Business Central is coded in objects. The extension model is object-based; you create new objects, and extend existing objects depending on what you want your extension to do.\n Table objects define the table schema that holds data.\n Page objects represent the pages seen in the user interface.\n Codeunits contain code for logical calculations and for the application behavior.\n Report objects define the layout and data for reports.\nLearn more about the objects that you can create for your extension in devenv-extension-object-overview.\nThese objects are stored as code, known as AL code, and are saved in files with the `.al` file extension. The AL Language extension for Microsoft Dynamics 365 Business Central also supports the multi-root functionality, which allows you to work with multiple AL folders within one workspace. Learn more about how to group a set of disparate project folders into one workspace in Working with multiple AL project folders within one workspace<devenv-multiroot-workspaces>.\n> NOTE\n> A single .al file might contain multiple objects, however, it's a best practice to have one object per file.\nTable extension objects and page extension objects are used to add or override changes to table or page objects. For example, consider a business that sells organic food, and the business wants to add two extra fields; Organic and `Local Produce` in its existing item table. The business uses a table extension object to define those extra fields. The table extension makes the newly added fields available for use in the item table. You can store data in these fields and access them by code. You can then use the page extension object to display the fields in the UI.\n> NOTE\n> Extension objects can have a name with a maximum length of 30 characters.\nYou have several options for creating new objects with the AL Language extension for Microsoft Dynamics 365 Business Central for Visual Studio Code. Learn more about the objects that you can create for your extension in AL development environment<devenv-reference-overview>.\n## Developing extensions in Visual Studio Code\nUsing the AL Language extension for Microsoft Dynamics 365 Business Central for Visual Studio Code, you get the benefits of a modern development environment along with seamless publishing and integration with your Business Central tenant. Learn more about the setup in Get started with AL<devenv-get-started>.\nBy using Visual Studio Code and the AL Language extension for Microsoft Dynamics 365 Business Central, you can complete the following tasks:\n Create new files for your solution.\n Get assistance with the creation of appropriate settings and configuration files.\n Use code snippets to help create application objects.\n Receive compiler validation while you code.\n Use an efficient publishing process. You can publish and see your code running by just selecting Ctrl+F5.\n> NOTE\n> For some users, the Ctrl+F5 shortcut key might not work due to keyboard or other settings. If it doesn't work for you, run your code by choosing Run Without Debugging from the Run menu in Visual Studio Code.\n> TIP\n> Use Ctrl+Space to trigger IntelliSense and get assistance on code completion, parameter info, quick info, and member lists. For more information about snippets, see Syntax and snippets<devenv-syntax>.\n## Extending the functionality of Business Central\nYou can extend the functionality of Business Central in several ways: you can extend tables, enumerations, application areas, pages, reports, code flows, and the security model directly in AL. But you can also contribute directly to the base application in the open source projects for the system application modules.\nLearn more about the extensibility options available to AL developers in Business Central including examples on how to extend various features, such as extending item charges, best price calculations, and data archiving in devenv-extensibility-overview.\n## Designer\nDesigner works in the client and allows you to design pages using drag and drop components. Designer lets you build extensions in the client itself by rearranging fields, adding fields, and previewing your changes in page design. See Use Designer<devenv-inclient-designer>.\n## Compiling and deploying\nCompile extensions as `.app` package files. Deploy the `.app` package file to the Business Central server. A `.app` package contains the various artifacts that deliver the new functionality to the Business Central deployment and a manifest that specifies the name, publisher, version, and other attributes of the extension. See devenv-json-files.\n## Instrumenting your app with telemetry\nBusiness Central emits telemetry data for several operations that occur when extension code runs. You can configure your extension to send this data to a specific Application Insights resource on Microsoft Azure. See Sending extension telemetry to Azure Application Insights<devenv-application-insights-for-extensions>.\n## Evaluating AL coding agents with BC-Bench\nBC‑Bench is a benchmarking framework for evaluating agent performance on real‑world Business Central AL coding tasks. It provides measurable, repeatable results, helping developers understand what improvements actually work. See https://github.com/microsoft/BC-Bench on GitHub.\n## Submitting your app\nAfter development and testing are done, you can submit your extension package to Marketplace. Before you submit the extension package, we encourage you to read the checklist to facilitate the validation process. See Checklist for submitting your app<devenv-checklist-submission>. To get code validation helping you to bring your extension package to Marketplace, you can enable the AppSourceCop code analyzer. See devenv-using-code-analysis-tool.\n## Related information\nGet started with AL<devenv-get-started>\nGet started developing Connect apps for Dynamics 365 Business Central<devenv-develop-connect-apps>\ndevenv-keyboard-shortcuts\nAL development environment<devenv-reference-overview>\nDocumenting your code with XML comments<devenv-xml-comments>\nFAQ for developing in AL<devenv-dev-faq>\nSending extension telemetry to Azure Application Insights<devenv-application-insights-for-extensions>\nAI agent tools for AL development<al-agent-tools/al-agent-tools-overview>\nAL LSP for AI agents and editors<devenv-al-tool#al-lsp>"}