Row-level Security - How to use "View as" testing function when report is separated from data

[mmcanelly]

I am working with row-level security for the first time, and I'm trying to test it to ensure the report is looking the way I'm expecting it to. The problem I am running into is that I have my dataset separated from my report (each in their own .pbix file, with the dataset published to the service and the report connecting to that dataset). I am able to use the "View as" button in the dataset file and I can verify the data in the tables, but when I go into the report, that functionality is grayed out. Ideally, I'd like to be able to view the report as a specific user just so I can see exactly what they will see. Is there a way to do this when the dataset/report are separated in this way?

[aj1973 · Accepted solution]

Hi @mmcanelly 

The RLS is applied on the dataset and not on the report, therefore it is not possible to test it that way unless you connect with the use principal credentials to test and see the outcome. Though if the test is good on the dataset level then there is no need to worry about the report.

[mmcanelly]

Thanks Amine. That's too bad that this functionality doesn't exist. It's nice to be able to see exactly what the user will see for testing purposes, even though I've already verified the correct data is being filtered in the underlying dataset. What I ended up doing was just copy and pasting the visuals from the report into the file that the dataset is in to do the testing there. Maybe there will be an easier way to achieve this implemented at some point in the future!

Thanks,

Matt

[aj1973]

May be and maybe not, just that you know from one dataset you can create multiple different reports and dashboards and you might not want to applie the RLS on every report by adding the security group to a specific report. 

Anyway all are opinions and the way you look at it.

Thanks