Best Practices for Field Groups

  • Article

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

Any field that appears in the user interface must belong to a field group. You must always use field groups to design your forms.

Standardized group names are as follows:

  • Identification

  • Administration

  • Address

  • ModuleName (for example 'Ledger')

  • Setup

  • Dimension

  • Misc

The Dimension field must always be the only field in a group named 'Dimension.' Error icon

Properties

Property

Rules

Name

Mandatory

Label

Mandatory Error icon

AutoReport

You must place at least two fields in the AutoReport field group for each table, Error icon except for parameter tables.

The fields placed there should be the ones that the user expects to print when they first click Print on the File menu. The fields used for the TitleField1 and TitleField2 properties are often candidates for this field group.

AutoLookup

If you do not put anything into the AutoLookup field group, the AutoLookup form will contain the fields used in the TitleField1 and TitleField2 properties, plus the field in the first unique index.

See also

How to: Create a Field Group

How to: Create Tables

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