{"title":"Extension objects overview","url":"https://jonas-paprotka.de/docs/dev-itpro/developer/devenv-extension-object-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-extension-object-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-extension-object-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":"Get an overview of the extension objects you can create in AL for Business Central.","date":"2024-03-11","meta":{"topic":"overview"},"outline":[{"level":2,"title":"Extension objects in the same app","slug":"extension-objects-in-the-same-app","at":1306,"chars":1754},{"level":2,"title":"Related information","slug":"related-information","at":3060,"chars":273}],"text":"This article provides an overview of the different extension objects that you can write to extend base application functionality in Business Central. You can use extension objects to extend tables, pages, reports, and enums. For example, by using an extension object, you can add new fields, actions, and layout to an existing page, or add data items, columns, request pages, and layouts to an existing report. By using an enum extension, you can add new values to an existing enumeration.\nFor a base object to be extensible, you must mark it with the property `Extensible = true;`. The default value for all objects is that they're extensible. Therefore, you don't have to specify this property explicitly in your code.\nThe following table lists the different extension objects that you can create in AL.\nObject type|Description\nTable extension<devenv-table-ext-object>|Add fields to an existing table.\nPage extension<devenv-page-ext-object>|Add fields, actions, and layout to an existing page.\nReport extension<devenv-report-ext-object>|Add data items, columns, request pages, and layouts to an existing report.\nEnum extension<devenv-extensible-enums>|Add new values to an existing enumeration.\nPermission set extension<devenv-permissionset-ext-object>|Add new permissions to an existing permission set.\n## Extension objects in the same app\n> NOTE\n> This feature is available with runtime 13.0 and later and is enabled by default if you're targeting runtime 13.0 and later.\nFrom runtime 13.0 and onwards, large applications have the ability to maintain a separation of concerns. This is achieved by permitting extension objects to coexist with their target within the same app. This facilitates the development of multiple extensions for a single target, all within the same app.\nWhen table extensions live in the same app as their target, their fields and keys are integrated into the base table. This integration eliminates the need for SQL-joins during runtime.\nAll types of extension objects; enums, pages, reports, tables, and XMLports, can coexist with their target within the same app. This allows for various combinations, such as a single table with its table extension, a single page with multiple page extensions, multiple enum extensions, and so forth. This flexibility supports a wide range of application structures and functionalities.\nPermitting extension objects to coexist with their target within the same app is useful for nondisruptive code refactoring within an app. It allows for dividing objects into modules based on specific functionalities, or for preparing to move objects into a separate app in anticipation of future releases.\nWith runtime 13.0, extension objects from a specific app are applied to the target based on the extension object ID. This introduces the following new compiler validations:\n Base objects are prohibited from referencing members from extension objects.\n An extension object can only reference members from other extension objects within the same app if the other extension object has a lower object ID.\n## Related information\ndevenv-extensibility-overview\nTable extension<devenv-table-ext-object>\nPage extension<devenv-page-ext-object>\nReport extension<devenv-report-ext-object>\nEnum extension<devenv-extensible-enums>\nPermission set extension<devenv-permissionset-ext-object>"}