Visual interactions should not pass visual filters. Only the item on the axis selected in the parent visual should be sent to the child visuals. If there are any underlying visual filters in the parent they should not be passed. I'm requesting restoration of t he original behavior. About a month ago it was changed so that the parent visual filter was passed as well. This is a huge reduction in functionality and has broken several production reports. I thought it was a bug but am now informed it is "by design". Bad choice.
3 Comments
MB2Advocate I
Visual level filters should not impact other visuals...that's why they are visual level filters and not page level filters. I have a waterfall chart that shows the components that makes up the current year-to-date net growth (a visual level filter is applied to only show the current year) and a line chart that shows cumulative growth by week with year-over-year comparison. When I select a component on the waterfall chart it cross filters my line chart and removes the historical years (which is what I am interested in seeing). If it where a true visual level filter, it shouldn't filter any of my other visuals.- i have the same problem, impossible to show timelines and current production on the samen page this way... or you gave to remove all interactions... also see: https://ideas.powerbi.com/forums/265200-power-bi-ideas/suggestions/18775207-advanced-interactions
- Status added:Needs Votes
Recent ideas
executeDaxQueries-like API call with effectiveUserName on SSO-enabled model with Service Principal
Please provide a way for a service principal to execute DAX - with an effective user name - against an SSO-enabled directlake semantic model and get per-user results that respect lakehouse OneLake Se...
