Testing RLS on shared dataset

[jtuck]

Need "View as Role" on report with RLS on shared dataset. I have a dataset that is shared with multiple reports that reside within the same workspace, but I cannot test the reports with RLS on the desktop side nor on the web side. On the desktop side, the Manage Roles and the View as Roles are grayed out. On the web side, "Test as role" does not recognize the report associated with the dataset. I receive the error "Role testing in row-level security (RLS) currently requires a report. Please build a report with this dataset to use role testing." But this is the report that is associated with the dataset! RLS works in this scenario but it cannot be tested. What gives?

[fbcideas_migusr]

This is oddly important. Often times we need to validate RLS on the LiveConnect reports. OR for training purposes we need to demonstrate the LiveConnect report via a specific role that the audience will have. Would love to be able to choose Test as Role on the original dataset and then have the ability to select any connected report to test the role with.

[jmontoya2]

Miles has right. But this isn't "oddly" important, but "really" important issue. It's necessary to be available to use RLS in reports that use Live Connection to Power BI Datasets which have RLS configured. Please, do something about it!

[elena_schott]

Totally agree. I use 3-4 shared datasets for my dozen reports. THe datasets are the model and measures only, and the reports have all the content to view. Yet there is no way to view row level security in the report, and none in the online environment unless I want to start constructing pages I will delete later. This is definitely missing coverage.

[fbcideas_migusr]

How is it that 'best practice' would suggest you have a "golden" semantic model (that sounded better when it was a dataset), and yet no way to test the security you've set up against the thin reports in separate workspaces?

This is a massive failure. It works if you have the reports in the same workspace but that's not enough when the model is separate and serving reports across multiple workspaces.

"Here you go customer, can you do me a favour and test if the security I built for you is working because I can't" 👍