Best Practices for Extended Data Type Properties [AX 2012]

Updated: December 6, 2011

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

In Microsoft Dynamics AX, the Best Practices for extended data type properties are listed in the following table. For more information about properties, see Extended Data Type Properties.




The names of extended data types should reflect the real-world items they model.

If the extended data type belongs to an application module (such as customers or vendors), the name must be prefixed with the name of the module (Cust, Vend, and so on).

If an extended data type extends another extended data type, its name can be the name of the parent followed by its own specialization. If it is used in another module, however, it can be prefixed.

If it is a data type for identification purposes, such as for a key field in a table, the name must be postfixed with "Id." For example, JournalId, InventJournalId, CustGroupId, and VendId.

Other common postfix terms can also be used, but avoid "Code," "Num," and "Type."

If you attempt to create an extended data type with a name that has already been used, an error occurs. Error icon


Do not set the Label property to the same value as the HelpText property. Error icon

The label should be defined at the most generic place, and not be duplicated down the hierarchy. Error icon Use the LabelId extended data type.Error icon


Do not set the HelpText property to the same as the Label property. Error icon Make it more descriptive and helpful.

The HelpText property should be defined at the most generic place, and not be duplicated down the hierarchy. For instance, if an extended data type inherits from an enumeration, the HelpText property should be reused, not duplicated. Error icon Use the LabelId extended data type. Error icon


Set FormHelp only when the standard lookup system facilities are not useful.


Set to Descending if the values in this field are more commonly sorted in descending order, for example, the date on which an e-mail was received.


Set to Discouraged if the values in the fields with this type are likely to be unique, for example, phone numbers.


Set to Auto.


If a part of a hierarchy, it must inherit an "is-a" type.


Set to Auto.


If an extended data type is of type enum, it is mandatory to set the EnumType property. Error icon


Set to Auto. Warning icon

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

Community Additions