Re: KPI Visualization - Problem With Multiple Sele...

jim_melichar · ‎04-26-2017

I have a report set up where I'm using the KPI Visualization along with a the slicer.

When choosing multiple values using the slicer the KPI Visualization only updates with the last value selected in the multiple select, rather than, in my case, summing the values associated with the KPI (revenue).

Eg: Slicer has Region 1, Region 2, Region 3

KPI has YTD revenue and YTD target revenue. When selecting Region 1, the KPI viz shows me Region 1 YTD Revenue and YTD Target Revenue. When control clicking the next region to select both Region 1 & Region 2 the KPI viz shows me only Region 2 YTD Revenue and Region 2 YTD Target Revenue.

I have several other column visualizations on the same report page, and in each one of those it sums the associated revenue and targets as I control click in the slicer for multiple regions.

I've also tried this with the custom "Chiclet Slicer" visualization and the problem is the same, therefore it seems to be an issue with the KPI visualization. Has anyone else noticed this? Can anyone else replicate the issue I'm having? Has this been reported anywhere else? Where could I report the issue?

Thank you in advance (I'm new to Power BI)

Jim

Phil_Seamark · ‎04-27-2017

Hi @jim_melichar

I think that is the way the KPI Visual is designed to work, in that it will always show the last value.

If you'd like it to show the sum of your selections you may need to create a measure that sums the underlying items and then see if that works with the visual.

To learn more about DAX visit : aka.ms/practicalDAX

Proud to be a Datanaut!

jim_melichar · ‎04-27-2017

Thanks for the reply Phil.

It's just an odd development choice considering all the other visuals will sum when a multiple select is in play. At the end of the day the slicer is just a fancy where clause. If it didn't work with the other limited set of visuals I'd understand it more.

It makes the KPI viz pretty worthless, in my opinion. I'm not sure how your workaround would be implemented, but perhaps this will be possible once I can use DAX with a live connection to our analysis cube.

Jim