would like to check with you regarding the standard practice for report deployment, I know the deployable packages didn’t take care of the report deployment, so it has to done through power shell script, can you provide more details on that.
Example of the deployment:
Deploying all reports Using PowerShell
All reports can be deployed using following commands . To run command open PowerShell as administrator and run following commands. Depending in path in your virtual machine you can switch between C: and J: drive.
J:\AosService\PackagesLocalDirectory\Plugins\AxReportVmRoleStartupTask\DeployAllReportsToSSRS.ps1 -PackageInstallLocation "J:\AosService\PackagesLocalDirectory"
Deploying a specific Reports through PowerShell
Now I want to deploy reports starting with AssetDep and TaxVatRegister , so I ran following command and in the output you can see only those reports get deployed. This trick is helpful in managed environment like UAT not prod when you have some issues with reports in those enviornments.
J:\AosService\PackagesLocalDirectory\Plugins\AxReportVmRoleStartupTask\DeployAllReportsToSSRS.ps1 -Module ApplicationSuite -ReportName AssetDep*,TaxVatRegister.Report
There is an issue going on regarding building a model, we are currently doing the manual build, there is dedicated VM for building the model and package creation, that VM is connected with the Main branch, The Admin team gets the latest from the branch, build the models and create the deployable package, currently building the model is not correctly generating the labels in the label DLL file in the resources for our custom model. The DLL has been validated through reflection process, so the label wasn't there.
In other case, if the label file is pulled into the project, project building has been correctly generating the labels, it has been validated in other environments.
There is another issue with the report that is open using the same label, the report is failing.
Error message:
No Error message, the label name is displayed in the UI instead of the label itself.
We have followed everything correctly (Label file is correct, Model is built successfully, Report has been deployed), but it is still now working. It is working on the scenarios that I have discussed in the below thread, and we haven’t fixed it in the Admin environment, Please let me know if you want to investigate in that environment.
We have deployed the latest packages in one of our environment (DBA-DEMO) and also deploy the report using the power shell but we are unable to run the report there and didn’t see the updated label, on the other hand I have setup a system for investigating that issue, I have created the project and pulled the report menu item and label file and build It, it is working fine.
Dev machine with Main branch (Same code base) | TEST Environment (Package created with Main branch) (Same code base) |
1. Created the project with few objects related to report 2. Build and run 3. Successfully working with correct output ![]() ![]()
| 1. Deploy the latest packages with the report code 2. Install all the report using power shell 3. Menu item is not displayed correctly, and report is failing 4. Need help to identify, next step
![]()
|
