Decomposition Tree: Dynamic 'Explain By' Sync Across Multiple Trees
The Decomposition Tree is an invaluable tool for root cause analysis and understanding drivers of key financial metrics. While its cross-filtering capabilities are strong, there's a significant gap in creating truly linked, progressive analytical flows across multiple Decomposition Trees or even other hierarchical visuals.
Currently, if I select a node in Decomposition Tree A (e.g., 'Region'), Decomposition Tree B on the same page is filtered by that region. However, its 'Explain By' fields remain static.
We propose a feature that would allow a selection in a Decomposition Tree (or potentially any visual) to dynamically influence the 'Explain By' fields available or actively selected in another visual (specifically, another Decomposition Tree).
Business Problem: In financial analysis, we often need to explore a core metric by different dimensions depending on the initial breakdown. For example, after identifying a problematic region in a first Decomposition Tree, we might want to automatically present a second Decomposition Tree that immediately breaks down profitability by Product Line and Cost Center specifically for that selected region, without the user having to manually re-select 'Explain By' fields or navigate different views. This would significantly improve the user's analytical journey and reduce friction, enabling faster insights and more guided exploration.
Proposed Technical Solution: Consider an enhancement to visual interactions or the 'Explain By' field well itself, potentially allowing:
- Conditional 'Explain By' Fields: The ability to define a DAX expression or a set of rules that dynamically changes the list of dimensions available in the 'Explain By' well of a target Decomposition Tree based on the filter context established by another visual (e.g., a selection in a source Decomposition Tree).
- Programmatic Expansion: The ability to define which 'Explain By' dimensions a target Decomposition Tree should automatically expand into, based on a selection in a source visual. This could leverage a similar mechanism to drill-through but specifically for setting the initial expansion path.
This feature would unlock more sophisticated and intuitive guided analytics experiences, making Power BI even more powerful for complex financial investigations.
Recent ideas
Add a Close or “Return to previous page” button to Semantic Model Security and Settings pages
When updating RLS group assignments through Semantic model > Security, there is no consistent in-product Close or Done button that returns the user to the previous workspace view. The browser Back b...Kalaiselvan55 minutes agoFrequent VisitorNew2Views0likes0CommentsRetain Comments and Formatting in Power Query within Dataflow
I imagine this is part of the pipeline for development of Dataflows by the time it comes out of Preview. Currently all comments and formatting that is written into the Power Query of a Dataflow is st...tmckenzie31 hour agoNew MemberUnder Review316Views22likes4CommentsEnable field parameters for live connection
One of the limitations of the use of Power BI field parameters is that they can't be used in a live connection model. I request this feature to be enabled since field parameters are hyper useful fo...MSteidl2 hours agoNew MemberNeed Clarification2.9KViews54likes12CommentsEnable SharePoint File Support in Fabric Copy Jobs
Idea description Microsoft Fabric Copy Jobs currently do not support reading from or writing files directly to SharePoint sites. This limitation makes it difficult to implement straightforward and r...arno_cd924 hours agoNew MemberNew2Views0likes0CommentsAdd a "Collapse All Code Cells" option in Fabric Notebooks
Title: Add a "Collapse All Code Cells" option in Fabric Notebooks Fabric Notebooks currently allow users to collapse code cells individually. However, in large notebooks, manually collapsing each ce...arno_cd924 hours agoNew MemberNew4Views0likes0Comments