Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
Hi All
Not sure how to ask this, so i'll describe my desired outcome.
I have a dataset that has 2 Roles setup (Can See, and Can't See).
Can See is able to view a specific column in a table
Can't See, can't see it
I want the default behaviour of everybody to be in the Can't See role, so adding in a group that has everybody in it.
Then if they are added to the Can See role, that takes precedence over the Can't See role.
Is this default behaviour or would the most restrictive role apply
@mattcornish That is the default behavior. Are you using OLS (Object Level Security) or are you doing something like this? Column Level Security - Microsoft Power BI Community
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.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 48 | |
| 45 | |
| 41 | |
| 20 | |
| 17 |
| User | Count |
|---|---|
| 69 | |
| 64 | |
| 32 | |
| 31 | |
| 27 |