Best Practices for Report Properties
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.
This topic describes the best practices for:
X++ Report Properties
X++ Report Design Properties
X++ Report Section Properties
X++ Report Control Properties
Report Properties
Property |
Rules |
---|---|
Name |
The name must comply with general Naming Conventions. Prefix: Module short name Infix: Logical description of contents |
Report Design Properties
Property |
Rules |
---|---|
Name |
Call the report 'Design', or use a logical name if you have more than one design. |
Caption |
Use a label to indicate the contents or purpose of the report. If the report is country/region-specific, you do not have to use a label. |
Description |
You must use a label for the Description property, unless it is a country/region-specific report. |
ReportTemplate |
Use one. In generated design reports, Report Templates are only used at generation time. Template-generated sections must be manually maintained afterwards. Use the following predefined templates:
Internal use External use
List InternalList ExternalList
Form InternalForm ExternalForm
|
Orientation |
Typically set to Auto to exploit all the IntelliMorph features. Set it to Portrait or Landscape for a report with specific format requirements. |
Report Section Properties
Property |
Rules |
---|---|
ColumnHeadingStrategy |
Use the default, WordWrap, if possible. |
Report Control Properties
Do not change the properties of report controls for controls that are based on fields, extended data types, and display methods, with respect to
Width
Label
Width of label
Formatting information, such as the kind of decimal point, and so on
If you change these report controls, you will not be able to use IntelliMorph.
The Left and Top properties should be set to Auto on most reports, but they should have a specific value on reports that are likely to be adjusted to the needs of individual customers.
See also
Best Practices for Use of Reports
Best Practices for Report Design
Announcements: New book: "Inside Microsoft Dynamics AX 2012 R3" now available. Get your copy at the MS Press Store.