Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
I have a report in PowerBI Service for my organization. This report has row level security enabled. Some users when they go inot the report even though they have permission to all the data the matrix visuals are not showing the full data. For example it is only showing one customer when it should show all. When I test as a role for the people who experince issues it shows up perfect. Another thing is some useres cant expand the matrix down to the lowest level but some are able to. This does not make sense please help.
Solved! Go to Solution.
Hi @wc123
Since the issue began after adding more levels to the matrix, and RLS was previously working fine, this could be related to a known rendering bug in Power BI Service that causes inconsistent behavior in matrix visuals for different users especially when deep hierarchies are involved.
There’s actually a great thread discussing this exact kind of issue here:
🔗 Different users see different results in same Power BI report
Several users reported that complex matrix visuals caused discrepancies due to a bug in the Power BI Service, and it affected how visuals were rendered or expanded for certain users. The thread also includes workarounds and updates from Microsoft.
I’d recommend giving it a read and seeing if any of the solutions apply to your scenario. In the meantime, if possible, you might try simplifying the matrix as a temporary workaround or using separate visuals to break out levels.
I told my org to use the green refresh button in the top right of the reports page and that seems to have worked for everyone.
Hi @wc123
Thank you for reaching out microsoft fabric community forum.
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
Hi @wc123
It sounds like you're encountering issues related to row-level security (RLS) and possibly permission or browser cache inconsistencies in the Power BI Service. Even though you've confirmed that users have access to all data and the "Test as role" feature displays the report correctly, the actual experience can vary if RLS roles are not being applied consistently, or if there's a mismatch between what roles users are assigned to in the Power BI workspace and what’s defined in the model.
Also, the inability for some users to expand the matrix to the lowest level could be due to their browser or Power BI settings (such as display modes or accessibility features). To troubleshoot, ensure users are correctly assigned to the RLS roles via the Power BI dataset security settings and verify their access in Azure Active Directory if you're using dynamic RLS. Additionally, ask affected users to clear their browser cache or try a different browser to rule out client-side issues. If problems persist, checking the dataset's security settings and reviewing user permissions both in Power BI and underlying data sources would be the next best steps.
Thank you for youre repsonse,
I dont think this has anything to do with RLS becasue everything was working great for the past month. I added a few more levels to the matrix visuals in my report (there are 6 total) and thats when people in my org started having issues with the report.
Hi @wc123
Since the issue began after adding more levels to the matrix, and RLS was previously working fine, this could be related to a known rendering bug in Power BI Service that causes inconsistent behavior in matrix visuals for different users especially when deep hierarchies are involved.
There’s actually a great thread discussing this exact kind of issue here:
🔗 Different users see different results in same Power BI report
Several users reported that complex matrix visuals caused discrepancies due to a bug in the Power BI Service, and it affected how visuals were rendered or expanded for certain users. The thread also includes workarounds and updates from Microsoft.
I’d recommend giving it a read and seeing if any of the solutions apply to your scenario. In the meantime, if possible, you might try simplifying the matrix as a temporary workaround or using separate visuals to break out levels.
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
Check out the November 2025 Power BI update to learn about new features.