Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now

Reply
riddhi_onyxdata
New Member

RLS is not working for a specific visual having column from KQL database.

I am using tables from KQL database and lakehouse.I am creating a measure in which i am just taking the MAX() of the column from the table from KQL database.
In the table visual, 3 column are coming from the tables which is coming from lakehouse and rest 2 are the measures from KQL database.
I am using DAX query for RLS. For eg, If the domain of the emailid accessing the report is "abc.com" then all the data should be visible else data should be visible as per the id. 
It is throwing error with one specific visual. Also, when RLS is applied only then it is causing an issue, Otherwise report and visual is loading correctly.


Issue.png

1 ACCEPTED SOLUTION
Anonymous
Not applicable

Hi @riddhi_onyxdata ,

This error indicates that your query appears to be overly complex and has reached its memory limit, resulting in a related error. I'm not sure what you did, but here's what I did:
From Power BI Desktop, I selected KQL Database and Lakehouse as the data source and created a connection, the connection mode is Import for both, then I did create an RLS role with DAX and tested this RLS role on both Desktop and Service, but neither of them had problems.
If the operation you performed is not the same as my test, please describe your steps in detail so that I can perform further relevant tests. If you are doing something similar to what I am doing, perhaps you can change the connection mode to Direct Query mode when connecting to KQL Database and Lakehouse, so that your query will be passed to the data source, and perhaps your query performance will be better this way.

Best Regards,
Dino Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

2 REPLIES 2
Anonymous
Not applicable

Hi @riddhi_onyxdata ,

This error indicates that your query appears to be overly complex and has reached its memory limit, resulting in a related error. I'm not sure what you did, but here's what I did:
From Power BI Desktop, I selected KQL Database and Lakehouse as the data source and created a connection, the connection mode is Import for both, then I did create an RLS role with DAX and tested this RLS role on both Desktop and Service, but neither of them had problems.
If the operation you performed is not the same as my test, please describe your steps in detail so that I can perform further relevant tests. If you are doing something similar to what I am doing, perhaps you can change the connection mode to Direct Query mode when connecting to KQL Database and Lakehouse, so that your query will be passed to the data source, and perhaps your query performance will be better this way.

Best Regards,
Dino Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

lbendlin
Super User
Super User

Refactor your DAX query in DAX Studio.  Examine the query plan and eliminate the steps that create excessive number of records.

Helpful resources

Announcements
November Fabric Update Carousel

Fabric Monthly Update - November 2025

Check out the November 2025 Fabric update to learn about new features.

Fabric Data Days Carousel

Fabric Data Days

Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!

Real Time Intelligence in a Day

Real-Time Intelligence in a Day—Free Training

Turn streaming data into instant insights with Microsoft Fabric. Learn to connect live sources, visualize in seconds, and use Copilot + AI for smarter decisions.

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Kudoed Authors