We have a user getting the error message “Access denied to method processReport in class PurchReceiptsListDP” when he is trying to print a receipts list for a PO. This method seems to be called by SSRS at runtime and the data in the report comes from two sources.
1. PurchReceiptsListDetailsTmp table
2. PurchReceiptsListHeaderTmp table
So far, I cannot seem to figure out what might be causing this message. Has anyone else seen this before or know of any possible solutions?
Thanks in advance for any assistance.
*This post is locked for comments
when you use client manually and its xpo import dialog to import, it gets always compilated if I am not wrong, thats why it takes also much longer to import then via pipeline. You can check AX client startup in debugger to see under which conditions it gets compiled. In customer pipeline I use autoRunXML as parameter for this ssrs xpo import and it takes aprox. 12mins to import xpo with 40 reports
Thanks RV for swift response. I have used below script .
ax32.exe -aotImportFile="C:\ModelMerge\IMX_SSRS.xpo" .Let me try once again.
One more thing, ModelSecurityPermission table was not populated if we use script but if we use client to import the xpo file then the record was populated in the table. Once again thank you RV for your Inputs.
I solved this in customer's AZDO build pipeline in following way. After importing whole repository content as single XPO and xppbuild I have added following few more steps before FullCIL: combine affected ssrs reports into single XPO, import this XPO and be sure that you do not skip compilation on this XPO import (check parameters passed to ax32.exe execution, leave out -NoCompileOnImport parm). I discovered that the compilation makes difference, no records are are created in ModelSecurityPermission when compilation is skipped. good luck!
We have also facing same issue with ALM build machine after deploy the code from TFS to build machine ,we were not able to generate report got access denied issue. We have seen some of the records missing in ModelSecurityPermission table .the resolutions we follow re import report xpo or switching back report elements from one model to another model.
But the same process we want to automate with CD\CI pipeline which will not create any records in ModelSecurityPermission and it will not work always.so every code movement we need to re import report xpo in PROD every time.
I would be so grateful if you provide any update on this issue.
thanks
Hi,
I don't remember very well unfortunately, but you can try looking at the ModelSecurityPermission table in the model database.
I remember that importing the report XPO added some missing rows on that table, regarding the design node of the report in the AOT
any chance you have more info about what you found under the hood please? it seems like we have this issue with multiple reports and I would like to avoid reimporting all of them. Thank you
thank you..
The solution provided by Nicolas Granjon worked for me too . Thanks
The solution provided by Nicolas Granjon worked for us as well. Thank you!
André Arnaud de Cal...
291,965
Super User 2025 Season 1
Martin Dráb
230,817
Most Valuable Professional
nmaenpaa
101,156