2

Hi,


As we are not allowed to have two table extensions to the same table in one app. This limitation causes table-extension objects to be in a general source folder instead of in a typical module folder where it should/might/could belong. Therefor this suggestion to provide an extra object type that is a subpart of a real/current tableextension and at compile time all partial-table-extension objects build to one table-extension as we already have today. In this way, the code can reside in the module folder together with the corresponding code.


This idea is to provide a new object type (let's call it) PartialTableExtension, so we're able to have multiple (partial) objects that are combined at compile time into one table extension, which should allow for backwards compatibility.


The same idea for page extensions and maybe also interesting for other object types.


Regards,

Filip


Category: Development
STATUS DETAILS
Needs Votes
Ideas Administrator

Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team