Reporting Project Overview

Bài viết
11/29/2021

Important

This content is archived and is not being updated. For the latest documentation, see Microsoft Dynamics 365 product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.

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

A reporting project is used to create SQL Server Reporting Services reports that can be used in Microsoft Dynamics AX. The following sections provide an overview of a reporting project.

Reporting Project in the AOT

There are two nodes in the AOT or Application Explorer that apply to Reporting Services reports.

SSRS Reports contains the report model elements such as a report that is contained in a reporting project.
Dynamics AX Model Projects under the Visual Studio Projects node contains the code and other project files for a reporting project.

The report project is accessed from the AOT or Application Explorer when you expand the Visual Studio Projects > Dynamics AX Model Projects node, right-click the report project, and then click Edit. This will open the report model for edit in Visual Studio. You cannot edit a report in the developer workspace. For a list of the reporting projects in the Dynamics AX Model Projects node and the reports they contain, see List of Reporting Projects.

There is a distinction between managing reports versus managing report projects. Storing a report in the AOT happens when you add a report to a Microsoft Dynamics AX reporting project. If you want to store your reporting project or business logic assemblies for your reports in the AOT, then you must add the report project into Microsoft Dynamics AX. In the Solution Explorer, right-click the reporting project and click Add [project name] to AOT. When you add a report project to the AOT, the reporting project is added to the Visual Studio Projects > Dynamics AX Model Projects. The following table summarizes the distinction between managing reports and managing report projects.

AOT element	Description
Reports	Stored and available in the AOT when it is added to a Microsoft Dynamics AX Report Model in Visual Studio. Can be included in any number of reporting projects.
Report projects	Stored and available in the AOT when you right-click the reporting project and click Add [project name] to AOT. Used to manage a collection of reports or report business logic assemblies.

The following illustration shows the AOT with the SSRS Reports node and the supported project types. This includes Dynamics AX Model Projects that store reporting model projects.

AOT view of the Dynamics AX Model Project node

Reporting Project in Visual Studio

In Visual Studio, from the View menu, click Application Explorer to display a tree view of the elements that are contained in the Microsoft Dynamics AX system. The SSRS Reports node and Dynamics AX Model Projects node both display in Application Explorer. The report project is accessed from the Application Explorer when you expand the Visual Studio Projects > Dynamics AX Model Projects node, right-click the report project, and then click Edit.

Note

You should open the report for edit at the Visual Studio project level. The project solution will contain any necessary dependencies for the report to build. For example, report drill-throughs require both the source and target report to be loaded in the solution to build successfully.

For information about how to create a report, see How to: Add or Delete a Report. The following illustration shows the layout of a reporting project in Solution Explorer in Visual Studio.

Dynamics AX reporting project layout

Managed Business Logic

The reporting framework supports writing business logic for reports in managed code. Supported managed languages are C# and Visual Basic. For more information, see Using Business Logic in Report Data Methods to Access Report Data. For information about how to define business logic using X++ code, see Using Report Data Provider Classes to Access Report Data.

Customizing Reports

Reporting projects can be customized, upgraded, and patched using the built-in layering support in Microsoft Dynamics AX.

To customize a report, you will edit the report in Visual Studio and when you save the changes, the customizations are added to the layer that you are currently working in. Referenced reporting projects are unpackaged and added to the solution in Visual Studio.

Reporting projects are added to the model store in a packaged format. To add a project to the AOT, in Solution Explorer, right-click a reporting project and then click Add to AOT. The required project items and the referenced reporting projects are stored in the model store in the layer that you are currently working in. Then you can access the reporting project in the AOT. Expand the Visual Studio Projects node, expand the Dynamics AX Model Projects node, and then find the reporting project. One Dynamics AX Model Project is created for each reporting project that is imported into Microsoft Dynamics AX. For more information, see Integrating and Customizing Reports. After a report is added, you can use them in Microsoft Dynamics AX. For more information, see How to: Create a Menu Item for a Report.

Metadata

Reporting projects created in Visual Studio are stored in granular and customizable elements in the AOT called metadata. The metadata is stored in a SQL-based database and is visible in the AOT in the Dynamics AX Model Projects.

Version Control

Version control is available for application projects from either the AOT or Visual Studio. For more information, see Version Control System.

Deploy a Reporting Project

You can deploy reports in Visual Studio, from the AOT, or in Windows PowerShell. The following list describes what occurs when a report is deployed:

Uploads the Report Definition Language (RDL) to Reporting Services.
Copies the business logic assemblies to the Reporting Services server.
Verifies that referenced report and business logic assemblies are present.

To deploy an Microsoft Dynamics AX reporting project in Visual Studio, you must start Visual Studio with administrative privileges or start Microsoft Dynamics AX and the Developer Workspace with administrative privileges. To do this, you must right-click on the icon for Visual Studio or Microsoft Dynamics AX and then choose Run as administrator. To deploy the project in Solution Explorer, right-click the project, and then click Deploy.

To deploy a reporting project from the AOT, expand the SSRS Reports node, expand the Reports node, find the report to deploy, right-click the report and then click Deploy Element.

To deploy reports using Windows PowerShell, see Deploy the default reports.

Report Model Elements

There are several model elements that are used to define a report in a model. The following table describes the main elements in a model:

Element	Icon	Description
Report		The report element represents a report definition. A report definition contains a collection of elements such as datasets, parameters, images, and report designs. The elements that define a report are located under the node for the report in a model. For more information, see How to: Add or Delete a Report.
Report Data Source		A data source is a source of data for a report dataset. You can use the predefined data source, which connects to the Microsoft Dynamics AX application database. Or, you can define your own data sources. For more information, see How to: Define a Report Data Source.
Dataset		A dataset identifies data that is displayed in a report. Every report must have one or more datasets. For more information, see How to: Define a Report Dataset.
Data Method		A data method contains code to retrieve and process data for a report. The code for a data method is written in C# or Visual Basic, depending on which project template is used. For more information, see How to: Define a Data Method in C#.
Data Region		A data region is an area in a report that displays data. Data can be displayed in table, list, matrix, or chart formats. For more information, see How to: Add a Data Region to a Report.
Parameter		A parameter lets you parameterize data for a report. For more information, see How to: Define a Report Parameter.
Filter		A filter is used to filter or restrict the data that is displayed in a report. For more information, see How to: Define a Report Filter.
Grouping		A grouping lets you organize data that displays in a report by grouping fields. For more information, see How to: Define Groupings in a Data Region.
Sorting		A sort lets you control the order in which data displays in a report. For example, you can sort alphabetically by field in ascending or descending order. For more information, see How to: Define a Sorted Data Region.
Image		An image can be a company logo. Or, you can display images together with the data in a report, which is common in product listings. For more information, see Displaying Images in Reports.
Auto Design		An auto design is a report design that is automatically generated based on the report data. An auto design is created by using drag-and-drop actions, and selecting elements by using Model Editor. For more information, see How to: Create an Auto Design for a Report.
Precision Design		A precision design is a report design that is created by using SQL Report Designer. Precision designs are useful when a very precise layout is required. For more information, see How to: Create a Precision Design for a Report.
Layout Template		A layout template specifies the styles that are applied to the header, footer, and body of a report. One layout template can be applied to many reports. For more information, see How to: Create a Layout or Style Template.
Style Template		A style template specifies the styles that are applied to a data region. When you create a style template, you will notice that there are several types of templates that you can create based on the data region type. A style template can be applied to more than one data region in a report, and it can be applied to data regions in more than one report. For more information, see How to: Create a Layout or Style Template.