Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
Is there a way to send the RLS FIlter to the server to limit the data that is sent back?
I am currently using DirectQuery with Databricks. However, the RLS seems to be filtering in Power BI and not on the server. Which is extremely inefficient.
Is there a way to add the RLS filter to what is sent to the server so only the data that should be sent to the client is sent?
Solved! Go to Solution.
Dynamic M query parameters in Power BI Desktop - Power BI | Microsoft Learn
See if you can use that to send the USERPRINCIPALNAME back to Databricks.
It spends all its time on the folded query. In DAX Studio make sure to clear the cache before each run.
Dynamic M query parameters in Power BI Desktop - Power BI | Microsoft Learn
See if you can use that to send the USERPRINCIPALNAME back to Databricks.
Thanks I'm looking into that now.
I have another question (let me know if I need to post this as a separate discussion).
Do you have any idea why the execution time of the query power bi is sending back to databricks takes 1.5 seconds on databricks to execute but 17 seconds in power bi to finish the entire visual?
Use the Performance Analyzer in Power BI to investigate the timing for each visual. May just be a case of too many visuals on the page.
I reduced it to 1 visual with my filters...
In Power BI Desktop it takes 62 seconds to render...
In Dax Studio 2 seconds
I copy the dax from the above and run it in Dax Studio connected to the same data model
It spends all its time on the folded query. In DAX Studio make sure to clear the cache before each run.
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
Check out the November 2025 Power BI update to learn about new features.