Best Practices for Use of Reports

  • 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.

RunBaseReport

Reports should use the RunbaseReportStd Class framework to make it possible to run the report in batch and to give it a consistent user interface. An example can be seen in the tutorial_RunbaseReportStd report.

The menu item that is used to start the report is used to control on which tier (client, server, called from) the report should run.

A Menu Item for a report should be an Output Menu Item. Name the Output Menu Item after the report, or name it logically.

Consider where the report should run (Client, Server, Called), and set the property on the menu item (or the class) starting the report.

Apply the same label for the Output Menu Item, the caption of the report, and its dialog.

See also

Best Practices for Report Properties

Reports Best Practices

Best Practices for Report Design

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