Recently I was asked by a customer to look into a securityissue around one of their reports in Dynamics AX 2012 R2. Users were reporting that some people withinthe customer organization had access to the accrued purchases report and somedid not.
After reviewing the security we found that the user that hadaccess to the report was looking at a US legal entity localization in a TESTenvironment while the other user who could NOTview the report was looking at their UK localization legal entity in their PRODenvironment. Once we were comparingapples to apples we found that the accrued purchases report was not availablein any of their UK localizations.
After further research this was found to be “by-design” inDynamics AX 2012 R2. As stated in aTechNet article, the link is below, the accrued purchases report is onlyavailable in localizations for the United States and Canada.
This did not change the fact that the customer still neededa report to reconcile their UK received not invoiced account at month andyear-end.
After speaking with some collogues on the possible risk ofdeploying a report not made for a particular localization I decided to attemptthis in a TEST environment.
The only risk that you run when deploying a report this wayis that the report may not work. Areports could require data from fields that may not exist in a differentlocalization causing the report query to fail.
In short, the deployment and testing of the accruedpurchases report in my TEST environment was successful for multiple users inthe UK legal entity! Also, attached tothis blog entry is a generic document for how to deploy the accrued purchasesreport to a UK localization.
It should also be noted that this is not a process that isunique to this report. This processcould be used to deploy any report to any legal entity where it does notoriginally exist, however, this does not mean the report will work in thatlocalization. This should be testedbefore a deployment to PROD is attempted with any report.
As always, please test, test, test. Although this solution worked for me it should still be thoroughly vetted in your TESTenvironments before the deployment is attempted in any production (PROD) environment.
When I was researching this issue I found very littleinformation on this topic so I hope this helps if this is ever an issue for anyof you!