Custom visual

Radar & Polar Pro Coming to AppSource

The radar chart that labels its rings, says what its axis is doing, and lets every axis have its own scale — with targets no other radar has.

Get in touch See the features Limitations

A six-spoke KPI scorecard with a dashed target outline and a coloured, labelled gap on every spoke. — A KPI scorecard for one quarter. The gap to target is drawn on every spoke: green where the target was beaten, red where it was missed, with the signed difference beside it.

Why this exists

Radar charts have two famous problems, and the stock visual has carried both for years: blanks are drawn at the centre where they read as zero, and one measure per spoke is impossible without reshaping your data — an open request since 2024. Every axis silently shares one scale, so a revenue spoke crushes a five-point rating into the centre. And no radar on AppSource has any concept of a target.

Features

●Three scales, each for a reason. One scale for all spokes is the default, and when one spoke dwarfs the rest the chart says so and names the remedy. Each spoke on its own range mixes revenue, NPS and a 1–5 rating on one web. Percent of each spoke’s target draws the target as one circle. Fix any spoke to its real business range — NPS is −100…100 whatever this month contains — and it holds through every slicer. The tooltip always names the scale in use.
●Targets with gap emphasis. Bind a target measure and get a target outline, a shaded band, or markers. Turn on the gap spurs and the shortfall itself is drawn on each spoke — green where met, red where missed, with a signed label. Nobody else has any of this.
●Pinned axis order. Power BI re-sorts your data whenever a slicer changes, so every other radar rearranges its axes under the reader. Pin the order once and the axes never move; new categories are appended and reported.
●Measures as axes. Leave the Axis well empty and drop in several measures — each measure becomes a spoke. Works on drillthrough pages.
●Honest by design. Blanks are gaps, not zeros — and a note counts them. Rings are labelled with what they mean. A scale that doesn’t start at zero says so, and names the spoke. A value beyond a fixed axis is drawn on the rim and reported, never silently clamped. Each note has its own close button, the format pane lists what you closed, and the notes about clamped values cannot be closed at all.
●Styled for reports. Per-series colours and line styles, curved shapes, marker shapes and borders, web or circular grid, web background fill, wrapped axis labels, ring-label chips that stay readable over the fills, data labels, and full high-contrast support.
●A full Power BI citizen. Cross-filtering with multi-select, right-click drill, report-page tooltips, keyboard navigation on the markers, and inbound slicers that work even with blanks in the data.
●Verified against an independent implementation. Every scale resolution, blank policy, sort and tick was checked against a clean-room oracle built separately from the visual — 164 checks on every build, plus a 24-point gate on the packaged file itself.

The same data twice: on one shared scale only the revenue spoke is readable; with each spoke on its own range every shape is readable. — Mixed units. Left: one shared scale, where a revenue of 610,000 squashes every other spoke, and the chart says so and names the setting to change. Right: each spoke on its own range.

Two radar charts filtered to different quarters with their spokes in the identical order. — Two quarters, one pinned spoke order. Sorted by value and left unpinned, NPS would jump from third place to fifth in the left chart. Pinned, a filter changes the values and nothing else.

Three team shapes; two outlines are open where a value is missing, and a note above the chart counts the missing values. — Missing is a gap, never a zero. Two outlines stay open where a value is missing and a note counts them, while Team A's real zero is drawn.

Three quarters of KPI results on a percent-of-target scale, the target drawn as one regular outline on the 100 percent ring. — Percent of target. The target is one outline on the 100% ring of every spoke, and the rim moves out to 110% because NPS beat its target by that much, so nothing is flattened against it.

Learn it properly

The Radar & Polar Pro tutorial explains which radial scale to use and why, targets and gaps, percent of target, missing values and pinned spokes, with two sample files you can download and follow along with.

Where it fits

KPI scorecards against target, team skill and competency assessments, supplier and product comparisons, survey results, OEE and quality dimensions — anywhere five to seven measures need one honest picture.

Honest limitations

We would rather you know these before you buy than after.

A radar is a poor chart past ~7 spokes. We warn instead of pretending — and you choose the threshold.
Per-spoke scaling trades comparability for readability by design; the tooltip always names the actual value and the scale used.
Targets are “higher is better” in v1. A lower-is-better target (cost per order) shows green when numerically above target, so express such a measure the other way round for now. Direction-aware targets are the first item for an update.
Percent of target needs a target above zero. A spoke whose target is zero or negative falls back to its own range, with a note; a negative value on this scale is drawn at the centre and reported as lower than it looks.
A log axis cannot show zero or negative values; they become gaps, counted in a note.
English-only labels and notes — same stance as our other visuals.

Questions about Radar & Polar Pro?

Pricing, a feature you need, whether it fits your model — ask, and a person who wrote it answers within two business days. It is in AppSource certification now.

Get in touch Read the tutorial Support & FAQ