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

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.

Reply
DShallcross
Frequent Visitor

When using DAX in a semantic model will Fabric fall back to Direct Query

We have a semantic model created and inside we have a main date table. We wanted to create other tables based on this date table, whilst still using DirectLake for performance. Initially we tried creating views but realised that views fall back to DirectQuery mode when trying to use them in a filter. So I wondered if alternatively we could use DAX instead? Reading through the documentation here Direct Lake overview - Microsoft Fabric | Microsoft Learn it mentions "Import and Direct Lake storage modes use the VertiPaq engine to process DAX queries and return results to the Power BI report and user" so I presume that mean it won't fall back to DirectQuery mode but I wanted to check before I start the laborious process of changing them all to DAX

1 ACCEPTED SOLUTION

Hi @DShallcross

Yes, this is why they should be materialized and stored as tables for DirectLake on warehouses. On Lakehouses, materialized lake views work in directlake mode for semantic models. 

 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.

View solution in original post

6 REPLIES 6
tayloramy
Community Champion
Community Champion

Hi @DShallcross 

When using DirectLake models, the views should be calculated and materialized as tables on the lakehouse/warehouse before getting to the semantic model. 

 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.

We created the views in the warehouse first and then added those views into the semantic model. During the creation of a PowerBI report when trying to add a filter using those views it mentions that it will fall back to DirectQuery mode.

Hi @DShallcross

Yes, this is why they should be materialized and stored as tables for DirectLake on warehouses. On Lakehouses, materialized lake views work in directlake mode for semantic models. 

 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.

Thank you, I believe this is what I will need to do and materialize my views as tables.

Cookistador
Super User
Super User

Hi @DShallcross 

 

In your case, you can only create a calculated table using direct lake if calculations is not referering to columns of tables in Direct Lake mode.

(source: https://learn.microsoft.com/en-us/fabric/fundamentals/direct-lake-overview#fabric-item-permissions)

 

So in your case, you will have to create view directly in your lakehouse/warehouse

But of course, you can create measure

Unfortunately if we create views it falls back to DirectQuery mode so that is off the table for us. If DAX is also not possible in DirectLake then we will have to create extra tables

Helpful resources

Announcements
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!

October Power BI Update Carousel

Power BI Monthly Update - October 2025

Check out the October 2025 Power BI update to learn about new features.

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.