Forum Discussion
Impactful Individualpower bi report based on multiple semantic models
You can use more than one Power BI semantic model in a single report, but there are two different scenarios:
1. Same report with multiple models,
You can connect to Model A and Model B and use visuals from both in one PBIX. However, the models stay separate: you generally can’t relate tables across them, and slicers/filters from one model usually won’t filter visuals from the other model.
2. Truly combining models,
You may be able to use a composite model (DirectQuery for semantic models) to add a second model and create relationships/combined measures. This depends on tenant settings and can introduce limitations such as performance, restricted modeling features, and more sensitivity to changes in the upstream models.You will need permission to all underlying semantic models. If upstream models change (rename/remove fields), your report can break. Also, cross-model filtering and “single set of slicers” is not automatic unless you implement an integration approach.
If your end goal is a single, consistent reporting experience, the most reliable approach is usually to build a combined semantic model upstream and then build reports from that one model.
Super UserYou can use more than one Power BI semantic model in a single report, but there are two different scenarios:
1. Same report with multiple models,
You can connect to Model A and Model B and use visuals from both in one PBIX. However, the models stay separate: you generally can’t relate tables across them, and slicers/filters from one model usually won’t filter visuals from the other model.
2. Truly combining models,
You may be able to use a composite model (DirectQuery for semantic models) to add a second model and create relationships/combined measures. This depends on tenant settings and can introduce limitations such as performance, restricted modeling features, and more sensitivity to changes in the upstream models.
You will need permission to all underlying semantic models. If upstream models change (rename/remove fields), your report can break. Also, cross-model filtering and “single set of slicers” is not automatic unless you implement an integration approach.
If your end goal is a single, consistent reporting experience, the most reliable approach is usually to build a combined semantic model upstream and then build reports from that one model.
Hi,
I am currently looking into the performance issues of clients power bi setup and realised that they are using direct query connection to 5-6 semantic models for a single report. Now as per my experience and as you mentioned this is a probable issue for degraded report performance. But I can t seem to find any microsoft article mentioning the same. Can you help with that.
Also correct me if I'm wrong, the direct query connection to models need xmla read write permission which further impacts performance, isn't it .
If you can guide me to any documentation or article on the same, that'll be very helpful.
