This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreJoin the FabCon + SQLCon recap series. Up next: Power BI, Real-Time Intelligence, IQ and AI, and Data Factory take center stage. All sessions are available on-demand after the live show. Register now
I have a master data table and a user group dimension table. And they are joint together in the data model. The use case is, I want to give certain viewer only partial data visiablity to a specific group(usergroup). I was trying to do so by applying RLS (row level security).
For example, I created a role where group(aka. usergroup, a column in user group dimension table) = "Technical Team".
Then I tested this role by 'View As' function. You can see from the screenshot, the drop down content of group(usergroup) slicer is indeed being limited to "Technical Team". However, the data didn't actually change or say being limited until I clicked on "Technical Team". For some reason, this Role is working superficially, not restricting the data in an automated way.
The filtering of the data in a role flows along the relationships in your model. So if the role is not working as you expect it could be because there is an issue with the way your relationships are setup. What is the relationship between the group table and whatever fact table you are looking at?
Check out the April 2026 Power BI update to learn about new features.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
| User | Count |
|---|---|
| 4 | |
| 3 | |
| 2 | |
| 2 | |
| 2 |
| User | Count |
|---|---|
| 5 | |
| 3 | |
| 3 | |
| 3 | |
| 3 |