Earn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.
Within the dasboard, the user has access to the underlying data and the user will be allowed to generate new reports. That is a nice feature.
But in a number of cases, I must see to it that the dashboard user will not combine and generate new reports because they are not allowed to see other combinations of the data (e.g. to prevent bias in study enrollment). Or because of simple privacy reasons I need to prevent the user to see record level data associated to a table.
Is there a way to achieve this?
You can achieve this by loading your data into a SSAS tabular cube and enforcing row level security.
https://powerbi.microsoft.com/en-us/documentation/powerbi-admin-analysis-services-connector-indepth/
Thanks PowerBIGuy. Your tip does not work with some simple adjustments. I even need to permanently keep a machine running to keep the connection working, if I get it right.
And, if I read it properly, it only helps to limit record level access, not to column acces (https://msdn.microsoft.com/library/jj127437.aspx, see the word the doc). There is no easier way?
The link you provided produced a error. Ideally you would install the connector on your SSAS server. Also you can obtain column level security via row level security. Users would see the column but if used the column would not return any data. Below is more information on row level security.
The error in the link comes from the comma at the end it.
Anyway, I have no intention to use MSQL to achieve this. I currently use Excel to start with and I intend to keep it that way until Microsoft allows others from outside my organisation to cooperate. If that happens I might switch to a higher level for the data backend. For now, I need a different kind of solution.