Document Reporting Services overview

Important

Welcome to the documentation for Microsoft Dynamics 365 for Operations on docs.microsoft.com. We are migrating our content here from the Dynamics 365 for Operations Help Wiki.

This article describes the integrated reporting solution that is available in Microsoft Dynamics 365 for Operations. This solution simplifies service administration, increases developer productivity, and provides an enhanced report viewing experience for users.

Document Reporting Services

Document Reporting Services are based on Microsoft SQL Server Reporting Services (SSRS). In the current version of Microsoft Dynamics 365 for Operations, these services are hosted in the Microsoft Azure compute service. If you're developing in a one-box environment, the services also run locally in the Azure compute emulator.

Service deployment – Local vs. cloud

In a one-box environment, developers can create, modify, and preview reports, from end to end, by using Microsoft Visual Studio 2015. A separate process isn't required in order to add reports to the application's metadata store. Changes to reports are packaged together with other solution updates and then deployed to the cloud after development is completed in the local environment.

document-reporting-services-topology

Viewing reports in Dynamics 365 for Operations

The enhanced report viewing experience that Dynamics 365 for Operations provides for end users is the same as the report preview experience in Microsoft Visual Studio. You no longer use a separate design preview in Visual Studio. Instead, just press Ctrl+F5 to build and preview the report in an Internet Explorer window. The report appears exactly as it would appear in the client. Even the user's parameter experience is the same. The following screen shot shows an example of a report preview that is opened from Visual Studio.

Example of a report preview

Service administration prerequisites

The following table compares the service administration prerequisites for Microsoft Dynamics AX 2012 and the current version of Dynamics 365 for Operations.

AX 2012 The current version of Dynamics 365 for Operations
A report development environment has the following prerequisites:
  • SSRS must be installed.
  • SSRS must be configured by using Reporting Services Configuration Manager.
  • SSRS extensions for Dynamics 365 for Operations must be installed.
Reporting services run in the Azure compute emulator, together with the application server. Therefore, there are no SSRS service administration prerequisites. After reports have been deployed to the local reporting services, they can be accessed from the client.

Developing application reports

The process for developing a report in the current version of Dynamics 365 for Operations is easier than it is in AX 2012, because you can create and validate a reporting solution entirely in Visual Studio 2015. The following table describes how Dynamics 365 for Operations simplifies the basic procedure for adding an automatic design report that is based on a query.

AX 2012 The current version of Dynamics 365 for Operations
  1. In the Microsoft Dynamics 365 for Operations client, create a query in the Application Object Tree (AOT).
  2. In Visual Studio, create a reporting project, and add the query to it.
  3. Edit the report in the Visual Studio model editor.
  4. Preview the report design in Visual Studio by using the model editor toolbar.
  5. Use Visual Studio to add the report to the AOT.
  6. Use the AOT in the client to create a menu item for the report, and add the menu item to a menu.
  7. Use the AOT to deploy the report to the report server.
  8. Verify the report in the client.
  1. In Visual Studio, create a reporting project and the query.
  2. Edit the report in Visual Studio.
  3. In Visual Studio, add the report to a menu item, and set the menu item as a startup object.
  4. Use the AOT to deploy the report to the report server.
  5. Press Ctrl+F5 to verify the report in the Dynamics 365 for Operations client. Note: There is no longer a separate preview of the report design from the model editor.
  6. When the whole solution is completed, deploy it to the cloud in one package.