Forum Discussion
Row Level Security (RLS) on SQL Server data
- Anonymous10 years ago
Hi Adam, and everyone,
I finally got it t work. the reason why RLS was not working as expected, was that the role member (PBITEST002) was configured as an admin of the workspace. RLS started working as expected once I set pbitest002 as member.
Thanks
Kaz
Anonymous, did you check the same Power BI report when you do "Test data as role" and sign in as PBITEST002? The images you posted show that you're checking Power BI report when you do "Test data as role", however, you're checking with Power BI Dashboard when sign in as PBITEST002.
Vicky_Song, yep, I checked the same report at the time of testing the role as well as after logging in as PBITEST002.
- Anonymous10 years agoNot applicable
bump...
- Anonymous10 years agoNot applicable
Um, looks like this feature is not there yet...
- GuyInACube10 years agoAdministrator
I just did a test on my end using the same fields as in your screenshot. I didn't encounter any issues. It worked as expected. I tested with both of the following DAX expressions for the rule.
[UserID]=username()
[UserID]="[email protected]"
These both filtered data as expected.
It may be worth opening a support ticket to see what is happening on your end, as it isn't obvious.
- Anonymous10 years agoNot applicable
Hi Adam,
Where did the filters work for you? Did they work at the time of testing, within the dataset security where you have the feature to 'test as role'? or did it work for you in an actual report? I have added screenshots (below) where I expect to see pbitest002 user to see only Central District, but the user can see all districts.
How can I log a support ticket? I have just tested out RLS after June 2016 update, and it has not changed a bit for me.
1 - Implementing RLS and testing it on Desktop (June 2016)2 - Configuring RLS in cloud (post publish) and adding users to role3 - Viewing as the end user
Thanks
Kaz