Share via

Table Index Properties

  • Article

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

In the Application Object Tree (AOT), the node for indexes is located at Data Dictionary > Tables > YourTable > Indexes. The following table describes the properties that are available for indexes on tables.

Property

Description

New in this version of
 Microsoft Dynamics AX

AllowDuplicates

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.

AlternateKey

Controls whether this index is part of an alternate key.

The index field must have a unique value in every record.

AX 2012

ConfigurationKey

Sets the configuration key.

An index field that is disabled through a configuration key is automatically removed from the index.

Enabled

Allows you to disable the index.

ID

The internal identifier of the object.

Model

Specifies which model the table index is in.

A model is a logical grouping of elements in a layer. An element can exist in exactly one model in a layer. Examples of elements are a table or class. The same element can exist in a customized version in a model in a higher layer.

AX 2012

Name

Specifies the index name.

UniqueAcrossCompanies

This property is for internal Microsoft use only.

Possible values are Yes or No. The default value is No.

The value of this UniqueAcrossCompanies property is ignored when the AllowDuplicates property is set to No. But when AllowDuplicates is Yes, a setting of UniqueAcrossCompanies to Yes can improve the performance of some cross-company queries. The performance improvement comes from changes to the caching of data.

AX 2012 R2

ValidTimeStateKey

Specifies whether this index key is used to determine the valid time state relationship with the parent table. The default is No.

Tip

Requires setting AllowDuplicates to No and AlternateKey to Yes to enable the property.

AX 2012

ValidTimeStateMode

Specifies whether gaps are allowed between two date effective records. The default is NoGap.

Tip

Requires setting AllowDuplicates to No, AlternateKey to Yes, and ValidTimeStateKey to Yes to enable the property.

AX 2012

Note

Forms sort on the first index.

See also

Best Practices for Index Properties

How to: Create an Index

Best Practices for Indexes

Announcements: To see known issues and recent fixes, use Issue search in Microsoft Dynamics Lifecycle Services (LCS).