Best Practices for Index Properties

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

The following table describes the standards and best practices in Microsoft Dynamics AX for setting the properties for an index. For a description of each property, see Table Index Properties.




Use the field name for a single field index. You must use "Idx" as a postfix for index names.

If you attempt to create an index with a name that has already been used for an index in Microsoft Business Solutions—Axapta, an error occurs. Error icon


The primary index must have the AllowDuplicates property set to No.

Error icon

There should be one unique index per table for tables that belong to the table groups Group, Main, and WorksheetHeader. If set to Yes, the index can be non-unique.

If you do not create at least one unique index, Microsoft Dynamics AX creates one by combining the first index and the RecId.


This property is usually set to Yes.


You should use a configuration key so that the index is disabled for features that are disabled.


If forms are opened with no specific ranges or specific sort orders, and no index is specified in the index property of the form's data source, forms sort on the first index.

See also

Best Practices for Indexes

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