Data Model for New Microsoft Dynamics AX Modules

Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

When creating a new module, create a data model that has the following criteria:

• Has a structure similar to the one in the standard application

• Can be normalized to the third normal form

  For a description of the third normal form, see the Microsoft Knowledge Base article about Data Normalization Basics.

The following figure shows a simplification of the basic structure of the data model found in most Microsoft Dynamics AX modules. This structure can be used as a template for setting up the properties of your tables.

Data model found in most modules

The following table shows typical values for the various types of tables used in the previous figure. (All values shown in these tables are only guidelines and might not be exactly as found in the actual tables.)

Property	CustGroup	CustTable	CustTrans
Name postfix	Group.	Table.	Trans.
TableGroup	Group.	Main.	Transaction.
Description	Stores information that categorizes the records.	Stores some base data in the application.	Stores some transactions in the application.
Number of records	Typically relatively low with relatively static information.	Typically high with relatively static information.	Typically very high.
Key	There is always a key.	There is always a key.	There is always a key.
Delete actions	The information is sometimes so non-vital that records can be deleted from the table, even if there are other records in the system that relate to the table.	Restricted against CustTrans and SalesTable.	Not applicable.
CacheLookup	Entire table.	Found, NotInTTS.	None.
ClusterIndex	On the key.	On the key.	Consider.

The following table shows additional typical values for the various types of tables used in the previous figure.

Property	CustParameters	SalesTable	SalesLine
Name postfix	Parameter.	Table.	Trans or Line.
TableGroup	Parameter.	WorkSheetHeader.	WorkSheetLine.
Description	Stores some basic parameters in the application. There is one field per parameter.	Stores some header information for the related worksheet transactions.	Stores worksheet lines in the application.
Number of records	Typically only one, or very few, with very static information.	Typically high with relatively static information.	Typically very high.
Key	There is a key to make the found cache work.	There is always a key.	There is sometimes a key.
Delete actions	Not applicable.	Cascading SalesLine.	Not applicable.
CacheLookup	Found.	NotInTTS.	None.
ClusterIndex	Not applicable.	On the key.	Consider.

See also

Designing a Microsoft Dynamics AX Application

Announcements: New book: "Inside Microsoft Dynamics AX 2012 R3" now available. Get your copy at the MS Press Store.