Forum Discussion
Using Import Models and Dataflows Together
- 1 month ago
Yes, this is a perfectly valid and commonly used architecture. There's no issue with having a mix of regular Import mode semantic models and Dataflow-based semantic models within the same workspace.
Using a Dataflow for larger or more complex ETL workloads can actually be considered a best practice because it separates data preparation from semantic modeling and allows the transformed data to be reused across multiple reports.
A few considerations to keep in mind:
Reuse: If multiple semantic models require the same transformed data, using a Dataflow avoids duplicating Power Query logic across PBIX files.
Refresh order: Ensure the Dataflow refresh completes before any dependent semantic models refresh. You can achieve this by configuring an appropriate refresh schedule.
Performance: Dataflows can reduce the amount of transformation work performed during semantic model refreshes, although the semantic model will still need to import the processed data.
Capacity and licensing: Since you're using Power BI Pro, be aware of refresh limits and shared capacity constraints. Large datasets may still require careful optimization of your model and queries.
Management: Keep naming conventions and documentation consistent so it's clear which semantic models depend on Dataflows.
If the large dataset is only used by a single report, you could continue using Power Query in Desktop. However, if the transformations are complex or the data may be reused in the future, moving the ETL logic into a Dataflow is a good design choice.
For more information, see:
Introduction to Dataflows: https://learn.microsoft.com/power-bi/transform-model/dataflows/dataflows-introduction-self-service
Best practices for Dataflows: https://learn.microsoft.com/power-query/dataflows/best-practices-developing-complex-dataflows
Semantic models in Power BI: https://learn.microsoft.com/power-bi/connect-data/service-datasets-understand
💡 Helpful? Give a Kudos 👍 — keep the community growing.
✅ Solved your issue? Mark this as the Accepted Solution ✔️
Best regards, Prince Singh | Data Science & Microsoft Fabric Enthusiast
Yes, this is a common practice that there is no conflict between Import models and Dataflow sourced models in the same workspace. Few things to keep in mind with your Pro license setup is that Dataflow will be in Import mode once taken by the semantic model as Pro will not support DirectQuery over Dataflows across workspace the way Premium does.
So you can gain reusability and offloading transformation logic to the service instead a different storage mode. Watch your refresh scheduling the Dataflow needs to finish refreshing before dependent semantic model refreshes. Also keep an eye on Dataflow storage limits and refresh duration on Pro as large datasets might push against timeout limits
Thank you krishnakanth240 for the explanation. It really cleared the doubts.