Direct Query warning message when trying to publish

Hi siddrow ,

You can follow the below 3 options.

Option 1: Keep Logic Out of Composite Model (No Calculated Tables/Columns)

Avoid any calculated tables or columns that reference the DirectQuery dataset. Only create measures, and make sure those do not reference imported tables in their logic. Consider moving some transformations to Power Query (for import-mode tables).
Keep DirectQuery and Import parts completely decoupled (no relationship, no measure linking them).

Option 2: Split into Two PBIX Files
This is the most stable and scalable option.

PBIX 1 Live Dataset Model: Only connects to the shared DirectQuery dataset. Build all visuals and measures that rely on it. Publish it as a standalone Power BI report or dataset.

PBIX 2 Import Model: Connects to your other data sources. Create local measures and logic here.

In PBIX 2: Use Power BI datasets to connect to the published dataset from PBIX 1. This avoids calculated tables/columns issues because the entire remote dataset is treated as a semantic model, not raw tables.

Note: You can now reuse that dataset across multiple reports without hitting DirectQuery limitations.

Option 3: Use Dataflows as a Middle Layer
Useful if you want more control over the shared data or want to reuse across models. If the source data is available in a Power BI Dataflow , import that instead. You can schedule refreshes and shape the data in Power Query without relying on DirectQuery constraints. This gives you Import-mode flexibility, but still aligns with governance (if the dataflows are created in your organization’s workspace).

If my response has resolved your query, please mark it as the Accepted Solution to assist others. Additionally, a 'Kudos' would be appreciated if you found my response helpful.

Thank you