Forum Discussion
DirectLake over OneLake with combination with DirectQuery tables
Hi jaryszek,
As per my understanding, Compatibility level is a property of the semantic model itself, not of individual tables. Your model already runs at compatibility level 1702.
Best regards,
Ganesh Singamshetty.
Hello jaryszek,
I mean that the semantic model is initially built and authored using Microsoft supported modeling experiences, where composite models are explicitly supported and documented.
According to the documentation:
- Composite models (mixing storage modes) are supported when the model is created using Power BI Desktop or supported Fabric web modeling experiences:
Use composite models in Power BI Desktop - Power BI | Microsoft Learn - DirectLake semantic models are designed to work directly over OneLake and are authored and managed using Fabric tooling:
Direct Lake overview - Microsoft Fabric | Microsoft Learn
https://learn.microsoft.com/en-us/fabric/fundamentals/direct-lake-web-modeling
Ok so we misunderstood.
My question is: if warehouse table using Fabric environment can be used together with OneLake semantic model?
Assume you have 3 tables on DirectLake over OneLake. This is DirectLake mode.
But now I want to add warehouse table, so I am goinf to fabric, clicking import table, choosing Fabric Warehouse...It will work?
Or we will have semantic model version issues or something like that?
Best,
Jacek
Hello jaryszek,
Yes, you can add a Fabric Warehouse table to your existing DirectLake semantic model (with the 3 OneLake tables) directly in the Fabric web experience. Here's how it works:- Go to your semantic model in Fabric > Model view > Get data from the ribbon > Select Fabric > Warehouse > Choose your table. This automatically creating a composite model (mixing DirectLake + DirectQuery modes).
Thank you,
what about compatibility level? I am currently using 1702 for directLake...It will work or there is no connection between them?
Best,
JacekHi jaryszek,
As per my understanding, Compatibility level is a property of the semantic model itself, not of individual tables. Your model already runs at compatibility level 1702.
Best regards,
Ganesh Singamshetty.