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?
5 Comments
- fbcideas_migusrNew MemberThis 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.
- jmontoya2New MemberMiles 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_schottNew MemberTotally 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_migusrNew Member
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" 👍
- fbcideas_migusrNew MemberStatus added:Needs Votes
Recent ideas
Allow External OneLake Data Shares to Be Accepted into Multiple Fabric Item Types
Fabric External Data Sharing provides an excellent zero-copy mechanism for sharing OneLake data across tenants. However, the receiving tenant currently has to accept the share into a Lakehouse. I w...Mourak18 hours agoNew MemberNew5Views0likes0CommentsAllow OneLake Shortcut Authentication Mode to Be Changed In Place
OneLake shortcuts support passthrough and delegated authentication, but changing the authentication model currently requires deleting and recreating the shortcut. I would like shortcut authenticatio...Mourak18 hours agoNew MemberNew7Views0likes0CommentsTenant-Wide OneLake Shortcut Lineage and Impact Analysis
This is grounded in a documented limitation: shortcut lineage is currently workspace-scoped, and Microsoft specifically says lineage for shortcuts to warehouses and semantic models isn't currently av...Mourak18 hours agoNew MemberNew15Views0likes1CommentAdd an End-to-End Production Reference Architecture for Microsoft Fabric Real-Time Intelligence
I would like to see a complete end-to-end Microsoft Fabric Real-Time Intelligence reference architecture that demonstrates how the individual RTI capabilities work together in a production-oriented s...Mourak18 hours agoNew MemberNew5Views0likes0CommentsImprove CI/CD consistency for Microsoft Fabric Real-Time Intelligence Eventstreams
Microsoft Fabric Real-Time Intelligence has made strong progress with Git integration and deployment pipelines, but lifecycle management can still be inconsistent across Eventstream sources, destinat...Mourak19 hours agoNew MemberNew3Views0likes0Comments