March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early bird discount ends December 31.
Register NowBe one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now
Hi there..........I am working with a training firm that has 11 clients. Currently I have one data model with all 11 clients that refreshes nightly. The reason they want them all in a single data model is that they have reports based on all clients in aggregate. The data model will, at times, fail to refresh due to its complexity. Is there a way to have 11 different data models, all configured the same, and bring them together into a "single model" that one could use for reporting? Kind of like "appending" the output of each data model in a stacked format? Thanks in advance.
@DPCCGF - did we resolve your issue? If we did, please select the appropriate solution, it helps with visibility for others and for SuperUsers to keep their status! Thanks!
1. Use Separate Datasets for Each Client (Data Models)
Instead of putting all 11 clients into one large data model, you can create separate Power BI datasets for each client, which are configured the same way, as you mentioned. Each dataset can have its own refresh schedule, which helps reduce the complexity of each individual model.
Once these datasets are created, you can bring them together in a single report by using the following methods:
2. Using Power BI Service: Datasets and Shared Datasets
The idea is to use the Power BI Service to create separate datasets for each client, and then use a shared dataset model in Power BI Desktop to combine them. Here's how:
Step 1: Create Separate Datasets for Each Client
Create and configure individual data models in Power BI Desktop for each client.
Publish each dataset to the Power BI Service.
Step 2: Use Power BI Service to Combine the Data
In the Power BI Service, you can create a new report that references multiple datasets (one for each client).
In Power BI Desktop, you can connect to these Power BI datasets as sources (using Power BI Service data sources), then combine them in a unified report.
Step 3: Combine Data Using DirectQuery or Import Mode
In Power BI Desktop, when you connect to these datasets, you can use DirectQuery (which allows for real-time querying) or Import Mode (which will pull data into the model).
You can append data from each individual dataset (client data) into a unified report model by using the Append Queries feature in the Query Editor.
3. Appending Data from Multiple Models into One Using Dataflows (for Large-Scale Integration)
If you want a more scalable approach, especially for complex datasets, Power BI Dataflows might be the solution. With Dataflows, you can consolidate data from multiple sources into one central data model. You can:
Create individual Dataflows for each client's data.
In each Dataflow, apply the same transformations and data modeling processes.
Use Power BI Service Dataflows to create a central dataflow that combines all 11 client data sources. This allows you to merge, clean, and prepare your data at a more granular level.
The final unified dataflow can then be used to create a single dataset that can be used for reporting.
4. Combining Models in Power BI Desktop Using "Get Data"
You can combine the data from different models (datasets) by:
Getting Data from multiple sources (individual Power BI datasets).
Then, in Power Query, use the Append Queries function to stack the data from the different datasets.
This effectively merges the client-specific data into a single table that you can use in your unified report model.
@DPCCGF - Whilst I would personally recommend sorting out the "complexity" in my experience this is usually rooted in bad practice, you could (in theory) set up 11 different models and then import them into one model using Composite models - you will not be able to append using this method however, but you could write DAX over the 11 different Fact tables and use some shared dimensions in the composite model - at a guess I would say performance of this would be terrible though.
https://learn.microsoft.com/en-us/power-bi/transform-model/desktop-composite-models
If you need to append things together into one table, I would set up 11 Dataflows and then use a master data flow that appends these into one.
https://learn.microsoft.com/en-us/power-bi/transform-model/dataflows/dataflows-create
If this guidanance helps, please accept as the solution for others with the same issue.
I can rephrase complexity. I have to connect to the souce via API to about 8 different data topics. So if it is one client I have 8 different APIs connections all for that single client and its token. Well, my current model replicates that 11 times as I cannot get to each client in whole. So all the data is brought in, then appended into one table. Then the appended 8 tables are joined to allow for reporting. I am open for suggestions.
@DPCCGF - I would suggest the dataflow option is your only viable solution. With one separate dataflow per client and a master dataflow that appends them all. This should ensure if one dataflow fails, your end dataflow will still succeed, it will just have out of date data for the one client until that connection is fixed.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.
Arun Ulag shares exciting details about the Microsoft Fabric Conference 2025, which will be held in Las Vegas, NV.
User | Count |
---|---|
133 | |
90 | |
88 | |
64 | |
58 |
User | Count |
---|---|
203 | |
141 | |
107 | |
73 | |
70 |