- Print
- PDF
Move Fix Reports
Several ways exist to move Fix reports. The following pages provide some examples.
Note
This can vary from environment to environment, so Formpipe cannot give a detailed step-by-step guide. Always refer to Microsoft documentation.
Create a Model File
To create a model file, follow these steps:
Log into your AX server and run a Command prompt as Administrator.
In a File Explorer, locate the Fix reports folder. All reports are saved here by default (unless there are reports from another ISV solution):
K:\AosService\PackagesLocalDirectory\LACFixReportsForApplicationSuite
Open the Command prompt and navigate to your AosService\PackagesLocalDirectory\bin folder.
Run the model to create the model. Remember that your output path should exist before doing this.
Example
modelutil -export -metadatastorepath=K:\AosService\PackagesLocalDirectory -modelname=LACFixReportsForApplicationSuite -outputpath=C:\LACExport
Now you can import this model file in any non—production environment.
Import example
modelutil.exe -import -metadatastorepath=K:\AosService\PackagesLocalDirectory -file=C:\LACExport\LACFixReportsForApplicationSuite-Lasernet.axmodel
Create a Deployable Package
To create a deployable package, follow these steps:
Log into your AX server and run Visual Studio as administrator.
In File Explorer, locate the Fix reports folder. All reports are saved here per default (unless there are reports from another ISV solution):
K:\AosService\PackagesLocalDirectory\LACFixReportsForApplicationSuite
In Visual Studio, select Dynamics 365 > Deploy > Create Deployment Package.
Scroll down and select LACFixReportsForApplicationSuite. The name might be different depending on other ISV solutions.
The packages are now ready for import.
Note
You still need permission to access the folder and the reporting server on the receiving environment. After all fixes are moved, you might need to deploy the reports again via Lasernet > Reports > Fixed Report Version > Deploy.
If this error is thrown, then the reports have not been deployed correctly: