Deploying the report
SSRS being a server-side solution, after the development of the report it has to be deployed to the server. A report is not exposed to the users until it is deployed. This recipe will show how a report developed in Visual Studio can be deployed to the reporting server. There are multiple options to do it and the choice is left to the developer. PowerShell scripts are better when the reports are to be deployed by an AX administrator.
Getting ready
To be able to attempt the recipe. You need deploying rights to the SQL reporting services and permissions to view the report manager.
How to do it...
AX supports the following deployment options:
To verify if the report is deployed, open the Report Manager in the browser and open the Dynamics AX folder. The report PKTReleasedProduct should be found in the list of reports.
The report can also be previewed from the reporting services. Open the reporting services and click on the name of the report to open the report preview.
How it works...
A report deployment is actually moving all the stuff related to the report to a central location, which is the server, from where they could be made available to the end user. The following list indicates the typical actions performed during deployment:
- The RDL file is copied to the server.
- The business logic is placed in the server location in the format of a DLL.
- Deployment ensures that the RDL and business logic are cross-referenced to each other.
Tip
The MorphX IDE from AX 2009 is still available. Any custom reports that are designed can be imported. This support is only for the purpose of backward compatibility.
See also
- The Deploying language-specific reports to speed up execution time recipe, in Chapter 8, Troubleshooting and Other Advanced Recipes.