Index development extension practices recap in Microsoft Dynamics 365 Finance and Operations apps

Index development extension practices recap in Microsoft Dynamics 365 Finance and Operations apps

A general rule of thumb is to use a tempDB table if you anticipate your data set or report will exceed 5000 rows or records. 

Index based on:

• foreign key in AOT node under MyTable > Relations represents a foreign key.

• natural key whose value has meaning to people. Most replacement keys are natural keys.

• surrogate key whose value has no meaning to people. A large number generated by the system, such as RecId, could be a surrogate key.

• unique key, broad term that applies to primary keys and to alternate keys. It does not apply to foreign keys. This term emphasizes that all values for a given key must be unique within one table. All fields in a unique key must be not-nullable.

A primary index provides a unique key to each record in a table.  This is the index that's used for record caching in Dynamics AX. 

• Used to record caching