This articles describes how to install the modern report design templates in the application suite. You can use these samples to create graphically rich business documents that have flexible header and footer branding.
This article introduces a new set of developer tools that take the form of report designs for several core business documents in the application suite. These report designs have been re-imagined so that flexible branding in the header and footer is rendered for publicly facing documents when transactions are generated in Microsoft Dynamics 365 for Finance and Operations. The following illustration shows how a legacy design for a sales invoice differs from a modern sales invoice.
Why aren't these designs the default designs for the application suite reports?
There are two primary reasons why we are maintaining the legacy solutions for Finance and Operations:
- Modern designs don't include code. Although the legacy solutions use embedded Microsoft Visual Basic (VB) code to recognize configuration keys and honor regulatory requirements that vary by region, the modern designs offer much less flexibility. The benefit of a simple design that has minimal code behind it comes at the expense of reusability across regions.
- Modern designs aren't available for all business documents. There is a gap between supported business documents and the availability of a modern design. Although the legacy designs aren't as aesthetically pleasing, they provide a sense of consistency.
Important: These simple modern designs are not recommended for all types of deployments. They are intended for cases where the customer doesn't require run-time control over the layout of the document through existing application configuration settings.
Apply the modern designs
The report designs have been bundled into a model file and posted to Microsoft Dynamics Lifecycle Services (LCS), so that you can easily access them from your existing subscription. Use the following procedure to obtain the report design solutions and install them in your local development environment. After you've installed them, you must apply some customizations to incorporate the new report designs for the appropriate scenarios. Follow these steps to install the modern report designs for the application suite.
- Download the ApplicationSuiteModernDesigns model file from the Shared asset library page on LCS. Sign in to Microsoft Dynamics Lifecycle Services to access the deployment dashboard, and then save the model file to a location that is accessible from the development environment.
Import the model file into your local development environment. To install a model file in a Finance and Operations development environment, use the ModelUtil.exe tool and the -import directive. Here is an example.
ModelUtil.exe -import -metadatastorepath=[path of the metadata store] -file=[full path of the file to import]
- Navigate to the C:\AOSService\PackagesLocalDirectory\bin folder.
Run the following command.
ModelUtil.exe -import -metadatastorepath=C:\AOSService\PackagesLocalDirectory -file="E:\Test\AppSuiteModernDesigns.axmodel"
For more information about how to import model files, see Distribution of models: How to export and import a model. After you've imported the model file, start Microsoft Visual Studio 2015 to verify that the new collection appears under the AOT node in Application Explorer.
Follow these steps to incorporate the modern report design into an existing application suite report:
- Create a project that contains the application suite report.
- Copy the DocuBrandDetailsDS data set, and paste it into the collection of data sets.
- Copy the Modern design, and paste it into the collection of existing report designs.
- Build and deploy the updated application suite report, which now includes the modern report design.
Update the Controller object to add references to the new report design. Search for code that resembles the following code. This code is often nested in the preModify method of the Controller object.
// select the report design this.parmReportName(ssrsReportStr(CustAccountStatementExt, DesignName));
At this point, you should be able to access the modern report designs from the application. Be sure to perform thorough test validations on these design templates before you deploy to production environments.