I created a Power BI paginated report and embedded it in Acumatica. I’m able to view the report without any issues, but another user is unable to access the report screen within Acumatica.
The same user can successfully open and view the report directly in Power BI Service, so it doesn’t appear to be a permissions or licensing issue on the Power BI side. I also contacted Microsoft Power BI support, and they confirmed there is no issue with Power BI.
This issue occurs only when accessing the report through Acumatica.
Has anyone encountered a similar issue or can provide guidance on what might be causing this? Any leads would be greatly appreciated.
I’m curious for some of the scenarios they mentioned there, namely:
Does a different browser behave different?
If you log in on their computer, do you have the problem?
If they log in on your computer, do they have the problem?
Most of the advice when I search appears to be about checking the performance/scalability of the underlying data model. So there’s a chance that changing the caching settings, or reducing dataset size, might help?
Also apparently just creating a new copy of the report and republishing might have an affect, though I’m really just reviewing what other people have tried via Google search at this point.
@KCHEKURI What are the technical details for the error if you click on it?
Does the report work fine if you log in on their PC or they log in on your PC? (Is it machine/user specific?) What monitor setups are you each running?
Is it all other users, or just 1 other user that is having the issue?
@KCHEKURI can you please check the configuration :
1. Role/screen permissions — verifying the user has the correct access level assigned to the embedded report screen under System > Security > Roles.
2. Third-party cookie settings in the browser — since the report is embedded via an iframe, a browser blocking third-party cookies could prevent it from loading even if direct Power BI access works fine.
3. Try a different browser to rule out any browser-specific blocking.
Only two of us are using this report right now. When I open the report on my PC, everything works fine without any issues. However, when the other user opens the same report on their PC, it throws an error, so it appears to be user-specific.
We have verified role/screen permissions, Power BI access (workspace, dataset Build, and report), third-party cookies, and tested across different browsers. The user can also access the dashboard screen in Acumatica.
However, the issue still persists for this specific user. The report works fine on my PC but fails on theirs, so it appears to be user-specific.
I’m curious for some of the scenarios they mentioned there, namely:
Does a different browser behave different?
If you log in on their computer, do you have the problem?
If they log in on your computer, do they have the problem?
Most of the advice when I search appears to be about checking the performance/scalability of the underlying data model. So there’s a chance that changing the caching settings, or reducing dataset size, might help?
Also apparently just creating a new copy of the report and republishing might have an affect, though I’m really just reviewing what other people have tried via Google search at this point.
