You’re offline. This is a read only version of the page.
60
Hello, I am creating my first ever extension in BC (or anywhere for that matter).... this will be a PTE and it has gone well so far.
I've created Tables and Pages for Items which we use in our business.
I believe that conventional BC development approach would be to extend the item table to modify or add fields into what we need.
However, the items which we use in our business are so unique, that I am skeptical that the Items table would accommodate enough fields.
If it does, I am very doubtful that it would resemble anything functional for the user.
My question is this...
Rather then extend the Items Table to get the fields that we need, can I instead make it so that my new Table(s) have the proper attributes behave like Items?
(eg functions so that these items have features like base system items, such as inventory control, replenishment, ability to add them to BOMs, etc)
Thanks in advance for your help!
-Anthony
Absolutely you can do what you describe and I agree with Duilio that in some cases subsidiary tables are much better than adding tons of fields into the standard Item table with tableextensions.
Carefully evaluate your business case, if you plan to have more than 2 extensions that extends the same table, go with companion tables.
I would create subsidary tables instead of table extension. To improve performances.
Below an example Using tables instead of table extensions – Kauffmann @ Dynamics 365 Business Central
#1
Sohail Ahmed
932
#2
YUN ZHU
841
Super User 2025 Season 1
#3
Mansi Soni
602
Share
Report
All responses (
Answers (
