Power BI Ideas Admin on 06 Dec 2019 22:42:46
Since buttons have many conditional formating options now and they are affected by measures and other visuals, it is needed to assign individual visual level filters for buttons to make dynamic label and formatting changes for buttons.
- Comments (3)
- Merged Idea (1)
RE: Visual level filter support for Buttons
Hi, great post. I am totally onboard with this suggestion and am experiencing the same scenario. There is a 3rd party visual by CloudScope (Image Pro) that has the feature you require. It has functionality to act like a button and has 'Filters on this visual' enabled. Unfortunately it is a little clunky in that it throws a confirmation click to warn you that you are redirecting to another URL if you are using the "Action" config.I hope this gets voted up as I would prefer to use the native button.
RE: Visual level filter support for Buttons
With the limited functionality of Card visuals, buttons often need to be substituted with their ability to be fully customized. Either buttons need to have control over their visual-level filters or Cards need to be revamped and have customization on par with buttons.
Use case example I ran into:
For a KPI dashboard I use buttons to call out specific metrics. On hover, the button shows the WoW % change of the metric, and the text color corresponds to an increase or decrease in the value. For each of these metrics it requires:
1) A [Base Metric] measure
2) A [WoW % Change] measure
3) Another measure that only returns FORMAT([Base Measure]) so that it can be used in the button's conditional formatting
4) Another format measure for [WoW % Change]
5) A measure to return the corresponding hexidecimal color code
If I were to have 5 different metrics it would require 25 measures to be able to obtain this sort of functionality (in my case I have 20 metrics I'd like to display = 100 Measures). This not only causes performance to significantly drop in the report but also requires tedious work to apply any changes to the measures.
A work around is to create a reference table that contains each of the metrics names. From there you can have a single measure that takes advantage of the SELECTEDVALUE() function, so that when a slicer or VISUAL-LEVEL FILTER is applied it can switch to the respective measure. This means you would only need to have 5 measures in total for however many metrics you need.
Except for the fact that buttons don't allow for individual level filters, and you're stuck with a laggy, cumbersome report that requires sacrificing functionality for performance.