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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :

Normalization dilemma

Klaas Deforche Profile Picture Klaas Deforche 2,433

Hi all!

I have a dilemma, and would like your opinions.
The situation is that I want to add fields to an existing table (say InventTable)

What would you prefer:
Add fields or table

So the question is, should I add new fields to the table (option one), or should I create a new table with the fields and link to it. (option 2)

Normally, option 1 is the standard way of adding extra fields to a table, but option 2 has a few advantages:

  • You don’t need to modify the existing table
  • You’ll have less trouble with these fields when you have to upgrade AX
  • It will be easier to deploy your modifications in an AX environment that already contains modifications to the table

There are also a few disadvantages I can think of:

  • You have to join 2 tables to get the data from the new fields
  • You can’t add the new fields to fields groups on the main table (InventTable in this example)
  • On forms, you will have to add a new data source, or add display fields

I would certainly go for option 1 when doing customizations for a customer, but would consider option 2 for product development. I’m in doubt. How about you?

Comments

*This post is locked for comments