topic Re: Power KPI Matrix - treat zero values as null comparison values in Custom Visuals Development Discussion

Power KPI Matrix - treat zero values as null comparison values

Anonymous — Thu, 28 Mar 2019 11:32:47 GMT

Hi,

In the Power KPI Matrix visual it's possible to set the option for "Treat zero values as null" for Current Value, however this option is missing for Comparison Value / Second Comparison Value. It is fairly common to have a zero as a KPI target, especially when thinking of health & safety (zero injury KPI for example), so it looks a little strange having an actual (current) value of 0 and a target (comparison) value of blank!

Would it be possible to add in the "Treat zero values as null" on/off for Comparison Value & Second Comparison Value?

Re: Power KPI Matrix - treat zero values as null comparison values

v-evelk — Fri, 29 Mar 2019 15:38:04 GMT

Hi,

These feature is already in the visaul backlog.

Thanks!

Evgenii Elkin,
Software Engineer
Microsoft Power BI Custom Visuals
pbicvsupport@microsoft.com

Re: Power KPI Matrix - treat zero values as null comparison values

jmb — Fri, 12 Jun 2020 16:22:52 GMT

Hi, I couldn't find any option to get the comparizon field to take 0 as 0 (rather then null) in PowerMatrix 3.1.1. Is there a better version ? Is there any horizon date to have this included ?

thanks in advance for your answer.

Re: Power KPI Matrix - treat zero values as null comparison values

paulbodman — Mon, 23 Oct 2023 09:34:04 GMT

also looking forward to this update! it does still look very odd to have comparison as null instead of blank

Re: Power KPI Matrix - treat zero values as null comparison values

vh_ — Sat, 12 Oct 2024 09:09:55 GMT

I am new to PowerBI and had this issue just yesterday - changed the measures used Comparison and Second Comparison values slightly.

Introduced an If condition in RETURN to check if the value was Blank() or 0 and assigned a small non-zero value such as 0.00001. This was done in all 3 measures used as Actual, Comparison and Second Comparison and the issue got resolved. It is just a workaround you can try while an actual the item gets picked up from the change backlog.

Please mark as "Solved" if it solves the problem!