Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
| Enabled for | Public preview | General availability |
|---|---|---|
| Admins, makers, marketers, or analysts, automatically | 
Apr 1, 2024 |
Apr 1, 2024 |
Business value
When you segment objects into base functionality and extended functionality, you can define extensions to objects in the same app as the object. This approach lets you group related functionality into smaller contributions. It also simplifies moving these functionalities to a separate app during refactoring.
Feature details
With this feature, you can define both the base object and extension objects in the same app. For example, you can define a table and a table extension in the same app.
In metadata, extension objects are still separate. Each extension object needs its own object ID in the used range. The key change is that extension objects can now be in the same extension and app as the base object. For tables, table extensions that are in the same app as the base table merge into that table in the database schema. This merge means there's no companion table extension.
This feature applies to all extensible object types. Some examples are page, table, report, enum, and permission set objects.
When you target runtime version 13.0, this capability is on by default.
Geographic areas
Visit the Explore Feature Geography report for Microsoft Azure areas where this feature is planned or available.
Language availability
Visit the Explore Feature Language report for information on this feature's availability.
Additional resources
Extension objects overview (docs)