Forum Discussion
Single User Account doesn't see published changes
Hi there,
Wondering if anyone has encountered this issue. We have one user account (Pro license) that always seems to have issues not seeing the latest changes made to reports. Most notably issues with Slicers not functioning correctly.
The changes are funtioning in Desktop and when published, they work with other accounts, but this one user is constantly having issues and its very frustrating for him but also causing issues trusting that the reports are functioning correctly.
We have tried clearing the browser cache, logging out and back in, different browsers, etc. but nothing seems to work. I have asked him to try logging in with his account on another user's computer and am waiting to hear back.
It seems to be account or specific browser or computer related but wondering if anyone that has experience this before has any troubleshooting pointers.
TIA,
Kevin
After renaming the report and re-publishing to a new Workspace, it appears (fingers crossed) to have fixed this issue for the one user. Not sure why or how but it seems to work the same as it does for everyone else now.
In the end turning off the persistent filters before publishing seemed to resolve this issue.
Thanks!
4 Replies
The user has confirmed that the report works fine on another user's computer under that user's account, but when he tried it using his account under both Edge and Chrome browsers that the problem is still happening. So this definitely seems to be related to their account and this is not an RLS or similar security type issue as this user has full admin rights.
Thanks,
KevinHi, KevinColes
It's strange. But there is no abnormality in the information you mentioned.
Can you check if the problem will occur even if you create a new simple report?
Whether the problem is only found under a specific report?
Whether the gateway is running normally in powerbi service and the dataset can be refreshed normally?
If it doesn’t solve your problem, please feel free to ask me.
Best Regards
Janey Guo
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
After renaming the report and re-publishing to a new Workspace, it appears (fingers crossed) to have fixed this issue for the one user. Not sure why or how but it seems to work the same as it does for everyone else now.
In the end turning off the persistent filters before publishing seemed to resolve this issue.
Thanks!
