When I tested the role, the dimension and the bridge table were filtered just fine, but the fact table wasn’t. I remembered I had to select a checkbox on the relationship: “Apply security filter in both directions”, because the bi-di won’t be honored in RLS scenarios. Kasper de Jonge explains it in his blog post Dynamic security made easy with SSAS 2016 and Power BI (a must-read).
Except that the checkbox wasn’t there.
Ehrm.
So after a bit of digging, I found out that the following preview property must be enabled: Enable cross filtering in both directions for DirectQuery.
Quite confusing, since I’m not using DirectQuery at all. Anyway, once you enabled this feature – you don’t even need to restart Power BI Desktop – the checkbox is alive and kicking.
And all was well. Also, Kasper said he’ll fix it. Sweet. 🙂
A while ago I blogged about a use case where a pipeline fails during debugging…
Quite the title, so let me set the stage first. You have an Azure Data…
At Saturday the 21st of February I'm presenting an introduction to dimensional modelling at dataMinds…
I'm not trying to start up a debate whether you should use tabs or spaces…
The Power BI Enhanced Report Format (PBIR) will soon become the default, and that's a…
Quite a long title for a short blog post :)While deploying a DACPAC (from a…