Forum Discussion
Direct query vs Import Mode when complex DAX is used
- 9 months ago
julsr One option would be to simply take your dataflow Power Query code and use that in your import queries. Then you are just refreshing a single time. The other option would be to land your dataflows in a Fabric warehouse/lakehouse and use Direct Lake. DirectQuery is going to be limited and slow. Direct Lake should be comparable to import but somewhat slower.
Hey julsr ,
To streamline refreshes while preserving DAX in Import mode, use Composite Models with your Dataflow as a source in Import mode. Then, enable “Scheduled Refresh” for the dataset that uses the Dataflow. Power BI automatically queues the Dataflow refresh before the dataset refresh, ensuring the semantic model always reflects the latest data without manual intervention.
Key points:
Keep the dataset in Import mode to retain full DAX functionality.
Schedule dataset refresh, not the Dataflow separately.
Power BI handles dependencies, refreshing the Dataflow first, then the semantic model.
This approach provides a single, synchronized refresh while keeping your DAX measures intact.
If it solved your issue, feel free to mark it as the solution so others can benefit too.
Thanks for being part of the community.
- lbendlin9 months agoSuper User
Power BI automatically queues the Dataflow refresh before the dataset refreshThat is incorrect. You need to orchestrate that yourself, via Power Automate or Fabric Data Pipelines.
- MohdZaid_9 months agoSuper User
Actually, while the initial response mentions Power BI automatically queuing the Dataflow refresh before the dataset refresh, it's important to clarify that, in some scenarios, Power Query-based solutions can offer more control over refresh orchestration especially when using Power Query instead of Dataflows.
Since Dataflows are indeed based on Power Query, you can leverage the same techniques and scheduling capabilities within Power BI to synchronize the refreshes effectively. In cases where you need more advanced orchestration (such as dependencies or triggering events), Power Automate or Fabric Data Pipelines would indeed be the next step for more complex workflows.