KPI & summaryNative + ConfigurationAvoidLive example

Legacy multi-card

Legacy multi-card visual retained for backward compatibility.

Interactive example

Revenue€8.4M

Margin€2.1M

Budget€8.5M

Simulated behaviour on the shared fictional retail dataset. Native mechanism: Yes, legacy/deprecation direction.

Best for

Maintaining an existing report that depends on the legacy behavior.

Avoid when

New report design.

Typical data

Relevant recovered tags: legacy, multi card, kpi

Usage

Maintaining an existing report that depends on the legacy behavior.

Power BI limitation

Replaced for new work by the current Card visual, which can display multiple values and reference labels.