Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now
I have read all the Microsoft documentation on this topic, but cannot seem to find an answer to my question.
Situation: I am trying to limit the data visible in a published Power BI app based on a user's division, however the visible data is displaying correctly in the app when I had them test it.
Example: Let's take the following sample table:
Division | Sales |
A | $10 |
B | $20 |
I have applied row-level security to the semantic model such that my test user is in division A and the testing in PBI desktop does in fact show $10 in sales as expected.
When I test in the PBI Service however, I get the below results. I would have expected at least one of these scenarios to result in the correct sales value ($10), but that does not seem to be the case.
Workspace Access | Report Sales Value | App Access | App Sales Value |
Viewer | $10 | granted as workspace user | $30 |
None | N/A | added individually | $30 |
I know that the app is just a display for the reports in a workspace and the audiences just limit which reports can be seen. I also know row-level security is applied at the semantic model level. My question is how to make the the correct sales values show the app? (What roles or access needs to be given in the workspace and/or app to ensure this displays correctly?)
Solved! Go to Solution.
In retracing steps, I found my issue and will detail here in case anyone else has the same problem. There were two reports in my workspace: the original and the one with row-level security applied. I had the original visible in the app and the new RLS hidden, so naturally the RLS would not apply in the app.
Steps to check:
Hi @ldsmith919
Can you confirm that you have put the user also into the role in the power bi service?
Yes, we have a security group which includes all members of the user's team (including the user) that was added as a member to the role.
In retracing steps, I found my issue and will detail here in case anyone else has the same problem. There were two reports in my workspace: the original and the one with row-level security applied. I had the original visible in the app and the new RLS hidden, so naturally the RLS would not apply in the app.
Steps to check:
Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
User | Count |
---|---|
39 | |
26 | |
21 | |
19 | |
10 |
User | Count |
---|---|
41 | |
36 | |
35 | |
20 | |
14 |