Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowJuly 7 - July 17 | Round 2 of the Power BI Dataviz World Championships. Don't miss your chance! Learn more
Hi,
I am looking for feedback on other experiences.
Today we build data models and reports in the same .pbix and deploy them. We are starting to use shared data source for multiple .pbix reports. I am comfortable with this.
In doing this, i was curious if it is a best practice to always have a backend data source and front end report file. Meaning, create 1 .pbix that is just the full prepped data model with all power quuery and dax completed, publish that, and then connect a 2nd file as the front end report file (even if you only plan to use the data source once).
Has anyone done this? What is your experience (e.g. are the refresh times impacted good/bad when developing, does it impact the user's speed experience, etc).
@Anonymous
It looks a good approach to me. But I also suggest that you also post this question in the "Power BI Service" forum
Check this article by @MattAllington
https://exceleratorbi.com.au/new-power-bi-reports-golden-dataset/
and this one
Meanwhile you can also explore "DATAFLOWS"
Here are recent articles by @reza_rad
http://radacad.com/what-are-the-use-cases-of-dataflow-for-you-in-power-bi
and
http://radacad.com/getting-started-with-dataflow-in-power-bi-part-2-of-dataflow-series
and a video by @ruthpozuelo
https://www.youtube.com/watch?v=bkFG8s_9sGE
Join us in Barcelona for FabCon and SQLCon, the Fabric, Power BI, SQL, and AI community event. Save €200 with code FABCMTY200.
Join Data Days 2026: 60 days of free live/on-demand sessions, challenges, study groups, and certification opportunities.
| User | Count |
|---|---|
| 31 | |
| 30 | |
| 27 | |
| 24 | |
| 16 |
| User | Count |
|---|---|
| 57 | |
| 40 | |
| 28 | |
| 24 | |
| 20 |