This was exactly what I was looking for! Thanks a looooooot
@p3dr0txАй бұрын
Any solution to avoid fallback do DirectQuery using RLS ?
@AmitChandakАй бұрын
Using this method it should not fallback, unless you are using view or it is reaching data limit of your capacity
@p3dr0txАй бұрын
@@AmitChandak I just tested it and it really does not fallback! Works like a charm! Thanks!
@AmanSingh-gw6we9 ай бұрын
Hi Amit thank you for the video I have one question can we do same thing in lakehouse also as I am not getting setting of gateways and cloud connections in lakehouse semantic model
@AmitChandak9 ай бұрын
Hi Aman, Make sure you are using custom semantic model, not the default one.
@AmanSingh-gw6we9 ай бұрын
@@AmitChandak so to create a customer semantic model I need workspace access right I can’t do with lakehouse access it’s giving me error that can’t delete or modify
@prajwalsalutagi4859Ай бұрын
i need to Create 1 time RLS in the data lake and it can be applied also in power bi reports instead of doing RLS for every single PBIX file . can we?
@AmitChandakАй бұрын
Direct Lake RLS can be implemented at the semantic model level, allowing it to be used across multiple reports. If you prefer to apply RLS at the Lakehouse or Warehouse level, you need to create SQL roles. However, this approach will enforce the use of Direct Query mode.
@prajwalsalutagi4859Ай бұрын
@ Thank you for the clarification! I have another doubt: I have two semantic models where RLS roles and users are already defined. If I create a report that connects to both semantic models, can I still achieve centralized RLS in this scenario? Will the roles from both models apply seamlessly, or is there a different approach required? Looking forward to your guidance!