It would be helpful if Row Level Security could be defined on entities within a Data Flow, so that a single data flow could be used as a repository for different users (with different access rights) to get data.
3 Comments
- elena_schottNew MemberAbsolutely. I'd be fine with having to have a new dataflow for each change in the relevent role field, or per table. That would let me be certain the data was secured even if a report writer got lazy on the dataset.
- James_LeesNew MemberAdded my vote. We use dynamic RLS to restrict viewers of reporting data from a financials system to see only the same transactions they would be allowed to see on the source system itself. However, we want power users to be able to create their own datasets based upon these restricted data sources and, for example, their own Excel-on-SharePoint sources. This is not possible at present because (a) a dataset cannot bring in data from another dataset and (b) if we use a data flow instead, this blows open the security model.
- fbcideas_migusrNew MemberStatus added:Needs Votes
Recent ideas
Support external tables for parquet/csv in Fabric DW
Fabric Data Warehouse allows reading Parquet and CSV files using the OPENROWSET function. However, it does not support external tables that reference Parquet or CSV files (CREATE EXTERNAL TABLE (Tran...jovanpop-msft1 hour agoMicrosoft EmployeePlanned2.9KViews38likes3CommentsFabric warehouse SQL editor: improve Ctrl-Enter
Today the Fabric warehouse SQL editor executes the full text in the editor when you press Ctrl-Enter without anything selected. It would be very convenient if Ctrl-enter only executed the single sql...stegus641 hour agoNew MemberNew15Views0likes1CommentNew tab should not retain opened Workspaces and artifacts
Since the recent UI changes, Microsoft Fabric keeps opening workspaces/items in additional tabs and retains many workspace tabs simultaneously. This makes navigation difficult and increases browser c...swatigupta22 hours agoNew MemberNew4Views0likes0Comments