To understand this question please follow this thread
https://community.dynamics.com/ax/f/33/t/108159
This explained solution in above thread works for me also.
"If the permission node under the design of the SSRS report seems OK, as Brandon explained, you can try to export and re-import the SSRS report by XPO. For us, it solved the problem (on AX2012 R2 CU7) without having to add any permission on roles or privileges.
Under the hood, we found out that re-importing the report (re)generate data in the ModelSecurityPermission table of the model database, especially the permissions links between the report and the tables that it uses, and the data provider class.
"
NOW MY PROBLEM AND MAIN QUESTION IS:
I am also facing same problem after CU13 upgrade. i applied the same fix on test, re-imported the xpo and it did the trick and worked.
Now problem i can not do these same steps in Production. I can not delete or manually import XPO on prod. We have Build process in place and we always use Modelstore deployment.
Let me know if someone has some directions with build process.
Should i do above steps on Build server, like delete/re-import the object on build server and then regenerate the build ?
Thanks for any help