Best Practice: Table extensions with more than 10 new fields

(0) Share

Report

Posted on by Jakob M

Hi all,

we have a table extension to add some new fields to a AX standard table. If the number of new fields is greater than 10, there is a BP-warning like "Number of new fields in base table table.Extension is greater than 10"

What's the best way to avoid this BP-warning? Should i create a new table to extend the standard table analogue to the 2012 Extension Framework? Or is it sufficient to create a second table extension?

Thanks for your help.

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (1)

Yuji 4,131 on at

Like (0)

Report

RE: Best Practice: Table extensions with more than 10 new fields

I got one question when use separate table and use FK to link to main table:

How easy to modify Data entities and ensure Create/Read/Update/Delete actions on this table.

For example, we need to ensure when creating a record in the main table, this table needs also got created. I think in this way, table extension is always convenient.

Was this reply helpful? Yes No
Suggested answer

Sukrut Parab 71,699 Moderator on at

Like (0)

Report

RE: Best Practice: Table extensions with more than 10 new fields

You should create a new table and all your fields in new table and joined it with you table with foreign key

Was this reply helpful? Yes No
Martin Dráb 236,039 Most Valuable Professional on at

Like (0)

Report

RE: Best Practice: Table extensions with more than 10 new fields

It's not necessary; the framework is there to make it easier for you.

Was this reply helpful? Yes No
Jakob M 55 on at

Like (0)

Report

RE: Best Practice: Table extensions with more than 10 new fields

Thank you both for your suggestions.

I think, that a related table with foreign key relationship is the way to go.

Is it in D365 still necessary to integrate it with the Table Extension Framework (create PackedExtensions field, parent table to SysExtensionSerializerMap map and child table to SysExtensionSerializerExtensionMap ..)?

Was this reply helpful? Yes No
Martin Dráb 236,039 Most Valuable Professional on at

Like (0)

Report

RE: Best Practice: Table extensions with more than 10 new fields

Nobody says that ten is a magic number, it's just an indication. If you were implementing the best practice check, you would have to pick a concrete number as well.

Was this reply helpful? Yes No
Henrik Larsen 646 on at

Like (0)

Report

RE: Best Practice: Table extensions with more than 10 new fields

I have not come across any documentation, why Microsoft thinks 10 new fields is a good number, but one has to assume it has to do with normalisation and you should extend through a related table and a foreign key relationship.

Was this reply helpful? Yes No
Verified answer

Martin Dráb 236,039 Most Valuable Professional on at

Like (0)

Report

RE: Best Practice: Table extensions with more than 10 new fields

The purpose of this warning is to avoid adding too many fields to standard tables. Excessive number of fields slows down fetching the data and often suggest that the schema isn't normalized (which has additional consequences). But it depends, of course.

Obviously splitting the extension to two wouldn't solve the problem, because all the fields would be added to the standard table in the end. The best practice checks wants you to consider dividing fields to several separate tables.

Was this reply helpful? Yes No