Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! It's time to submit your entry. Live now!
In the latest Power KPI 3.0.3.0, the line color will show the same color for the same series and different values, whereas in 2.0.0, the line color will show different for the same series but different values.
3.0.3.0
2.0.0
I think the 2.0.0 color scheme is better as 3.0.0 will mess data totally
Solved! Go to Solution.
Thanks very much for your details explaination John. Unfortunately, your solution is not suitable for my use case as I don't have a target to define colors. And the Microsoft team restored the Power KPI visual back to 2.0.0.0 a couple weeks ago, so now it is working as expected. They will launch the newer version after resolving this error. Many thanks.
n Power KPI 3.0.3.0 the visual binds colors to the series identity (legend category). That keeps a fixed color per series.
In 2.0.0, color could vary by the value/range, so the same series might change color as its values changed. Your screenshots show exactly that difference. So what you’re seeing in 3.0.3.0 is expected behavior after the change.
Pick the one that fits your setup:
Use thresholds / conditional colors (preferred)
Create a state measure and an optional color measure:
KPI State =
SWITCH(TRUE(),
[Value] >= [Target] * 1.05, "Good",
[Value] >= [Target] * 0.95, "Neutral",
TRUE(), "Bad"
)
KPI Color =
SWITCH([KPI State],
"Good", "#2F7E2F",
"Neutral","#F2C811",
"Bad", "#C64E4E"
)
In the Power KPI formatting, turn on conditional colors/thresholds (or “color by field value”) and bind KPI Color. That restores value-driven coloring for the line/markers.
Split a single series into categorical “states”
Materialize the states (Good/Neutral/Bad) into separate series (measures) and plot them together. Assign each series a fixed color. The line will appear to change color because different segments belong to different series.
Pin the older visual version
If you must keep exactly the 2.0.0 behavior, upload Power KPI 2.0.0 to Organizational Visuals and disable auto-update for that visual. Then use that pinned version in reports that need value-based coloring.
Did I answer your question? Mark my post as a solution! Appreciate your Kudos !!
Thanks very much for your details explaination John. Unfortunately, your solution is not suitable for my use case as I don't have a target to define colors. And the Microsoft team restored the Power KPI visual back to 2.0.0.0 a couple weeks ago, so now it is working as expected. They will launch the newer version after resolving this error. Many thanks.