Best Practices for Report Design

  • Article

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

Note

SQL Server Reporting Services is now the primary reporting platform for Microsoft Dynamics AX. The X++ reporting framework is being deprecated in Microsoft Dynamics AX 2012. Use the Visual Studio tools for Microsoft Dynamics AX to define reports. For more information, see Development Tasks for Reporting.

An X++ report can have two kinds of design:

  • Auto (AutoDesignSpecs)

  • Generated (Design)

Use Auto design for all 'normal' reports.

Use a Generated design for reports that have special functional requirements that cannot be implemented by using Auto designs or where the design is determined externally. For example:

  • Reports that are forms with externally-determined layouts where the information is expected to be added in very specific positions.

  • Reports that are forms (invoices and so on) where the design should probably be adjusted to the customer's needs at the installation. Most controls should have their positions fixed (not set to Auto) to simplify moving the controls by using the Visual Report Designer.

See also

Best Practices for Report Properties

Reports Best Practices

Best Practices for Use of Reports

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