You’re offline. This is a read only version of the page.
Skip to main content
Dynamics 365 Community
Cancel
Forums
Customer experience
| Sales, Customer Insights, CRM
Service
| Customer Service, Contact Center, Field Service, Guides
Supply chain
| Supply Chain Management, Commerce
Finance
| Project Operations, Human Resources, AX, GP, SL
Small and medium business
| Business Central, NAV, RMS
Microsoft Dynamics 365
| Integration, Dataverse, and general topics
Microsoft Cloud for Sustainability
| MSM, SDSF, ECS, EID, ESG
Archived topics
| Read-only forums of past discussions
Microsoft Dynamics AX (Archived)
Microsoft Dynamics CRM (Archived)
Microsoft Dynamics GP (Archived)
Microsoft Dynamics NAV (Archived)
Microsoft Dynamics RMS (Archived)
Microsoft Dynamics SL (Archived)
Blogs
Community blog
Dynamics 365 blogs
User groups
Galleries
Ideas
Resources
Getting started
Community news
Leaderboard
Learn
Community support
Community events
Community feedback
FastTrack
TechTalks
Blogs
FastTrack forum
Partner case studies
Implementation guide
More
Search
Notifications
Announcements
Announcing Category Subscriptions!
Announcing Category Subscriptions!
Dynamics 365 Community
/
Blogs
/
Jesús Almaraz blog
/
Define extension objects in...
Define extension objects in same app as their base object
Jalmaraz
667
Follow
Like
(
0
)
Share
Report
Define extension objects in same app as their base object
This post is about one of the last new features of BC24:
Source
New and planned features for Dynamics 365 Business Central, 2024 release wave 1 | Microsoft Learn
We can go to the detail of the feautre and can read:
“
With this new feature, it's possible to define both the base object and extension objects in the same app. For instance, a table and a table extension can be defined within the same app.
”
Source:
Define extension objects in same app as their base object | Microsoft Learn
Does the wold need this feature?
So, the first reaction is
“
I am missing something
”
. But if you read the Business Value justificaction we can read
“
By allowing the segmentation of objects into base functionality and extended functionality, it becomes possible to define extensions to objects in the same app as the object itself. This provides an option to group related functionality in smaller contributions and makes it easier to later move these to a separate app as part of refactoring.
”
.
So the conclussions are:
No. You are not missing anything.
The value of this feature is
……
procastination!!
No, the wolrld does not need this feature.
I want a configurable error o avoid create a tableextension in the same app than the extension.
Comments
Add new comment
Comment on this blog post
New#123
You don't have the appropriate permissions.
Welcome,
Profile
Messages
My activity
Sign out