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
What I would recommend when working with your semantic models is always to make your semantic model size as small as possible. So remove any extra columns which are never gonna be used for any measures or any reporting to reduce the size of your semantic model which will help you keep under the pro size limit of 1GB.
- Learner_PowerBI1 month agoFrequent Visitor
Thanks GilbertQ . Sure will keep it mind the best practice in order to limit semantic model size.