web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Best Practice: Table e...
Microsoft Dynamics AX (Archived)

Best Practice: Table extensions with more than 10 new fields

(0) ShareShare
ReportReport
Posted on by Jakob M 55

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

  • Verified answer
    Martin Dráb Profile Picture
    Martin Dráb 241,467 Most Valuable Professional on at

    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.

  • Henrik Larsen Profile Picture
    Henrik Larsen 646 on at

    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.

  • Martin Dráb Profile Picture
    Martin Dráb 241,467 Most Valuable Professional on at

    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.

  • Jakob M Profile Picture
    Jakob M 55 on at

    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 ..)?

  • Martin Dráb Profile Picture
    Martin Dráb 241,467 Most Valuable Professional on at

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

  • Suggested answer
    Sukrut Parab Profile Picture
    Sukrut Parab 71,741 Moderator on at

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

  • Yuji Profile Picture
    Yuji 4,131 on at

    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. 

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the August Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans