DAX limitations with row level security RLS

Learn restrictions and workaround in using the USERELATIONSHIP function with row-level security in a semantic model for Power BI and Analysis Services.
Article and download: sql.bi/831053?aff=yt
How to learn DAX: www.sqlbi.com/guides/dax/?aff=yt
The definitive guide to DAX: www.sqlbi.com/books/the-defin...

[@mwaltercpa]

Thanks for sharing the RLS DAX. Very helpful.

[@user-wx3dn3il2f]

Thank you! greate contents. one quick question was in my mind, why 2018 value have variation when Marco RLS applied?(4,984,304,80 vs 5,314,492,31)

[@pratikfutane8131]

Awesome video !!👏

[@amardeepbhingardeve9903]

Thank you so much for everything you are doing to inspiring us, one request : your voice is very low in this video, if could fix that it will be great

[@mateusnunes5747]

Is the solution the same when I use Cross Filter?

[@Charlie888]

This solution is awesome！

[@mienzillaz]

Hi Alberto!
Recently I was working on dynamic RLS done on 2 dimensions.. sounds as regular stuff however there was a twist.
I had to beat additive nature of RLS in PBI as some users could be members of multiple roles, and also I had to give access based on any level of hierarchy. I was able to pull this successfully using generate with dynamic tables built on filtered dimensions on path column. Then I used combined values from both dims, same I needed to have in facts. And that last point drives me crazy since I feel it can be done better.
I did watched Marco's tuple video, but I'm struggling to create tuples dynamically. Any suggestions here?

[@carlynwidowski2560]

*promosm* ✔️