Forum Discussion

jaryszek's avatar
jaryszek
Super User
6 months ago
Solved

DirectLake over OneLake with combination with DirectQuery tables

Hello Guys,

 

Can I create a composite model on the current existing DirectLake over the OneLake remote semantic model?

I want to connect to Fabric Warehouse and make the new table a DirectQuery? 

It will be working?

Best,
Jacek


  • 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.

9 Replies

  • v-ssriganesh's avatar
    v-ssriganesh
    Community Support

    Hi jaryszek,
    Thank you for posting your query in the Microsoft Fabric Community Forum.

    Adding a DirectQuery table via Tabular Editor may appear to work at the metadata level, Microsoft only supports composite models (Direct Lake + DirectQuery) when the semantic model is created and owned as a composite using supported tools, not by extending an already published remote Direct Lake on OneLake semantic model.

    The best approach is to Create and own the semantic model in Fabric, including Direct Lake (OneLake) tables and Warehouse tables, letting Fabric manage the storage modes (Or) create a new local semantic model as a composite model that includes Direct Lake and DirectQuery tables.

    Thanks, Jaywant-Thorat for sharing valuable insights.

    Best regards,
    Ganesh Singamshetty.

  • Hi jaryszek 

    Short Answer = No, not in the way you’re describing.

    Let me elaborate What works vs what doesn’t:
    You cannot:

    • Take an existing DirectLake semantic model (remote)
    • And extend it with DirectQuery tables
    • To create a composite model

    A remote DirectLake model is read-only for modeling.

    You can do this instead:

    Option 1 : Fabric way

    • Build all tables inside Fabric
      • DirectLake tables (from OneLake)
      • Warehouse tables (SQL)
    • Let Fabric automatically handle:
      • DirectLake
      • DirectQuery
    • One semantic model → works fine

    Option 2 : Classic Composite

    • Create a new local semantic model
    • Add:
      • DirectLake tables
      • DirectQuery tables (Warehouse / SQL)
    • This works only if the model is local, not remote

    Key rule to remember:

    • You cannot extend a remote DirectLake semantic model.
    • Composite models work only when you own the model.

    Recommendation: If you’re already in Fabric

    • Create everything in Fabric (Warehouse/Lakehouse)
    • Let Fabric manage DirectLake + DirectQuery natively

    =================================================================
    Did I answer your question? Mark my post as a solution! This will help others on the forum!

    Appreciate your Kudos!!

    Jaywant Thorat | MCT | Data Analytics Coach | Super User
    LinkedIn: https://www.linkedin.com/in/jaywantthorat/
    Join #MissionPowerBIBharat: https://tinyurl.com/JoinMissionPowerBIBharat
    #MissionPowerBIBharat
    LIVE with Jaywant Thorat

    • jaryszek's avatar
      jaryszek
      Super User

      Hello,

      thanks. 

      Hmm I am not sure what does it mean "No".

      I have connected to Fabric Warehouse table using tabular editor: 


      I have this as DirectQuery: 


      Seems that it is working. 

      What I am afraid of if really this table will be compatibile with other tables connected from DirectLake over OneLake? 


      Best,
      Jacek