New Database Layout in NAV2018 when using Extensions

With Extensions v2 in Microsoft Dynamics NAV2018, fields are distributed across multiple SQL tables. In the example here, I have added a tableextension object that adds the “KOB Nummer” field to the customer table.

As you can see, there is a new table in the SQL, “Customer@2039b279……..” (same guid as my extension)

So in order to get to your complete/combined customer table from SQL, you must JOIN the two tables.

Here is a trick, if you RUN the table from C/Side, you’ll see the fields added by extensions, even though you cannot see the extension fields in C/Side.

Share thisShare on FacebookTweet about this on TwitterShare on RedditShare on Google+Share on LinkedIn

One thought on “New Database Layout in NAV2018 when using Extensions”

  1. Isn’t this going to be a performance killer? Imagine having 10 extensins adding fields to Cust. Ledger Entries and GL Entries and Item Ledger Entries. We will have to use background posting to get anything done 🙁

    This new design even prevents Table Extensions to create keys across custom fields and standard fields. (At least I can’t see how to do it in the December preview – haven’t tried NAV2018)

    I thought Microsoft would make Views with the joined tables, and then make indexes to atleast improve reading speed.

Leave a Reply