Naming Conventions: Name Structure

  • Article

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

Where possible, application object names should be constructed hierarchically from three basic components:

  • {business area name} + {business area description} + {action performed (for classes) or type of contents (for tables)}

Examples:

  • CustInvoicePrintout

  • PriceDiscAdmCopy

  • PriceDiscAdmDelete

  • PriceDiscAdmSearch

  • PriceDiscAdmName

  • PriceDiscAdmTrans

Also refer to the general naming conventions.

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