This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowA new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.
I am trying to present and use a decomposition tree in PowerPoint and it is being extremely slow and lagging. When I try to drill down into it, it is often unresponsive and can take several minutes to register the click. Is there any way to improve the speed of decomposition trees when using them in PowerPoint?
Solved! Go to Solution.
Hi, @pparker9834
Happy answering your questions. Here's why inserting a report in PowerPoint is slow when using the Decomposition Tree:
1. The decomposition tree uses a large dataset or is computationally complex.
2. Network latency can impact report performance by increasing the time it takes for a request to reach the Power BI service, as well as the time it takes to deliver a response. Tenants in Power BI are assigned to specific regions. When a user in a tenant accesses the Power BI service, their requests are always routed to this region. When a request arrives at the Power BI service, the service may send additional requests (for example, to the underlying data source or data gateway) that are also affected by network latency.
3. The maximum number of levels of the decomposition tree is 50. The maximum number of data points that can be visualized at one time on a tree is 5000. When you have a lot of decomposition tree levels, it can lead to long response times.
You can optimize your reports for speed by following these steps:
1. Optimize your dataset. Check if your dataset can be further optimized.
2. Optimize visualizations. You can optimize your dashboard/Power BI reports based on your actual situation.
3. Optimize the environment. This section includes: Optimize the environment, capacity settings, gateway sizing, and network latency.
4. Adjust your decomposition tree, such as reducing the level of the decomposition tree
You can click on the link below to optimize the content mentioned above according to the official documentation and your actual situation:
Optimization guide for Power BI - Power BI | Microsoft Learn
DirectQuery model guidance in Power BI Desktop - Power BI | Microsoft Learn
In addition, you can also improve the speed of accessing the decomposition tree by following the tutorial provided by the link below:
Solved: Why your Power BI reports are slow and how you can... - Microsoft Fabric Community
Solved: Re: Power Bi Report export to PowerPoint way too s... - Microsoft Fabric Community
How to embed Power BI in PowerPoint - dev>scope (devscope.net)
How to Get Your Question Answered Quickly
Best Regards
Jianpeng Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi, @pparker9834
Happy answering your questions. Here's why inserting a report in PowerPoint is slow when using the Decomposition Tree:
1. The decomposition tree uses a large dataset or is computationally complex.
2. Network latency can impact report performance by increasing the time it takes for a request to reach the Power BI service, as well as the time it takes to deliver a response. Tenants in Power BI are assigned to specific regions. When a user in a tenant accesses the Power BI service, their requests are always routed to this region. When a request arrives at the Power BI service, the service may send additional requests (for example, to the underlying data source or data gateway) that are also affected by network latency.
3. The maximum number of levels of the decomposition tree is 50. The maximum number of data points that can be visualized at one time on a tree is 5000. When you have a lot of decomposition tree levels, it can lead to long response times.
You can optimize your reports for speed by following these steps:
1. Optimize your dataset. Check if your dataset can be further optimized.
2. Optimize visualizations. You can optimize your dashboard/Power BI reports based on your actual situation.
3. Optimize the environment. This section includes: Optimize the environment, capacity settings, gateway sizing, and network latency.
4. Adjust your decomposition tree, such as reducing the level of the decomposition tree
You can click on the link below to optimize the content mentioned above according to the official documentation and your actual situation:
Optimization guide for Power BI - Power BI | Microsoft Learn
DirectQuery model guidance in Power BI Desktop - Power BI | Microsoft Learn
In addition, you can also improve the speed of accessing the decomposition tree by following the tutorial provided by the link below:
Solved: Why your Power BI reports are slow and how you can... - Microsoft Fabric Community
Solved: Re: Power Bi Report export to PowerPoint way too s... - Microsoft Fabric Community
How to embed Power BI in PowerPoint - dev>scope (devscope.net)
How to Get Your Question Answered Quickly
Best Regards
Jianpeng Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Check out the May 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 14 | |
| 10 | |
| 9 | |
| 7 | |
| 7 |
| User | Count |
|---|---|
| 33 | |
| 28 | |
| 26 | |
| 20 | |
| 17 |