Complete Power BI Component & Capability Inventory

The recovered interactive guide contained 133 catalog entries. That catalog intentionally mixed native Power BI visuals/features with Nudge BI representations, Power UI standardization assets, design-system tokens, custom visuals and reusable design patterns. This reconstruction preserves that coverage but labels the implementation status so those categories are not confused.

KPI & summary

Card

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Show one or more high-priority measures with optional reference labels and supporting values.
• Best for: Primary KPIs, actual vs target, actual vs previous period, compact executive summaries.
• Avoid when: Large metric inventories or cases where row-by-row comparison is the main task.
• Suitable data: Measure(s), Optional reference/detail fields
• Typical UX usage: Primary KPIs, actual vs target, actual vs previous period, compact executive summaries.
• Key configuration / design guidance: Show label → primary value → comparison(s). Use semantic color only for meaningful status. Keep number formats consistent.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Keep the number of callouts small. A card is a summary, not a substitute for a table or trend chart. The current Card visual is GA and replaces the legacy single-card and multi-card visuals for new reports.
• Recommended standard configuration: Show label → primary value → comparison(s). Use semantic color only for meaningful status. Keep number formats consistent.
• Possible reusable Figma component: Card representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Card representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Card
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-card

KPI visual

• Native Power BI: Yes
• Catalog status / standard: Core native / Situational
• Purpose: Communicate progress toward a measurable target, often with trend context.
• Best for: A single goal where status against a target is the primary question.
• Avoid when: Dashboards with many KPIs or situations where a Card with references is clearer.
• Suitable data: Indicator, Trend axis, Target
• Typical UX usage: A single goal where status against a target is the primary question.
• Key configuration / design guidance: Use only when target status is more important than the raw number. Clearly label the target and period.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Requires a meaningful target and trend axis to work well.
• Recommended standard configuration: Use only when target status is more important than the raw number. Clearly label the target and period.
• Possible reusable Figma component: KPI visual representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: KPI visual representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI KPI visual
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-kpi

Gauge

• Native Power BI: Yes
• Catalog status / standard: Core native / Use cautiously
• Purpose: Show progress of one measure within a meaningful minimum–maximum range.
• Best for: Capacity, threshold or progress situations where the scale itself has business meaning.
• Avoid when: General KPI reporting or comparing many entities.
• Suitable data: Value, Min/max, Target
• Typical UX usage: Capacity, threshold or progress situations where the scale itself has business meaning.
• Key configuration / design guidance: Always define meaningful min, max and target. Prefer Card + delta for most operational KPI use cases.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Consumes substantial space for one value and can exaggerate small differences.
• Recommended standard configuration: Always define meaningful min, max and target. Prefer Card + delta for most operational KPI use cases.
• Possible reusable Figma component: Gauge representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Gauge representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Gauge
• Recovered note: Use with caution. A linear bar/KPI is usually more space-efficient.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-radial-gauge-charts

Scorecard / Metrics

• Native Power BI: Yes
• Catalog status / standard: Core native / Situational
• Purpose: Track structured business goals, owners, status and progress.
• Best for: Goal-management scenarios rather than general report-page KPIs.
• Avoid when: Simple operational metric display.
• Suitable data: Metric, Target, Status/time
• Typical UX usage: Goal-management scenarios rather than general report-page KPIs.
• Key configuration / design guidance: Use when ownership, status and progress tracking are first-class requirements.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Best suited to goals/metrics workflows in the Power BI service.
• Recommended standard configuration: Use when ownership, status and progress tracking are first-class requirements.
• Possible reusable Figma component: Goals / scorecard representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Goals / scorecard representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Metrics / scorecard capability
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/create-reports/service-goals-introduction

Legacy single Card

• Native Power BI: Yes, legacy/deprecation direction
• Catalog status / standard: Legacy direction / Avoid new
• Purpose: Legacy single-measure Card retained for backward compatibility.
• Best for: Maintaining existing reports that already use the legacy Card.
• Avoid when: New report design.
• Suitable data: Relevant recovered tags: legacy, card, kpi
• Typical UX usage: Maintaining existing reports that already use the legacy Card.
• Key configuration / design guidance: Do not introduce into new standardized reports. Migrate when practical.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: The current Card visual became GA in November 2025 and is recommended for new reports.
• Recommended standard configuration: Do not introduce into new standardized reports. Migrate when practical.
• Possible reusable Figma component: A design-only representation of Legacy single Card may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-card

Legacy multi-card

• Native Power BI: Yes, legacy/deprecation direction
• Catalog status / standard: Legacy direction / Avoid new
• Purpose: Legacy multi-card visual retained for backward compatibility.
• Best for: Maintaining an existing report that depends on the legacy behavior.
• Avoid when: New report design.
• Suitable data: Relevant recovered tags: legacy, multi card, kpi
• Typical UX usage: Maintaining an existing report that depends on the legacy behavior.
• Key configuration / design guidance: Use the current Card for new work.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Replaced for new work by the current Card visual, which can display multiple values and reference labels.
• Recommended standard configuration: Use the current Card for new work.
• Possible reusable Figma component: A design-only representation of Legacy multi-card may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-card

Charts

Clustered bar chart

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Compare values across categories with horizontal bars.
• Best for: Rankings, long category labels, best/worst comparisons.
• Avoid when: Continuous time series with many periods.
• Suitable data: Category, Measure, Optional legend/series
• Typical UX usage: Rankings, long category labels, best/worst comparisons.
• Key configuration / design guidance: Sort by value when ranking matters. Start quantitative baseline at zero. Put value labels outside bars where useful.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Too many categories reduce scanability; consider Top N plus detail table.
• Recommended standard configuration: Sort by value when ranking matters. Start quantitative baseline at zero. Put value labels outside bars where useful.
• Possible reusable Figma component: Clustered bar chart representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Clustered bar chart representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Clustered bar chart
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-bar-column-charts

Clustered column chart

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Compare values across short categories or discrete time periods.
• Best for: Week/month comparisons, compact category comparisons.
• Avoid when: Long category labels or large category sets.
• Suitable data: Category/date, Measure, Optional legend/series
• Typical UX usage: Week/month comparisons, compact category comparisons.
• Key configuration / design guidance: Start at zero. Use direct labels selectively. Keep categories ordered logically.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Labels can collide quickly; horizontal bar is better for long labels.
• Recommended standard configuration: Start at zero. Use direct labels selectively. Keep categories ordered logically.
• Possible reusable Figma component: Clustered column chart representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Clustered column chart representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Clustered column chart
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-bar-column-charts

Stacked bar chart

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Compare totals while also showing their internal composition.
• Best for: Total + component comparisons across categories.
• Avoid when: Precise comparison of every segment across many categories.
• Suitable data: Category, Measure, Legend/series
• Typical UX usage: Total + component comparisons across categories.
• Key configuration / design guidance: Limit segment count. Keep stack order consistent. Use semantic/categorical colors deliberately.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Middle segments do not share a common baseline, reducing precision.
• Recommended standard configuration: Limit segment count. Keep stack order consistent. Use semantic/categorical colors deliberately.
• Possible reusable Figma component: Stacked bar chart representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Stacked bar chart representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Stacked bar chart
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-bar-column-charts

Stacked column chart

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Show composition across time or short categorical groups.
• Best for: Component mix by week/month.
• Avoid when: Many segments or long labels.
• Suitable data: Category/date, Measure, Legend/series
• Typical UX usage: Component mix by week/month.
• Key configuration / design guidance: Use a stable series order and restrained palette.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Composition is easier to compare than individual middle segments.
• Recommended standard configuration: Use a stable series order and restrained palette.
• Possible reusable Figma component: Stacked column chart representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Stacked column chart representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Stacked column chart
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-bar-column-charts

100% stacked bar chart

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Compare proportional composition where every total equals 100%.
• Best for: Share/mix comparisons across categories.
• Avoid when: When absolute totals matter.
• Suitable data: Category, Measure, Legend/series
• Typical UX usage: Share/mix comparisons across categories.
• Key configuration / design guidance: Label the percentage basis and provide absolute volume elsewhere if it affects interpretation.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Hides differences in total volume.
• Recommended standard configuration: Label the percentage basis and provide absolute volume elsewhere if it affects interpretation.
• Possible reusable Figma component: 100% stacked bar chart representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: 100% stacked bar chart representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI 100% stacked bar chart
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-bar-column-charts

100% stacked column chart

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Compare proportional composition across ordered categories or time.
• Best for: Share evolution over weeks/months.
• Avoid when: When absolute totals are essential.
• Suitable data: Category/date, Measure, Legend/series
• Typical UX usage: Share evolution over weeks/months.
• Key configuration / design guidance: Keep category count low and series order stable.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: All columns normalize to the same height.
• Recommended standard configuration: Keep category count low and series order stable.
• Possible reusable Figma component: 100% stacked column chart representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: 100% stacked column chart representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI 100% stacked column chart
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-bar-column-charts

Line chart

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Show trends, direction and change over a continuous or ordered axis.
• Best for: Actual vs previous year vs target over time.
• Avoid when: Unordered categories or dozens of overlapping series.
• Suitable data: Date/time, Measure, Optional legend/series
• Typical UX usage: Actual vs previous year vs target over time.
• Key configuration / design guidance: Make current/primary series visually dominant. Reference series should be quieter. A non-zero Y-axis is acceptable only when clearly communicated.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted), Drill on hierarchy, Analytics pane features where supported, Small multiples where supported
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Too many lines create legend dependence and crossing clutter.
• Recommended standard configuration: Make current/primary series visually dominant. Reference series should be quieter. A non-zero Y-axis is acceptable only when clearly communicated.
• Possible reusable Figma component: Line chart representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Line chart representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Line chart
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-line-chart

Area chart

• Native Power BI: Yes
• Catalog status / standard: Core native / Situational
• Purpose: Show a trend while emphasizing magnitude through filled area.
• Best for: Single-series volume evolution where magnitude is important.
• Avoid when: Precise multi-series comparisons.
• Suitable data: Date/time, Measure
• Typical UX usage: Single-series volume evolution where magnitude is important.
• Key configuration / design guidance: Prefer line charts unless the area encoding adds real meaning.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Filled area adds visual weight and can obscure differences.
• Recommended standard configuration: Prefer line charts unless the area encoding adds real meaning.
• Possible reusable Figma component: Area chart representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Area chart representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Area chart
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-area-charts

Stacked area chart

• Native Power BI: Yes
• Catalog status / standard: Core native / Use cautiously
• Purpose: Show cumulative composition changing over time.
• Best for: Few stable categories whose total and composition both matter.
• Avoid when: Many categories or when individual trends must be compared precisely.
• Suitable data: Date/time, Measure, Legend/series
• Typical UX usage: Few stable categories whose total and composition both matter.
• Key configuration / design guidance: Limit series count and preserve ordering.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Only the baseline series is easy to compare accurately.
• Recommended standard configuration: Limit series count and preserve ordering.
• Possible reusable Figma component: Stacked area chart representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Stacked area chart representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Stacked area chart
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-area-charts

Line + clustered column

• Native Power BI: Yes
• Catalog status / standard: Core native / Situational
• Purpose: Combine clustered columns and a line to compare related measures.
• Best for: Sales in columns with margin % or target as a line.
• Avoid when: Unrelated measures or misleading dual axes.
• Suitable data: Shared axis/category, Column measure, Line measure
• Typical UX usage: Sales in columns with margin % or target as a line.
• Key configuration / design guidance: Use only when measures are conceptually related. Label both scales clearly.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Dual axes can create false visual relationships.
• Recommended standard configuration: Use only when measures are conceptually related. Label both scales clearly.
• Possible reusable Figma component: Line + clustered column chart representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Line + clustered column chart representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Line + clustered column chart
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-combo-chart

Line + stacked column

• Native Power BI: Yes
• Catalog status / standard: Core native / Situational
• Purpose: Combine stacked composition with a line measure.
• Best for: Component totals plus an overall rate/target.
• Avoid when: Complex combinations that require extensive legend decoding.
• Suitable data: Shared axis/category, Stacked measures/series, Line measure
• Typical UX usage: Component totals plus an overall rate/target.
• Key configuration / design guidance: Keep the stacked portion simple and the line semantically distinct.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: High cognitive load when many stacked series are present.
• Recommended standard configuration: Keep the stacked portion simple and the line semantically distinct.
• Possible reusable Figma component: Line + stacked column chart representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Line + stacked column chart representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Line + stacked column chart
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-combo-chart

Ribbon chart

• Native Power BI: Yes
• Catalog status / standard: Core native / Situational
• Purpose: Show how category ranking changes across an ordered axis.
• Best for: Department rank by weekly sales.
• Avoid when: Absolute trend analysis or large category sets.
• Suitable data: Date/ordered category, Measure, Series/category
• Typical UX usage: Department rank by weekly sales.
• Key configuration / design guidance: Use when movement in rank is the question; otherwise use bar or line charts.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Focuses on rank transitions rather than precise values.
• Recommended standard configuration: Use when movement in rank is the question; otherwise use bar or line charts.
• Possible reusable Figma component: Ribbon chart representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Ribbon chart representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Ribbon chart
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-ribbon-charts

Waterfall chart

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Explain sequential positive and negative contributions from a starting value to an ending value.
• Best for: Budget → contributing effects → actual.
• Avoid when: Simple category magnitude comparisons.
• Suitable data: Category, Value/change, Optional breakdown
• Typical UX usage: Budget → contributing effects → actual.
• Key configuration / design guidance: Use a clear start/end, business-meaningful contribution order and semantic increase/decrease styling.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Too many steps make the story hard to follow.
• Recommended standard configuration: Use a clear start/end, business-meaningful contribution order and semantic increase/decrease styling.
• Possible reusable Figma component: Waterfall chart representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Waterfall chart representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Waterfall chart
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-waterfall-charts

Funnel chart

• Native Power BI: Yes
• Catalog status / standard: Core native / Use cautiously
• Purpose: Show sequential stages in a process where volume typically decreases.
• Best for: Views → cart → checkout → purchase.
• Avoid when: Any merely descending set of categories.
• Suitable data: Stage/category, Measure
• Typical UX usage: Views → cart → checkout → purchase.
• Key configuration / design guidance: Use stage labels and conversion context; don't use as a decorative ranking chart.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Requires a meaningful ordered process.
• Recommended standard configuration: Use stage labels and conversion context; don't use as a decorative ranking chart.
• Possible reusable Figma component: Funnel chart representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Funnel chart representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Funnel chart
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-funnel-charts

Scatter chart

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Show the relationship between two numeric measures and reveal clusters/outliers.
• Best for: Sales vs waste %, optionally bubble size = revenue.
• Avoid when: Simple category ranking or single-measure analysis.
• Suitable data: X measure, Y measure, Optional category/details, Optional size
• Typical UX usage: Sales vs waste %, optionally bubble size = revenue.
• Key configuration / design guidance: Explain axes, use size only for a meaningful third measure and provide tooltips for identifiers.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Requires enough data points and meaningful numeric axes.
• Recommended standard configuration: Explain axes, use size only for a meaningful third measure and provide tooltips for identifiers.
• Possible reusable Figma component: Scatter chart representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Scatter chart representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Scatter chart
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-scatter

Pie chart

• Native Power BI: Yes
• Catalog status / standard: Core native / Use cautiously
• Purpose: Show simple part-to-whole relationships.
• Best for: One total with a very small number of distinct categories.
• Avoid when: Precise comparison, close values, many categories or multiple totals.
• Suitable data: Category, Measure
• Typical UX usage: One total with a very small number of distinct categories.
• Key configuration / design guidance: Prefer bar or 100% stacked bar for most analytical comparisons.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Angle/area comparisons are less precise than aligned bars.
• Recommended standard configuration: Prefer bar or 100% stacked bar for most analytical comparisons.
• Possible reusable Figma component: Pie chart representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Pie chart representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Pie chart
• Recovered note: Use with caution: angle/area comparison is less precise than aligned bars.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-pie-donut-charts

Donut chart

• Native Power BI: Yes
• Catalog status / standard: Core native / Use cautiously
• Purpose: Show simple part-to-whole relationships in a ring layout.
• Best for: Same narrow scenarios as pie, sometimes with a central summary value.
• Avoid when: Many categories or precise comparisons.
• Suitable data: Category, Measure
• Typical UX usage: Same narrow scenarios as pie, sometimes with a central summary value.
• Key configuration / design guidance: Use sparingly and keep category count low.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Carries the same perceptual limitations as pie charts.
• Recommended standard configuration: Use sparingly and keep category count low.
• Possible reusable Figma component: Donut chart representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Donut chart representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Donut chart
• Recovered note: Use with caution for the same reasons as pie charts.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-pie-donut-charts

Treemap

• Native Power BI: Yes
• Catalog status / standard: Core native / Situational
• Purpose: Show hierarchical part-to-whole relationships using nested rectangles.
• Best for: Compact composition overview with many categories.
• Avoid when: Precise comparisons or values that are close together.
• Suitable data: Group, Details/hierarchy, Measure
• Typical UX usage: Compact composition overview with many categories.
• Key configuration / design guidance: Use for overview/exploration, with Table/Matrix for exact values.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Area comparison is imprecise and small labels can disappear.
• Recommended standard configuration: Use for overview/exploration, with Table/Matrix for exact values.
• Possible reusable Figma component: Treemap representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Treemap representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Treemap
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-treemaps

100% stacked area chart

• Native Power BI: Yes
• Catalog status / standard: Core native / Situational
• Purpose: Show how proportional composition changes over an ordered/continuous axis, normalized to 100% at each point.
• Best for: Share or mix evolution over time where relative composition matters more than total magnitude.
• Avoid when: When absolute volume matters or precise comparison of middle series is required.
• Suitable data: Relevant recovered tags: 100% stacked area, area, proportion, time, composition
• Typical UX usage: Share or mix evolution over time where relative composition matters more than total magnitude.
• Key configuration / design guidance: Keep series count low, preserve stack order, and provide absolute totals elsewhere when volume affects interpretation.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Normalization hides total-volume changes. Multiple filled series quickly become difficult to compare.
• Recommended standard configuration: Keep series count low, preserve stack order, and provide absolute totals elsewhere when volume affects interpretation.
• Possible reusable Figma component: A design-only representation of 100% stacked area chart may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-line-chart

Tables & detail

Table

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Display exact values in a flat row/column structure.
• Best for: Detailed comparison, exportable records, operational data.
• Avoid when: Hierarchies that users need to expand/collapse.
• Suitable data: Dimensions, Measures/columns
• Typical UX usage: Detailed comparison, exportable records, operational data.
• Key configuration / design guidance: Text left, numbers right. Define default sort. Use consistent decimals. Conditional formatting should highlight exceptions, not decorate every cell.
• Interaction capabilities: Sort, Resize columns (viewer behavior varies), Conditional formatting, Tooltips, Cross-filter, Export, Scroll
• Accessibility considerations: Use meaningful headers, logical sort/order, consistent number formatting, non-color cues and a sensible reading/tab order.
• Known limitations / restrictions: Dense tables become hard to scan; use only columns required for the task.
• Recommended standard configuration: Text left, numbers right. Define default sort. Use consistent decimals. Conditional formatting should highlight exceptions, not decorate every cell.
• Possible reusable Figma component: Table representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Table representation (verify kit version) | Power UI: Enterprise table configuration: density, headers, totals, semantic formatting
• Native implementation mapping: Power BI Table
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-tables

Matrix

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Display hierarchical and multidimensional data with expand/collapse, subtotals and drill.
• Best for: BAF → product group → article, hierarchical operational analysis.
• Avoid when: Simple flat datasets where a Table is clearer.
• Suitable data: Row hierarchy, Optional column hierarchy, Measures
• Typical UX usage: BAF → product group → article, hierarchical operational analysis.
• Key configuration / design guidance: Use native hierarchy instead of manual indentation. Define subtotal logic explicitly. Keep measure set focused.
• Interaction capabilities: Drill/expand/collapse, Sort, Conditional formatting, Tooltips, Cross-filter, Export, Scroll
• Accessibility considerations: Use meaningful headers, logical sort/order, consistent number formatting, non-color cues and a sensible reading/tab order.
• Known limitations / restrictions: Deep hierarchies and too many columns create horizontal/vertical complexity. Validate totals and subtotals carefully.
• Recommended standard configuration: Use native hierarchy instead of manual indentation. Define subtotal logic explicitly. Keep measure set focused.
• Possible reusable Figma component: Matrix representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Matrix representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Matrix
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-matrix-visual

Sparklines in Table/Matrix

• Native Power BI: Conditional — preview
• Catalog status / standard: Preview / Pilot only
• Purpose: Add compact trend context inside Table or Matrix cells.
• Best for: Exact values are primary, but direction over time adds useful context.
• Avoid when: When the trend itself is the main analytical message.
• Suitable data: Relevant recovered tags: sparkline, table, matrix, preview, trend
• Typical UX usage: Exact values are primary, but direction over time adds useful context.
• Key configuration / design guidance: Use as secondary context and keep a full line chart for important trends.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use meaningful headers, logical sort/order, consistent number formatting, non-color cues and a sensible reading/tab order.
• Known limitations / restrictions: Preview capability; not a standalone chart. Validate support and export/accessibility behavior.
• Recommended standard configuration: Use as secondary context and keep a full line chart for important trends.
• Possible reusable Figma component: A design-only representation of Sparklines in Table/Matrix may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/create-reports/power-bi-sparklines-tables

Filters & slicers

Standard Slicer

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Expose a frequently used filter directly on the report canvas.
• Best for: Common user-controlled filtering by categories, dates or numeric ranges.
• Avoid when: Filters that users rarely touch; those can remain in the Filters pane.
• Suitable data: Relevant recovered tags: slicer, filter, canvas
• Typical UX usage: Common user-controlled filtering by categories, dates or numeric ranges.
• Key configuration / design guidance: Show only high-value filters. Use a consistent placement and visible selected state.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use clear labels and visible selected/active state; preserve keyboard access/focus order; do not hide critical state.
• Known limitations / restrictions: Too many slicers consume canvas space and increase interaction complexity.
• Recommended standard configuration: Show only high-value filters. Use a consistent placement and visible selected state.
• Possible reusable Figma component: A design-only representation of Standard Slicer may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-slicer-visual

Dropdown Slicer

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Compact selection from medium/large value sets.
• Best for: Store, department, budget type, channel.
• Avoid when: 2–5 obvious options where buttons are faster.
• Suitable data: Relevant recovered tags: dropdown, slicer, filter
• Typical UX usage: Store, department, budget type, channel.
• Key configuration / design guidance: Use for secondary filters and long option sets. Enable search where appropriate.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use clear labels and visible selected/active state; preserve keyboard access/focus order; do not hide critical state.
• Known limitations / restrictions: Selection is hidden when collapsed; ensure the current value remains legible.
• Recommended standard configuration: Use for secondary filters and long option sets. Enable search where appropriate.
• Possible reusable Figma component: A design-only representation of Dropdown Slicer may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-slicer-visual

Vertical List Slicer

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Keep filter choices visible in a vertical list and optionally support hierarchy/search.
• Best for: Short to medium option sets or hierarchical filters.
• Avoid when: Very long lists without search or limited vertical space.
• Suitable data: Relevant recovered tags: list, slicer, hierarchy
• Typical UX usage: Short to medium option sets or hierarchical filters.
• Key configuration / design guidance: Use when visibility of choices matters more than space efficiency.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use clear labels and visible selected/active state; preserve keyboard access/focus order; do not hide critical state.
• Known limitations / restrictions: Consumes more space than dropdown.
• Recommended standard configuration: Use when visibility of choices matters more than space efficiency.
• Possible reusable Figma component: A design-only representation of Vertical List Slicer may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-slicer-visual

Tile Slicer

• Native Power BI: Yes
• Catalog status / standard: Core native / Situational
• Purpose: Display short values as button-like tiles.
• Best for: Year, status, short period labels.
• Avoid when: Long labels, hierarchies or large option sets.
• Suitable data: Relevant recovered tags: tile, slicer, buttons
• Typical UX usage: Year, status, short period labels.
• Key configuration / design guidance: Use when users switch frequently and choices fit on one row or compact grid.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use clear labels and visible selected/active state; preserve keyboard access/focus order; do not hide critical state.
• Known limitations / restrictions: Standard tile mode doesn't support hierarchy.
• Recommended standard configuration: Use when users switch frequently and choices fit on one row or compact grid.
• Possible reusable Figma component: A design-only representation of Tile Slicer may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-slicer-visual

Between Slicer

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Select a start/end range for dates or numeric values.
• Best for: Date range, price range, quantity range.
• Avoid when: Discrete categories.
• Suitable data: Relevant recovered tags: range, between, date, numeric
• Typical UX usage: Date range, price range, quantity range.
• Key configuration / design guidance: Label units and range meaning clearly.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use clear labels and visible selected/active state; preserve keyboard access/focus order; do not hide critical state.
• Known limitations / restrictions: Range sliders can be imprecise; input fields should remain available.
• Recommended standard configuration: Label units and range meaning clearly.
• Possible reusable Figma component: A design-only representation of Between Slicer may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-slicer-visual

Before / After Slicer

• Native Power BI: Yes
• Catalog status / standard: Core native / Situational
• Purpose: Apply a single upper or lower boundary to dates/numbers.
• Best for: Before date X, after threshold Y.
• Avoid when: When both range endpoints are required.
• Suitable data: Relevant recovered tags: before, after, boundary
• Typical UX usage: Before date X, after threshold Y.
• Key configuration / design guidance: Use a clear label that communicates which side of the boundary is included.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use clear labels and visible selected/active state; preserve keyboard access/focus order; do not hide critical state.
• Known limitations / restrictions: One-sided boundary only.
• Recommended standard configuration: Use a clear label that communicates which side of the boundary is included.
• Possible reusable Figma component: A design-only representation of Before / After Slicer may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-slicer-visual

Relative Date Slicer

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Filter using rolling periods that update automatically.
• Best for: Last 7 days, previous month, last 12 months.
• Avoid when: Fixed historical reporting where exact date range must remain stable.
• Suitable data: Relevant recovered tags: relative date, rolling period, date
• Typical UX usage: Last 7 days, previous month, last 12 months.
• Key configuration / design guidance: State whether partial/current periods are included.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use clear labels and visible selected/active state; preserve keyboard access/focus order; do not hide critical state.
• Known limitations / restrictions: Users need to understand relative-period semantics.
• Recommended standard configuration: State whether partial/current periods are included.
• Possible reusable Figma component: A design-only representation of Relative Date Slicer may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/desktop-slicer-filter-date-range

Relative Time Slicer

• Native Power BI: Yes
• Catalog status / standard: Core native / Situational
• Purpose: Filter recent time windows at hour/minute granularity.
• Best for: Near-real-time operational monitoring.
• Avoid when: Normal daily/weekly business reporting.
• Suitable data: Relevant recovered tags: relative time, real time, slicer
• Typical UX usage: Near-real-time operational monitoring.
• Key configuration / design guidance: Use only when data freshness supports the selected window.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use clear labels and visible selected/active state; preserve keyboard access/focus order; do not hide critical state.
• Known limitations / restrictions: Requires date/time granularity and appropriate refresh cadence.
• Recommended standard configuration: Use only when data freshness supports the selected window.
• Possible reusable Figma component: A design-only representation of Relative Time Slicer may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/slicer-filter-relative-time

Date Picker Slicer

• Native Power BI: Conditional — preview
• Catalog status / standard: Preview / Pilot only
• Purpose: Provide a modern date-picking interaction for date filtering.
• Best for: Date-oriented reports where the preview behavior has been validated.
• Avoid when: Standardized production patterns before approval.
• Suitable data: Relevant recovered tags: date picker, preview, slicer
• Typical UX usage: Date-oriented reports where the preview behavior has been validated.
• Key configuration / design guidance: Do not make it a design-system default until GA and tested in embedded/mobile contexts.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use clear labels and visible selected/active state; preserve keyboard access/focus order; do not hide critical state.
• Known limitations / restrictions: Preview: behavior and availability can change.
• Recommended standard configuration: Do not make it a design-system default until GA and tested in embedded/mobile contexts.
• Possible reusable Figma component: A design-only representation of Date Picker Slicer may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-slicers

Button Slicer

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Filter using highly visible, styleable buttons.
• Best for: 2–7 frequent options such as Actual/Budget/PY or sales channel.
• Avoid when: Tens or hundreds of values.
• Suitable data: Field
• Typical UX usage: 2–7 frequent options such as Actual/Budget/PY or sales channel.
• Key configuration / design guidance: Keep labels short, states unmistakable, and selection behavior consistent.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Use clear labels and visible selected/active state; preserve keyboard access/focus order; do not hide critical state.
• Known limitations / restrictions: Large option sets create scrolling and visual noise.
• Recommended standard configuration: Keep labels short, states unmistakable, and selection behavior consistent.
• Possible reusable Figma component: Button slicer representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Button slicer representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Button slicer
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-button-slicer

List Slicer

• Native Power BI: Conditional — preview
• Catalog status / standard: Preview / Pilot only
• Purpose: Filter via a rich vertical list with hierarchy, search, conditional formatting and pasted selection.
• Best for: Large navigable lists where preview use is approved.
• Avoid when: Default production standard while still in preview.
• Suitable data: Field(s)/hierarchy
• Typical UX usage: Large navigable lists where preview use is approved.
• Key configuration / design guidance: Pilot for large store/product hierarchies; keep a fallback to standard slicer.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Use clear labels and visible selected/active state; preserve keyboard access/focus order; do not hide critical state.
• Known limitations / restrictions: Preview; availability/behavior can change and is documented primarily for Desktop.
• Recommended standard configuration: Pilot for large store/product hierarchies; keep a fallback to standard slicer.
• Possible reusable Figma component: List slicer representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: List slicer representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI List slicer
• Recovered note: Preview; keyboard/screen-reader support may be incomplete during preview.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-list-slicer

Input Slicer

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Filter by typed or pasted text/numeric values with configurable operators.
• Best for: Known identifiers such as article number, store ID, order ID or supplier number.
• Avoid when: Small known option sets that are easier to browse.
• Suitable data: Text or numeric field
• Typical UX usage: Known identifiers such as article number, store ID, order ID or supplier number.
• Key configuration / design guidance: Use for very large value universes. Provide an example placeholder and sensible operator default.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Use clear labels and visible selected/active state; preserve keyboard access/focus order; do not hide critical state.
• Known limitations / restrictions: Supports text/numeric columns; report author controls single/multiple input. Paste uses keyboard shortcuts.
• Recommended standard configuration: Use for very large value universes. Provide an example placeholder and sensible operator default.
• Possible reusable Figma component: Input slicer representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Input slicer representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Input slicer
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-input-slicer

Filters pane

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Centralized management of visual-, page- and report-level filters.
• Best for: Secondary/advanced filters and scoped filter logic.
• Avoid when: Hiding the few filters users need constantly.
• Suitable data: Relevant recovered tags: filters pane, visual filter, page filter, report filter
• Typical UX usage: Secondary/advanced filters and scoped filter logic.
• Key configuration / design guidance: Use visual/page/report scope deliberately and document default filters.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use clear labels and visible selected/active state; preserve keyboard access/focus order; do not hide critical state.
• Known limitations / restrictions: Less visible than canvas slicers; users may overlook active filters.
• Recommended standard configuration: Use visual/page/report scope deliberately and document default filters.
• Possible reusable Figma component: A design-only representation of Filters pane may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/create-reports/power-bi-report-add-filter

Interactions

Cross-filter

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Selecting one visual filters related visuals to the selected subset.
• Best for: Category selection should narrow the rest of the page.
• Avoid when: When the relationship is surprising, irrelevant or removes useful context.
• Suitable data: Relevant recovered tags: cross-filter, interaction, selection
• Typical UX usage: Category selection should narrow the rest of the page.
• Key configuration / design guidance: Define interaction intent per visual; disable meaningless cross-filter paths.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use clear labels and visible selected/active state; preserve keyboard access/focus order; do not hide critical state.
• Known limitations / restrictions: Default interactions are not automatically the right interactions.
• Recommended standard configuration: Define interaction intent per visual; disable meaningless cross-filter paths.
• Possible reusable Figma component: A design-only representation of Cross-filter may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/create-reports/service-reports-visual-interactions

Cross-highlight

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Highlight the selected contribution while retaining total context.
• Best for: Contribution-to-total analysis.
• Avoid when: When a clean filtered subset is easier to interpret.
• Suitable data: Relevant recovered tags: cross-highlight, interaction, context
• Typical UX usage: Contribution-to-total analysis.
• Key configuration / design guidance: Ensure highlighted vs non-highlighted states remain distinguishable without color alone.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use clear labels and visible selected/active state; preserve keyboard access/focus order; do not hide critical state.
• Known limitations / restrictions: Can be visually subtle depending on chart and palette.
• Recommended standard configuration: Ensure highlighted vs non-highlighted states remain distinguishable without color alone.
• Possible reusable Figma component: A design-only representation of Cross-highlight may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/create-reports/service-reports-visual-interactions

Drill down / up

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Move through hierarchy levels inside the same visual.
• Best for: Year → quarter → month or BAF → product group → article.
• Avoid when: When the next step requires a fundamentally different layout.
• Suitable data: Relevant recovered tags: drill, hierarchy, drill down, drill up
• Typical UX usage: Year → quarter → month or BAF → product group → article.
• Key configuration / design guidance: Use for vertical hierarchy exploration; use Drillthrough for a dedicated detail page.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use clear labels and visible selected/active state; preserve keyboard access/focus order; do not hide critical state.
• Known limitations / restrictions: Hierarchy must be meaningful and discoverable.
• Recommended standard configuration: Use for vertical hierarchy exploration; use Drillthrough for a dedicated detail page.
• Possible reusable Figma component: A design-only representation of Drill down / up may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/consumer/end-user-drill

Drillthrough

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Navigate from a summary selection to a dedicated detail page carrying filter context.
• Best for: Overview → department detail → article detail.
• Avoid when: Small inline expansions that can be handled by hierarchy drill.
• Suitable data: Relevant recovered tags: drillthrough, detail, navigation
• Typical UX usage: Overview → department detail → article detail.
• Key configuration / design guidance: Keep the automatic Back button; label selected context clearly; avoid blank/error visuals after filtering.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use clear labels and visible selected/active state; preserve keyboard access/focus order; do not hide critical state.
• Known limitations / restrictions: Requires drillthrough fields and a detail page designed for the selected context.
• Recommended standard configuration: Keep the automatic Back button; label selected context clearly; avoid blank/error visuals after filtering.
• Possible reusable Figma component: A design-only representation of Drillthrough may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/create-reports/desktop-drillthrough

Standard Tooltip

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Show supplementary values on hover.
• Best for: Exact values and supporting measures that do not need constant display.
• Avoid when: Essential information required to understand the chart.
• Suitable data: Relevant recovered tags: tooltip, hover, detail
• Typical UX usage: Exact values and supporting measures that do not need constant display.
• Key configuration / design guidance: Keep concise and consistent. Never make tooltip-only information business-critical.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use clear labels and visible selected/active state; preserve keyboard access/focus order; do not hide critical state.
• Known limitations / restrictions: Hover-dependent and less discoverable on touch devices.
• Recommended standard configuration: Keep concise and consistent. Never make tooltip-only information business-critical.
• Possible reusable Figma component: A design-only representation of Standard Tooltip may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-tooltips-overview

Report Page Tooltip

• Native Power BI: Yes
• Catalog status / standard: Core native / Situational
• Purpose: Show a mini report page as contextual hover content.
• Best for: Rich supplementary context with several measures or mini visuals.
• Avoid when: Interactive tasks or content that requires scrolling.
• Suitable data: Relevant recovered tags: report tooltip, hover, mini report
• Typical UX usage: Rich supplementary context with several measures or mini visuals.
• Key configuration / design guidance: All content must fit. Use Drillthrough if the user needs to interact.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use clear labels and visible selected/active state; preserve keyboard access/focus order; do not hide critical state.
• Known limitations / restrictions: Not interactive; users can't select slicers, tab through or scroll it. Screen readers can't read tooltip-page content when it appears on a data point.
• Recommended standard configuration: All content must fit. Use Drillthrough if the user needs to interact.
• Possible reusable Figma component: A design-only representation of Report Page Tooltip may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/create-reports/desktop-tooltips

Help Tooltip

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Explain terminology, calculation or metric meaning.
• Best for: Specialized metrics, abbreviations and non-obvious business rules.
• Avoid when: Long documentation or essential instructions.
• Suitable data: Relevant recovered tags: help, tooltip, definition
• Typical UX usage: Specialized metrics, abbreviations and non-obvious business rules.
• Key configuration / design guidance: Keep definitions short and provide persistent help for critical concepts.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use clear labels and visible selected/active state; preserve keyboard access/focus order; do not hide critical state.
• Known limitations / restrictions: Hover/focus discoverability; screen-reader limitations apply to tooltip content.
• Recommended standard configuration: Keep definitions short and provide persistent help for critical concepts.
• Possible reusable Figma component: A design-only representation of Help Tooltip may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/create-reports/desktop-visual-tooltips

Field Parameters

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Let users dynamically switch measures or dimensions used by one or more visuals.
• Best for: Sales/Margin/Waste switch, Week/Period/Year switch, Department/Product group/Article switch.
• Avoid when: Huge collections of unrelated metrics.
• Suitable data: Relevant recovered tags: field parameter, switch, measure, dimension
• Typical UX usage: Sales/Margin/Waste switch, Week/Period/Year switch, Department/Product group/Article switch.
• Key configuration / design guidance: Use to avoid duplicated charts and keep one analytical pattern reusable.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use clear labels and visible selected/active state; preserve keyboard access/focus order; do not hide critical state.
• Known limitations / restrictions: Changes data configuration, not arbitrary visual layout. Requires semantic-model setup.
• Recommended standard configuration: Use to avoid duplicated charts and keep one analytical pattern reusable.
• Possible reusable Figma component: A design-only representation of Field Parameters may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/create-reports/power-bi-field-parameters

Small Multiples

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Repeat the same chart in aligned panels by category.
• Best for: Compare trend shapes across departments or regions.
• Avoid when: Large category sets or exact-value tasks.
• Suitable data: Relevant recovered tags: small multiples, facets, compare
• Typical UX usage: Compare trend shapes across departments or regions.
• Key configuration / design guidance: Use shared scales where comparison requires it. Limit panel count.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use clear labels and visible selected/active state; preserve keyboard access/focus order; do not hide critical state.
• Known limitations / restrictions: Supported only for specific chart families; panel space becomes constrained quickly.
• Recommended standard configuration: Use shared scales where comparison requires it. Limit panel count.
• Possible reusable Figma component: A design-only representation of Small Multiples may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-small-multiples

Navigation & state

Bookmarks

• Native Power BI: Yes
• Catalog status / standard: Core native / Situational
• Purpose: Save report state including filters, slicers, sort, drill, visibility and current page.
• Best for: View states, storytelling, controlled show/hide panels.
• Avoid when: Simulating functionality better handled by field parameters or page navigation.
• Suitable data: Relevant recovered tags: bookmark, state, show hide
• Typical UX usage: View states, storytelling, controlled show/hide panels.
• Key configuration / design guidance: Name bookmarks clearly and configure Data/Display/Current page intentionally.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use clear labels and visible selected/active state; preserve keyboard access/focus order; do not hide critical state.
• Known limitations / restrictions: Bookmarks capture state; complex overlapping bookmark logic becomes hard to maintain.
• Recommended standard configuration: Name bookmarks clearly and configure Data/Display/Current page intentionally.
• Possible reusable Figma component: A design-only representation of Bookmarks may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/create-reports/desktop-bookmarks

Page Navigator

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Automatically create navigation buttons synchronized with report pages.
• Best for: Primary navigation across report pages.
• Avoid when: Custom manual page-button sets unless there is a validated need.
• Suitable data: Report page structure
• Typical UX usage: Primary navigation across report pages.
• Key configuration / design guidance: Preferred over manually maintaining page-navigation buttons.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Use clear labels and visible selected/active state; preserve keyboard access/focus order; do not hide critical state.
• Known limitations / restrictions: Shows pages according to navigator configuration; hidden/tooltip pages require deliberate handling.
• Recommended standard configuration: Preferred over manually maintaining page-navigation buttons.
• Possible reusable Figma component: Page navigator representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Page navigator representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Page navigator
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/create-reports/button-navigators

Bookmark Navigator

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Automatically create controls for bookmarks or bookmark groups.
• Best for: View toggles and state switching.
• Avoid when: Multiple navigators controlling overlapping settings.
• Suitable data: Bookmarks
• Typical UX usage: View toggles and state switching.
• Key configuration / design guidance: Each navigator should control a clearly separate concern.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Use clear labels and visible selected/active state; preserve keyboard access/focus order; do not hide critical state.
• Known limitations / restrictions: Only one bookmark can be active globally; overlapping bookmark groups can show confusing selected states.
• Recommended standard configuration: Each navigator should control a clearly separate concern.
• Possible reusable Figma component: Bookmark navigator representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Bookmark navigator representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Bookmark navigator
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/create-reports/button-navigators

Button

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Trigger native actions such as Back, Bookmark, Drillthrough, Page navigation or URL.
• Best for: View details, Back, Reset, explicit actions.
• Avoid when: Vague labels or duplicated navigation already covered by navigators.
• Suitable data: No data required; optional conditional formatting
• Typical UX usage: View details, Back, Reset, explicit actions.
• Key configuration / design guidance: Use action-oriented labels and define Default/Hover/Pressed/Disabled states.
• Interaction capabilities: Default, Hover, Press, Disabled in supported contexts, Loading for data functions
• Accessibility considerations: Use clear labels and visible selected/active state; preserve keyboard access/focus order; do not hide critical state.
• Known limitations / restrictions: Available actions depend on report context; disabled/loading states apply to certain actions.
• Recommended standard configuration: Use action-oriented labels and define Default/Hover/Pressed/Disabled states.
• Possible reusable Figma component: Button representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Button representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Button
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/create-reports/desktop-buttons

Apply all slicers button

• Native Power BI: Yes
• Catalog status / standard: Core native / Situational
• Purpose: Apply a set of slicer changes in one explicit action.
• Best for: Expensive queries, complex filter panels or search-like workflows.
• Avoid when: Normal lightweight filtering where instant feedback is expected.
• Suitable data: Relevant recovered tags: apply slicers, button, filters
• Typical UX usage: Expensive queries, complex filter panels or search-like workflows.
• Key configuration / design guidance: Use only when the delayed-apply behavior has clear performance or workflow value.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use clear labels and visible selected/active state; preserve keyboard access/focus order; do not hide critical state.
• Known limitations / restrictions: Adds an extra interaction step.
• Recommended standard configuration: Use only when the delayed-apply behavior has clear performance or workflow value.
• Possible reusable Figma component: A design-only representation of Apply all slicers button may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/create-reports/buttons-apply-all-clear-all-slicers

Clear all slicers button

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Clear active slicer selections.
• Best for: Reports with several user-controlled slicers.
• Avoid when: When the intended reset state is not equivalent to 'clear'.
• Suitable data: Relevant recovered tags: clear slicers, reset, filters
• Typical UX usage: Reports with several user-controlled slicers.
• Key configuration / design guidance: If a specific default state is required, use an appropriate reset/bookmark pattern instead.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use clear labels and visible selected/active state; preserve keyboard access/focus order; do not hide critical state.
• Known limitations / restrictions: Clear and reset-to-designed-default are not always the same thing.
• Recommended standard configuration: If a specific default state is required, use an appropriate reset/bookmark pattern instead.
• Possible reusable Figma component: A design-only representation of Clear all slicers button may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/create-reports/buttons-apply-all-clear-all-slicers

Focus Mode

• Native Power BI: Yes
• Catalog status / standard: Core native / Situational
• Purpose: Expand one visual for closer inspection.
• Best for: Dense Matrix/Table or detailed chart exploration.
• Avoid when: As compensation for a page where primary visuals are permanently too small.
• Suitable data: Relevant recovered tags: focus mode, inspect, visual header
• Typical UX usage: Dense Matrix/Table or detailed chart exploration.
• Key configuration / design guidance: Allow it where detail inspection helps, but design the normal page to remain usable.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use clear labels and visible selected/active state; preserve keyboard access/focus order; do not hide critical state.
• Known limitations / restrictions: Moves user temporarily out of the full dashboard context.
• Recommended standard configuration: Allow it where detail inspection helps, but design the normal page to remain usable.
• Possible reusable Figma component: A design-only representation of Focus Mode may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/consumer/end-user-focus

Visual Header

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Expose contextual actions such as drill, focus, sort, filters, export or more options.
• Best for: Only actions that help users operate the specific visual.
• Avoid when: Showing every available icon by default.
• Suitable data: Relevant recovered tags: visual header, actions, icons
• Typical UX usage: Only actions that help users operate the specific visual.
• Key configuration / design guidance: Curate the header; unnecessary controls add clutter and accidental complexity.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use clear labels and visible selected/active state; preserve keyboard access/focus order; do not hide critical state.
• Known limitations / restrictions: Header capabilities vary by visual and environment.
• Recommended standard configuration: Curate the header; unnecessary controls add clutter and accidental complexity.
• Possible reusable Figma component: A design-only representation of Visual Header may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/create-reports/visual-header

Sorting

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Control data order in supported visuals.
• Best for: Ranking, chronology and defined business sequences.
• Avoid when: Relying on automatic alphabetical order when it conflicts with analytical intent.
• Suitable data: Relevant recovered tags: sort, ranking, chronology
• Typical UX usage: Ranking, chronology and defined business sequences.
• Key configuration / design guidance: Define default sort in functional design and validate it in QA.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use clear labels and visible selected/active state; preserve keyboard access/focus order; do not hide critical state.
• Known limitations / restrictions: Sort options depend on visual/fields.
• Recommended standard configuration: Define default sort in functional design and validate it in QA.
• Possible reusable Figma component: A design-only representation of Sorting may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/consumer/end-user-change-sort

Analytics & formatting

Conditional Formatting

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Apply data-driven font, background, icons, bars or property formatting.
• Best for: Exception detection, threshold/status cues, compact in-cell magnitude.
• Avoid when: Coloring every value or creating a traffic-light wall.
• Suitable data: Relevant recovered tags: conditional formatting, icons, data bars, rules
• Typical UX usage: Exception detection, threshold/status cues, compact in-cell magnitude.
• Key configuration / design guidance: Use semantic rules and redundant cues (icon/text + color).
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Support varies by visual/property.
• Recommended standard configuration: Use semantic rules and redundant cues (icon/text + color).
• Possible reusable Figma component: A design-only representation of Conditional Formatting may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/create-reports/desktop-conditional-table-formatting

Analytics Pane

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Add analytical overlays such as reference lines, trend, forecast, anomalies and error bars where supported.
• Best for: Targets, averages, thresholds, statistical context.
• Avoid when: Manual overlays that duplicate native analytics capabilities.
• Suitable data: Relevant recovered tags: analytics pane, reference line, forecast
• Typical UX usage: Targets, averages, thresholds, statistical context.
• Key configuration / design guidance: Prefer native analytics features when they express the intended business rule accurately.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Available capabilities depend on visual type.
• Recommended standard configuration: Prefer native analytics features when they express the intended business rule accurately.
• Possible reusable Figma component: A design-only representation of Analytics Pane may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/transform-model/desktop-analytics-pane

Reference / constant lines

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Show fixed thresholds, targets or comparison levels on supported charts.
• Best for: Norm, target, limit, average reference.
• Avoid when: Decorative lines without a defined business meaning.
• Suitable data: Relevant recovered tags: reference line, constant, target, norm
• Typical UX usage: Norm, target, limit, average reference.
• Key configuration / design guidance: Label the reference directly where possible and distinguish it from actual series.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Support and configuration depend on visual.
• Recommended standard configuration: Label the reference directly where possible and distinguish it from actual series.
• Possible reusable Figma component: A design-only representation of Reference / constant lines may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/transform-model/desktop-analytics-pane

Forecast

• Native Power BI: Yes
• Catalog status / standard: Core native / Situational
• Purpose: Extend supported line-chart time series statistically into the future.
• Best for: Exploratory forecast context when the native model assumptions are acceptable.
• Avoid when: Treating statistical extrapolation as an approved business forecast without validation.
• Suitable data: Relevant recovered tags: forecast, future, analytics
• Typical UX usage: Exploratory forecast context when the native model assumptions are acceptable.
• Key configuration / design guidance: Clearly distinguish actual, forecast and confidence interval.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Availability depends on line-chart configuration and data.
• Recommended standard configuration: Clearly distinguish actual, forecast and confidence interval.
• Possible reusable Figma component: A design-only representation of Forecast may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/transform-model/desktop-analytics-pane

Error Bars

• Native Power BI: Yes
• Catalog status / standard: Core native / Situational
• Purpose: Show uncertainty or upper/lower bounds on supported visuals.
• Best for: Statistical or forecast ranges where uncertainty is material.
• Avoid when: Operational dashboards where the bounds are not defined or understood.
• Suitable data: Relevant recovered tags: error bars, uncertainty, range
• Typical UX usage: Statistical or forecast ranges where uncertainty is material.
• Key configuration / design guidance: Explain what the range represents.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Requires valid upper/lower measures and supported visual.
• Recommended standard configuration: Explain what the range represents.
• Possible reusable Figma component: A design-only representation of Error Bars may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/transform-model/desktop-analytics-pane

Visual Calculations

• Native Power BI: Yes
• Catalog status / standard: Core native / Situational
• Purpose: Create calculations scoped to a visual, using the visual structure itself.
• Best for: Running sums, moving calculations or visual-specific transformations where appropriate.
• Avoid when: Replacing reusable semantic-model measures that multiple visuals need.
• Suitable data: Relevant recovered tags: visual calculations, running total, calculation
• Typical UX usage: Running sums, moving calculations or visual-specific transformations where appropriate.
• Key configuration / design guidance: Prefer semantic measures for business logic; use visual calculations for genuinely visual-local needs.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Generally available as of May 2026. Logic is stored on the visual and can only reference data available in that visual; do not use it to replace reusable semantic-model business measures.
• Recommended standard configuration: Prefer semantic measures for business logic; use visual calculations for genuinely visual-local needs.
• Possible reusable Figma component: A design-only representation of Visual Calculations may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/transform-model/desktop-visual-calculations-overview

AI & exploration

Decomposition Tree

• Native Power BI: Yes
• Catalog status / standard: Core native / Situational
• Purpose: Interactively break a measure down across dimensions to explore contributors.
• Best for: Root-cause exploration such as Waste → BAF → Product group → Article.
• Avoid when: When a fixed, known hierarchy or explanation is sufficient.
• Suitable data: Analyze measure, Explain-by dimensions
• Typical UX usage: Root-cause exploration such as Waste → BAF → Product group → Article.
• Key configuration / design guidance: Curate explanatory dimensions and pair with exact detail views.
• Interaction capabilities: Expand branches, Choose next dimension, AI split where enabled, Cross-filter, Tooltip
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Exploratory; results depend on fields made available and should not be treated as causal proof.
• Recommended standard configuration: Curate explanatory dimensions and pair with exact detail views.
• Possible reusable Figma component: Decomposition tree representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Decomposition tree representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Decomposition tree
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-decomposition-tree

Key Influencers

• Native Power BI: Yes
• Catalog status / standard: Core native / Use cautiously
• Purpose: Identify factors statistically associated with a selected outcome.
• Best for: Exploratory analysis of likely influencing factors.
• Avoid when: Presenting associations as proven causal explanations.
• Suitable data: Analyze field/measure, Explain-by fields
• Typical UX usage: Exploratory analysis of likely influencing factors.
• Key configuration / design guidance: Label as exploratory insight and validate important findings with domain/data specialists.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Interpretation depends on model/data quality and statistical context.
• Recommended standard configuration: Label as exploratory insight and validate important findings with domain/data specialists.
• Possible reusable Figma component: Key influencers representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Key influencers representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Key influencers
• Recovered note: Treat findings as associations; communicate uncertainty and user control.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-influencers

Smart Narrative

• Native Power BI: Yes
• Catalog status / standard: Core native / Use cautiously
• Purpose: Generate natural-language summaries of report data.
• Best for: Supplementary summary or accessible narrative context after review.
• Avoid when: Replacing primary metrics/charts or publishing unreviewed generated interpretation as business truth.
• Suitable data: Report/visual context
• Typical UX usage: Supplementary summary or accessible narrative context after review.
• Key configuration / design guidance: Treat as supplementary and validate wording for business meaning.
• Interaction capabilities: Dynamic text updates with filters
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Narrative quality depends on model and context.
• Recommended standard configuration: Treat as supplementary and validate wording for business meaning.
• Possible reusable Figma component: Smart narrative representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Smart narrative representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Smart narrative
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-smart-narrative

Anomaly Detection

• Native Power BI: Yes
• Catalog status / standard: Core native / Situational
• Purpose: Detect unexpected deviations in supported line charts.
• Best for: Unexpected peaks/drops where statistical anomaly is the question.
• Avoid when: Known rule-based thresholds that should be implemented directly.
• Suitable data: Date/time, Measure
• Typical UX usage: Unexpected peaks/drops where statistical anomaly is the question.
• Key configuration / design guidance: Use together with business context and explanatory fields.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Statistical anomaly is not the same as business exception.
• Recommended standard configuration: Use together with business context and explanatory fields.
• Possible reusable Figma component: Anomaly detection representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Anomaly detection representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Line chart analytics feature
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-anomaly-detection

Q&A visual

• Native Power BI: Yes, but deprecating
• Catalog status / standard: Deprecating / Do not standardize
• Purpose: Let users ask natural-language questions and generate a visual answer.
• Best for: Existing reports only while migration plans are in place.
• Avoid when: New standardized report experiences.
• Suitable data: Semantic model with Q&A support
• Typical UX usage: Existing reports only while migration plans are in place.
• Key configuration / design guidance: Do not introduce as a new design-system component.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Microsoft schedules Q&A visual deprecation for December 2026.
• Recommended standard configuration: Do not introduce as a new design-system component.
• Possible reusable Figma component: Q&A visual representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Q&A visual representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Q&A visual
• Recovered note: Deprecation scheduled for December 2026.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/natural-language/q-and-a-visual

Maps

Azure Maps

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred for maps
• Purpose: Provide geographic analysis using bubbles, markers, filled areas, heat maps, paths and other layers.
• Best for: Location is itself analytically important: stores, regions, routes, density.
• Avoid when: Using location simply as another category.
• Suitable data: Location or lat/long, Measure, Optional category/size
• Typical UX usage: Location is itself analytically important: stores, regions, routes, density.
• Key configuration / design guidance: Use only when spatial context answers a real question; otherwise prefer ranked bar/table.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted), Zoom/pan, Map layers, Clustering where configured
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Mapping requires valid geographic data and can raise data-location/tenant considerations.
• Recommended standard configuration: Use only when spatial context answers a real question; otherwise prefer ranked bar/table.
• Possible reusable Figma component: Azure Maps representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Azure Maps representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Azure Maps
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-map-visualizations-overview

Basic Map (Bing)

• Native Power BI: Yes, legacy/deprecation direction
• Catalog status / standard: Legacy direction / Migrate / avoid new
• Purpose: Legacy bubble/location mapping.
• Best for: Existing reports that have not yet migrated.
• Avoid when: New standard components.
• Suitable data: Location or lat/long, Measure/size
• Typical UX usage: Existing reports that have not yet migrated.
• Key configuration / design guidance: Prefer Azure Maps for new work.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Microsoft has announced deprecation direction for Bing map visuals; timeline is still being planned. Prefer Azure Maps for new work.
• Recommended standard configuration: Prefer Azure Maps for new work.
• Possible reusable Figma component: Map (Bing) representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Map (Bing) representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Map (Bing)
• Recovered note: Microsoft recommends moving to Azure Maps; Bing map deprecation is planned.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-map-visualizations-overview

Filled Map (Bing)

• Native Power BI: Yes, legacy/deprecation direction
• Catalog status / standard: Legacy direction / Migrate / avoid new
• Purpose: Legacy choropleth mapping of geographic areas.
• Best for: Existing reports pending migration.
• Avoid when: New standard designs.
• Suitable data: Geographic region, Measure
• Typical UX usage: Existing reports pending migration.
• Key configuration / design guidance: Use Azure Maps filled/reference layers instead where supported.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Bing-based map visual. Prefer Azure Maps for new work and plan migration for existing reports.
• Recommended standard configuration: Use Azure Maps filled/reference layers instead where supported.
• Possible reusable Figma component: Filled map (Bing) representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Filled map (Bing) representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Filled map (Bing)
• Recovered note: Prefer Azure Maps for supported regions.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-filled-maps-choropleths

Shape Map

• Native Power BI: Conditional — preview
• Catalog status / standard: Preview / Pilot only
• Purpose: Map custom shapes/boundaries using TopoJSON/GeoJSON-style geographic definitions.
• Best for: Custom nonstandard regions where preview use is acceptable.
• Avoid when: Default production pattern before GA/approval.
• Suitable data: Region/shape key, Measure
• Typical UX usage: Custom nonstandard regions where preview use is acceptable.
• Key configuration / design guidance: Use only for validated custom-boundary requirements.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: Preview capability.
• Recommended standard configuration: Use only for validated custom-boundary requirements.
• Possible reusable Figma component: Shape map representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Shape map representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Shape map
• Recovered note: Preview: functionality and accessibility may change.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/desktop-shape-map

ArcGIS Maps for Power BI

• Native Power BI: Conditional — native integration
• Catalog status / standard: Native integration / Specialist
• Purpose: Provide Esri-powered advanced geographic analysis within Power BI.
• Best for: Specialist geospatial requirements that benefit from ArcGIS capabilities.
• Avoid when: Standard location dashboards that Azure Maps handles adequately.
• Suitable data: Relevant recovered tags: arcgis, map, geospatial
• Typical UX usage: Specialist geospatial requirements that benefit from ArcGIS capabilities.
• Key configuration / design guidance: Treat as an approved specialist dependency, not the default map.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Use descriptive titles/labels and alt text; maintain contrast; never rely on color or hover alone; ensure keyboard/tab-order behavior is testable.
• Known limitations / restrictions: External platform/service dependencies and licensing/capability considerations may apply.
• Recommended standard configuration: Treat as an approved specialist dependency, not the default map.
• Possible reusable Figma component: A design-only representation of ArcGIS Maps for Power BI may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualizations-arcgis

Structure & content

Text Box

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Add titles, headings, explanations and supporting text.
• Best for: Page title, section heading, brief context, definitions.
• Avoid when: Long documentation or recreating application chrome inside the report.
• Suitable data: Optional data-bound text
• Typical UX usage: Page title, section heading, brief context, definitions.
• Key configuration / design guidance: Use a clear hierarchy and consistent typographic tokens.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Decorative objects should be removed from tab order; meaningful objects need readable text/alt text as applicable.
• Known limitations / restrictions: Text should remain concise in analytical interfaces.
• Recommended standard configuration: Use a clear hierarchy and consistent typographic tokens.
• Possible reusable Figma component: Text box representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Text box representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Text box
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-text-box

Shape

• Native Power BI: Yes
• Catalog status / standard: Core native / Situational
• Purpose: Provide lightweight visual structure or act as an action-enabled object.
• Best for: Separators, simple grouping, background regions, occasional navigation.
• Avoid when: Building complex faux components out of many manual shapes.
• Suitable data: No data required
• Typical UX usage: Separators, simple grouping, background regions, occasional navigation.
• Key configuration / design guidance: Prefer whitespace/card grouping; remove purely decorative shapes from keyboard tab order.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Decorative objects should be removed from tab order; meaningful objects need readable text/alt text as applicable.
• Known limitations / restrictions: Decorative shapes can pollute tab order if not managed.
• Recommended standard configuration: Prefer whitespace/card grouping; remove purely decorative shapes from keyboard tab order.
• Possible reusable Figma component: Shape representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Shape representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Shape
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/create-reports/desktop-add-visual-elements

Image

• Native Power BI: Yes
• Catalog status / standard: Core native / Situational
• Purpose: Display contextual/static or supported dynamic imagery.
• Best for: Relevant product/location images, approved branding, explanatory graphics.
• Avoid when: Decoration with no analytical purpose.
• Suitable data: Image source / URL / data-bound field
• Typical UX usage: Relevant product/location images, approved branding, explanatory graphics.
• Key configuration / design guidance: Use alt text for meaningful images and exclude decorative imagery from focus order.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Decorative objects should be removed from tab order; meaningful objects need readable text/alt text as applicable.
• Known limitations / restrictions: Images must remain accessible and performant; external image behavior depends on source/security.
• Recommended standard configuration: Use alt text for meaningful images and exclude decorative imagery from focus order.
• Possible reusable Figma component: Image visual representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Image visual representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Image visual
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/create-reports/desktop-add-visual-elements

Report Theme

• Native Power BI: Yes
• Catalog status / standard: Core native / Preferred
• Purpose: Standardize colors, fonts and visual formatting through theme JSON.
• Best for: Organization-wide design tokens and repeatable defaults.
• Avoid when: Manual per-visual styling as the primary consistency mechanism.
• Suitable data: Relevant recovered tags: theme, tokens, styling, json
• Typical UX usage: Organization-wide design tokens and repeatable defaults.
• Key configuration / design guidance: Treat theme as the Power BI styling foundation aligned with design tokens.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Decorative objects should be removed from tab order; meaningful objects need readable text/alt text as applicable.
• Known limitations / restrictions: Not every property is fully theme-controllable; some settings still require visual-level configuration.
• Recommended standard configuration: Treat theme as the Power BI styling foundation aligned with design tokens.
• Possible reusable Figma component: A design-only representation of Report Theme may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/create-reports/desktop-report-themes

Native integrations

Power Automate visual

• Native Power BI: Conditional — native integration
• Catalog status / standard: Native integration / Specialist
• Purpose: Trigger a Power Automate flow using report selection/filter context.
• Best for: Create issue, start approval, notify owner or other operational workflow.
• Avoid when: Basic reporting interactions or where a report should remain read-only.
• Suitable data: Optional data fields as flow input
• Typical UX usage: Create issue, start approval, notify owner or other operational workflow.
• Key configuration / design guidance: Use only for a validated report-to-action workflow and provide explicit feedback about the action.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Depends on Power Automate environment, permissions, flow ownership and governance.
• Recommended standard configuration: Use only for a validated report-to-action workflow and provide explicit feedback about the action.
• Possible reusable Figma component: Power Automate visual representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Power Automate visual representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Power Automate visual
• Recovered note: Not supported for embedded analytics or export scenarios; permissions/licensing matter.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/create-reports/power-bi-automate-visual

Power Apps visual

• Native Power BI: Conditional — native integration
• Catalog status / standard: Native integration / Specialist
• Purpose: Embed a Power App and pass report context into a transactional experience.
• Best for: Edit/write-back/task workflows that Power BI alone cannot support cleanly.
• Avoid when: Simple navigation or read-only analysis.
• Suitable data: Data fields passed to Power Apps
• Typical UX usage: Edit/write-back/task workflows that Power BI alone cannot support cleanly.
• Key configuration / design guidance: Keep reporting and transaction responsibilities clear.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Separate Power Apps lifecycle, permissions, environment and performance considerations.
• Recommended standard configuration: Keep reporting and transaction responsibilities clear.
• Possible reusable Figma component: Power Apps visual representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Power Apps visual representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Power Apps visual
• Recovered documentation link: https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/powerapps-custom-visual

Paginated Report visual

• Native Power BI: Conditional — native integration
• Catalog status / standard: Native integration / Specialist
• Purpose: Embed pixel-precise, print-oriented paginated output inside a Power BI report.
• Best for: Print-ready documents and very detailed multi-page tables.
• Avoid when: Normal interactive analytics.
• Suitable data: Paginated report
• Typical UX usage: Print-ready documents and very detailed multi-page tables.
• Key configuration / design guidance: Use when precise pagination/printing is a requirement, not simply because a table is long.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Different authoring model and interaction expectations from standard Power BI visuals.
• Recommended standard configuration: Use when precise pagination/printing is a requirement, not simply because a table is long.
• Possible reusable Figma component: Paginated report visual representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Paginated report visual representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Paginated report visual
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/paginated-reports/paginated-report-visual-power-bi

R visual

• Native Power BI: Conditional — native integration
• Catalog status / standard: Native integration / Specialist
• Purpose: Render a statistical/custom visual using R.
• Best for: Specialist analysis not achievable with approved native visuals.
• Avoid when: Standard reporting components.
• Suitable data: Fields passed to R script
• Typical UX usage: Specialist analysis not achievable with approved native visuals.
• Key configuration / design guidance: Require technical justification and support ownership.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Runtime, package, service and interaction limitations; R-generated image cannot act like a fully native cross-filter source.
• Recommended standard configuration: Require technical justification and support ownership.
• Possible reusable Figma component: R visual representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: R visual representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI R visual
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/create-reports/desktop-r-visuals

Python visual

• Native Power BI: Conditional — native integration
• Catalog status / standard: Native integration / Specialist
• Purpose: Render plots produced with Python.
• Best for: Specialist analytical/plotting needs.
• Avoid when: Standard reusable enterprise visuals.
• Suitable data: Fields passed to Python script
• Typical UX usage: Specialist analytical/plotting needs.
• Key configuration / design guidance: Use only with technical justification and documented support model.
• Interaction capabilities: Cross-filter, Cross-highlight, Tooltip, Focus mode, Export data (where permitted)
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Runtime/package/data-size/service limitations apply and behavior differs from native interactive visuals.
• Recommended standard configuration: Use only with technical justification and documented support model.
• Possible reusable Figma component: Python visual representation (verify kit version)
• Possible Nudge BI / Power UI equivalent: Nudge: Python visual representation (verify kit version) | Power UI: Standardized styling/configuration pattern (organization-specific)
• Native implementation mapping: Power BI Python visual
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/connect-data/service-python-packages-support

Nudge BI

Nudge BI — KPI Card

• Native Power BI: No — Nudge BI
• Catalog status / standard: Nudge BI / Preferred
• Purpose: Nudge-style KPI composition for a primary value, comparisons and concise supporting context.
• Best for: Top-level operational KPIs and executive summaries.
• Avoid when: Large metric inventories or detailed record comparison.
• Suitable data: Relevant recovered tags: nudge bi, kpi, card, ui kit
• Typical UX usage: Top-level operational KPIs and executive summaries.
• Key configuration / design guidance: Use the Nudge pattern to prototype hierarchy and spacing, then implement with the native Card before introducing extra visuals.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Nudge BI is a Figma/template design layer, not a separate Power BI visual. Public Nudge pages do not expose the complete licensed internal component index.
• Recommended standard configuration: Use the Nudge pattern to prototype hierarchy and spacing, then implement with the native Card before introducing extra visuals.
• Possible reusable Figma component: A design-only representation of Nudge BI — KPI Card may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://www.nudgebi.com/power-bi-ui-kit

Nudge BI — KPI + mini trend

• Native Power BI: No — Nudge BI
• Catalog status / standard: Nudge BI / Preferred
• Purpose: KPI composition with compact directional trend context.
• Best for: Current result plus recent movement where trend is supporting information.
• Avoid when: When time-series analysis is the primary task.
• Suitable data: Relevant recovered tags: nudge bi, mini trend, kpi
• Typical UX usage: Current result plus recent movement where trend is supporting information.
• Key configuration / design guidance: Implement as Card + small Line chart, or use native Table/Matrix sparklines only where that pattern fits.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: A mini trend outside a Table/Matrix is not a native standalone Sparkline visual; it is normally composed from native visuals.
• Recommended standard configuration: Implement as Card + small Line chart, or use native Table/Matrix sparklines only where that pattern fits.
• Possible reusable Figma component: A design-only representation of Nudge BI — KPI + mini trend may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://www.nudgebi.com/showcase

Nudge BI — KPI group / summary row

• Native Power BI: No — Nudge BI
• Catalog status / standard: Nudge BI / Preferred
• Purpose: Consistent row/grid of related KPI blocks.
• Best for: Two to four top-level metrics with comparable scanning priority.
• Avoid when: Pages where every metric is promoted to a KPI.
• Suitable data: Relevant recovered tags: nudge bi, summary row, kpi
• Typical UX usage: Two to four top-level metrics with comparable scanning priority.
• Key configuration / design guidance: Use the minimum native Card count necessary and preserve one hierarchy for label, value and deltas.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: A visual tile in Figma does not necessarily require one separate Power BI visual.
• Recommended standard configuration: Use the minimum native Card count necessary and preserve one hierarchy for label, value and deltas.
• Possible reusable Figma component: A design-only representation of Nudge BI — KPI group / summary row may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://www.nudgebi.com/power-bi-templates

Nudge BI — Trend panel

• Native Power BI: No — Nudge BI
• Catalog status / standard: Nudge BI / Preferred
• Purpose: Card/panel shell containing time-series analysis and optional references.
• Best for: Actual vs previous year, target, norm or forecast over time.
• Avoid when: Unordered category comparisons.
• Suitable data: Relevant recovered tags: nudge bi, trend, line, panel
• Typical UX usage: Actual vs previous year, target, norm or forecast over time.
• Key configuration / design guidance: Use native Line chart plus Analytics/reference lines and concise title/context.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: The panel/container is presentation; the analytical behavior remains native Power BI.
• Recommended standard configuration: Use native Line chart plus Analytics/reference lines and concise title/context.
• Possible reusable Figma component: A design-only representation of Nudge BI — Trend panel may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://www.nudgebi.com/showcase

Nudge BI — Ranking panel

• Native Power BI: No — Nudge BI
• Catalog status / standard: Nudge BI / Preferred
• Purpose: Styled comparison module for ranked categories.
• Best for: Top/bottom departments, stores, products or regions.
• Avoid when: Continuous time-series analysis.
• Suitable data: Relevant recovered tags: nudge bi, ranking, bar
• Typical UX usage: Top/bottom departments, stores, products or regions.
• Key configuration / design guidance: Implement with native Clustered bar chart and intentional Sorting.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Decorative container elements must not obstruct sorting, selection, visual headers or tooltips.
• Recommended standard configuration: Implement with native Clustered bar chart and intentional Sorting.
• Possible reusable Figma component: A design-only representation of Nudge BI — Ranking panel may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://www.nudgebi.com/showcase

Nudge BI — Composition panel

• Native Power BI: No — Nudge BI
• Catalog status / standard: Nudge BI / Situational
• Purpose: Reusable part-to-whole module.
• Best for: Simple mix/share questions with a small number of components.
• Avoid when: Precise comparison or many segments.
• Suitable data: Relevant recovered tags: nudge bi, composition, donut, stacked
• Typical UX usage: Simple mix/share questions with a small number of components.
• Key configuration / design guidance: Prefer 100% stacked bar for comparison; use Donut only for genuinely simple part-to-whole cases.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Nudge styling does not remove the perceptual limitations of pie/donut charts.
• Recommended standard configuration: Prefer 100% stacked bar for comparison; use Donut only for genuinely simple part-to-whole cases.
• Possible reusable Figma component: A design-only representation of Nudge BI — Composition panel may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://www.nudgebi.com/showcase

Nudge BI — Variance / bridge panel

• Native Power BI: No — Nudge BI
• Catalog status / standard: Nudge BI / Preferred
• Purpose: Styled contribution analysis from a starting value to an ending result.
• Best for: Budget-to-actual and target-to-result explanations.
• Avoid when: Simple ranking or unrelated sequential data.
• Suitable data: Relevant recovered tags: nudge bi, waterfall, variance
• Typical UX usage: Budget-to-actual and target-to-result explanations.
• Key configuration / design guidance: Use native Waterfall and keep the explanatory shell lightweight.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Too many bridge steps remain hard to interpret regardless of styling.
• Recommended standard configuration: Use native Waterfall and keep the explanatory shell lightweight.
• Possible reusable Figma component: A design-only representation of Nudge BI — Variance / bridge panel may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://www.nudgebi.com/power-bi-templates

Nudge BI — Table panel

• Native Power BI: No — Nudge BI
• Catalog status / standard: Nudge BI / Preferred
• Purpose: Styled exact-value detail module with optional title/actions.
• Best for: Operational detail, quantitative comparison, exportable records.
• Avoid when: Hierarchy requiring expand/collapse.
• Suitable data: Relevant recovered tags: nudge bi, table, detail
• Typical UX usage: Operational detail, quantitative comparison, exportable records.
• Key configuration / design guidance: Use native Table + Conditional Formatting + curated Visual Header.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Avoid rebuilding the panel with many overlay shapes that interfere with accessibility or native interaction.
• Recommended standard configuration: Use native Table + Conditional Formatting + curated Visual Header.
• Possible reusable Figma component: A design-only representation of Nudge BI — Table panel may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://www.nudgebi.com/power-bi-templates

Nudge BI — Matrix / hierarchy panel

• Native Power BI: No — Nudge BI
• Catalog status / standard: Nudge BI / Preferred
• Purpose: Styled hierarchical table pattern.
• Best for: BAF → Product group → Article or comparable multi-level structures.
• Avoid when: Flat detail lists.
• Suitable data: Relevant recovered tags: nudge bi, matrix, hierarchy
• Typical UX usage: BAF → Product group → Article or comparable multi-level structures.
• Key configuration / design guidance: Prototype the shell in Nudge; implement hierarchy through native Matrix rather than fake indentation.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Native Matrix subtotal, stepped layout and drill behavior determine feasibility.
• Recommended standard configuration: Prototype the shell in Nudge; implement hierarchy through native Matrix rather than fake indentation.
• Possible reusable Figma component: A design-only representation of Nudge BI — Matrix / hierarchy panel may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://www.nudgebi.com/power-bi-templates

Nudge BI — Filter bar

• Native Power BI: No — Nudge BI
• Catalog status / standard: Nudge BI / Preferred
• Purpose: Consistent top-of-page filter composition.
• Best for: Frequently used context such as period, location, budget and channel.
• Avoid when: Showing every model filter on the canvas.
• Suitable data: Relevant recovered tags: nudge bi, filters, slicers, filter bar
• Typical UX usage: Frequently used context such as period, location, budget and channel.
• Key configuration / design guidance: Map each control to the simplest native slicer and move advanced/rare filters to the Filters pane.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: A Nudge filter bar is a composition of individual native slicers; synchronization and selection rules still require report configuration.
• Recommended standard configuration: Map each control to the simplest native slicer and move advanced/rare filters to the Filters pane.
• Possible reusable Figma component: A design-only representation of Nudge BI — Filter bar may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://www.nudgebi.com/power-bi-ui-kit

Nudge BI — Segmented metric switch

• Native Power BI: No — Nudge BI
• Catalog status / standard: Nudge BI / Preferred
• Purpose: Button-like switch for changing measure or dimension while retaining the same analysis layout.
• Best for: Sales | Margin | Waste or Week | Period | Year.
• Avoid when: Switching between fundamentally different page structures.
• Suitable data: Relevant recovered tags: nudge bi, segmented, field parameter, switch
• Typical UX usage: Sales | Margin | Waste or Week | Period | Year.
• Key configuration / design guidance: Prefer Field Parameters over duplicated hidden visuals or bookmark hacks.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: The Nudge control is a design pattern; native implementation normally uses Button Slicer + Field Parameter.
• Recommended standard configuration: Prefer Field Parameters over duplicated hidden visuals or bookmark hacks.
• Possible reusable Figma component: A design-only representation of Nudge BI — Segmented metric switch may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://www.nudgebi.com/power-bi-ui-kit

Nudge BI — Page tabs / navigation

• Native Power BI: No — Nudge BI
• Catalog status / standard: Nudge BI / Preferred
• Purpose: Styled navigation for report pages or controlled report states.
• Best for: Overview, Trend, Details and other stable report sections.
• Avoid when: Manual tab sets that must be maintained whenever pages change.
• Suitable data: Relevant recovered tags: nudge bi, navigation, tabs
• Typical UX usage: Overview, Trend, Details and other stable report sections.
• Key configuration / design guidance: Use Page Navigator for pages and Bookmark Navigator for view states.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Appearance may be Nudge-styled, but navigation behavior should remain native where possible.
• Recommended standard configuration: Use Page Navigator for pages and Bookmark Navigator for view states.
• Possible reusable Figma component: A design-only representation of Nudge BI — Page tabs / navigation may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://www.nudgebi.com/power-bi-ui-kit

Nudge BI — Tooltip detail card

• Native Power BI: No — Nudge BI
• Catalog status / standard: Nudge BI / Situational
• Purpose: Rich compact context card shown from a data point.
• Best for: Supplementary values or a mini trend that helps interpret the hovered point.
• Avoid when: Interactive content or essential information.
• Suitable data: Relevant recovered tags: nudge bi, tooltip, detail
• Typical UX usage: Supplementary values or a mini trend that helps interpret the hovered point.
• Key configuration / design guidance: Use Report Page Tooltip for supplementary context; use Drillthrough for interactive detail.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Power BI report-page tooltips are not interactive and have accessibility/touch discoverability limitations.
• Recommended standard configuration: Use Report Page Tooltip for supplementary context; use Drillthrough for interactive detail.
• Possible reusable Figma component: A design-only representation of Nudge BI — Tooltip detail card may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://www.nudgebi.com/power-bi-ui-kit

Nudge BI — Insight / callout card

• Native Power BI: No — Nudge BI
• Catalog status / standard: Nudge BI / Situational
• Purpose: Compact narrative or exception callout around an important finding.
• Best for: Explain a key variance, threshold breach or analytical interpretation.
• Avoid when: Replacing the underlying data evidence.
• Suitable data: Relevant recovered tags: nudge bi, insight, callout
• Typical UX usage: Explain a key variance, threshold breach or analytical interpretation.
• Key configuration / design guidance: Prefer concise authored/dynamic text + native Card/Shape; use Smart Narrative only when generated narrative is validated.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Authored insight text is not itself a data visual. Smart Narrative is a separate native option with its own limitations.
• Recommended standard configuration: Prefer concise authored/dynamic text + native Card/Shape; use Smart Narrative only when generated narrative is validated.
• Possible reusable Figma component: A design-only representation of Nudge BI — Insight / callout card may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://www.nudgebi.com/showcase

Nudge BI — Icon action / status

• Native Power BI: No — Nudge BI
• Catalog status / standard: Nudge BI / Situational
• Purpose: Use Nudge's icon library for actions, status cues and supporting semantics.
• Best for: Back, info, filter, positive/negative, export or navigation cues.
• Avoid when: Icons without labels where meaning is ambiguous.
• Suitable data: Relevant recovered tags: nudge bi, icons, status, action
• Typical UX usage: Back, info, filter, positive/negative, export or navigation cues.
• Key configuration / design guidance: Never rely on icon/color alone for critical meaning. Maintain alt text and tab-order rules.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: The Nudge icon library is an asset source; actual implementation may be a native Button, Image, conditional icon or Shape.
• Recommended standard configuration: Never rely on icon/color alone for critical meaning. Maintain alt text and tab-order rules.
• Possible reusable Figma component: A design-only representation of Nudge BI — Icon action / status may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://www.nudgebi.com/icon-library

Power UI

Power UI — Theme foundation

• Native Power BI: No — Power UI
• Catalog status / standard: Power UI / Recommended
• Purpose: Centralize Power BI theme foundations using reusable tokens and theme configuration.
• Best for: Enterprise-wide Power BI styling based on the company design system.
• Avoid when: Treating Power UI as a new runtime or a way to bypass native Power BI limitations.
• Suitable data: Relevant recovered tags: power ui, theme, tokens
• Typical UX usage: Enterprise-wide Power BI styling based on the company design system.
• Key configuration / design guidance: Map approved company semantic tokens into Power UI and export standard theme JSON.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Power UI exports/edits standard Power BI theme configuration; it does not add unsupported Power BI behavior.
• Recommended standard configuration: Map approved company semantic tokens into Power UI and export standard theme JSON.
• Possible reusable Figma component: A design-only representation of Power UI — Theme foundation may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://www.powerui.com/docs/design-system

Power UI — Semantic color tokens

• Native Power BI: No — Power UI
• Catalog status / standard: Power UI / Recommended
• Purpose: Use semantic text, surface, brand, success, warning, error and border tokens to keep theme colors consistent.
• Best for: Light/dark theme generation and centrally controlled color relationships.
• Avoid when: Copying raw hex values independently into each visual.
• Suitable data: Relevant recovered tags: power ui, semantic tokens, color
• Typical UX usage: Light/dark theme generation and centrally controlled color relationships.
• Key configuration / design guidance: Company token → mapped Power UI semantic token → Power BI theme value.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Token resolution occurs in Power UI; exported Power BI theme contains concrete theme values.
• Recommended standard configuration: Company token → mapped Power UI semantic token → Power BI theme value.
• Possible reusable Figma component: A design-only representation of Power UI — Semantic color tokens may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://www.powerui.com/docs/design-system

Power UI — Typography

• Native Power BI: No — Power UI
• Catalog status / standard: Power UI / Recommended
• Purpose: Standardize supported Power BI text classes and visual typography.
• Best for: Company typography mapping for titles, labels, cards and supporting text.
• Avoid when: Assuming every Figma typography style maps one-to-one to every Power BI text property.
• Suitable data: Relevant recovered tags: power ui, typography, text classes
• Typical UX usage: Company typography mapping for titles, labels, cards and supporting text.
• Key configuration / design guidance: Use approved font family/fallback and map hierarchy to Power BI text classes / visual styles.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Power BI text classes and per-visual properties determine actual coverage.
• Recommended standard configuration: Use approved font family/fallback and map hierarchy to Power BI text classes / visual styles.
• Possible reusable Figma component: A design-only representation of Power UI — Typography may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://www.powerui.com/docs/typography

Power UI — Data palette

• Native Power BI: No — Power UI
• Catalog status / standard: Power UI / Recommended
• Purpose: Manage repeatable chart data-color palettes aligned with brand and accessibility.
• Best for: Series/category colors used consistently across reports.
• Avoid when: Using brand colors for every data series regardless of semantic meaning.
• Suitable data: Relevant recovered tags: power ui, palette, data colors
• Typical UX usage: Series/category colors used consistently across reports.
• Key configuration / design guidance: Separate brand, data-series, semantic status and highlight palettes.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Power BI cycles through dataColors; conditional rules remain visual/model logic, not theme rules.
• Recommended standard configuration: Separate brand, data-series, semantic status and highlight palettes.
• Possible reusable Figma component: A design-only representation of Power UI — Data palette may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://www.powerui.com/docs/brand-palettes

Power UI — Style presets

• Native Power BI: No — Power UI
• Catalog status / standard: Power UI / Recommended
• Purpose: Create named formatting variants for supported visual types using Power BI theme style presets.
• Best for: Subtle vs emphasis Card, standard vs comparison chart, standard Table variants.
• Avoid when: Creating dozens of near-identical presets without clear use cases.
• Suitable data: Relevant recovered tags: power ui, style presets, visual styles
• Typical UX usage: Subtle vs emphasis Card, standard vs comparison chart, standard Table variants.
• Key configuration / design guidance: Define a small approved preset set and document when each applies.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Presets are specific to visual types and limited to properties exposed by Power BI theme schema.
• Recommended standard configuration: Define a small approved preset set and document when each applies.
• Possible reusable Figma component: A design-only representation of Power UI — Style presets may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://www.powerui.com/docs/style-presets

Power UI — Live theme preview

• Native Power BI: No — Power UI
• Catalog status / standard: Power UI / Recommended
• Purpose: Preview theme changes against an interactive Power BI sample report.
• Best for: Theme validation across multiple native visual types before export.
• Avoid when: Using preview as a substitute for QA on the real report/data.
• Suitable data: Relevant recovered tags: power ui, preview, theme
• Typical UX usage: Theme validation across multiple native visual types before export.
• Key configuration / design guidance: Use preview for theme development, then test the actual report in Desktop/Service/Embedded.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Production report-specific edge cases still require validation.
• Recommended standard configuration: Use preview for theme development, then test the actual report in Desktop/Service/Embedded.
• Possible reusable Figma component: A design-only representation of Power UI — Live theme preview may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://www.powerui.com/docs/real-time-preview

Power UI — Theme import/export

• Native Power BI: No — Power UI
• Catalog status / standard: Power UI / Recommended
• Purpose: Import existing Power BI theme JSON and export Power UI themes as standard Power BI JSON.
• Best for: Bringing an existing corporate theme under governed management or generating deployment-ready theme assets.
• Avoid when: Assuming an imported static theme automatically gains token relationships.
• Suitable data: Relevant recovered tags: power ui, import, export, json
• Typical UX usage: Bringing an existing corporate theme under governed management or generating deployment-ready theme assets.
• Key configuration / design guidance: Version theme JSON and validate against the current Power BI schema.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Imported themes start from static values; advanced Power UI token/preset relationships may need to be configured after import.
• Recommended standard configuration: Version theme JSON and validate against the current Power BI schema.
• Possible reusable Figma component: A design-only representation of Power UI — Theme import/export may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://www.powerui.com/docs/import-export

Power UI — PBIP Desktop integration

• Native Power BI: No — Power UI
• Catalog status / standard: Power UI / Situational
• Purpose: Apply a Power UI theme directly into a Power BI Project (.pbip) workflow.
• Best for: Teams using PBIP, Git and supported Windows Power BI Desktop environments.
• Avoid when: Making it mandatory when the team uses PBIX-only workflows or unsupported environments.
• Suitable data: Relevant recovered tags: power ui, pbip, desktop, git
• Typical UX usage: Teams using PBIP, Git and supported Windows Power BI Desktop environments.
• Key configuration / design guidance: Treat this as an accelerator. Keep versioned theme JSON/PBIP starter as the durable baseline.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Current Power UI Desktop docs require Windows 10/11, PBIP, and recent Power BI Desktop for instant reload; PBIX cannot be modified externally.
• Recommended standard configuration: Treat this as an accelerator. Keep versioned theme JSON/PBIP starter as the durable baseline.
• Possible reusable Figma component: A design-only representation of Power UI — PBIP Desktop integration may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://www.powerui.com/docs/desktop

Power UI — Card style pattern

• Native Power BI: No — Power UI
• Catalog status / standard: Power UI / Recommended
• Purpose: Standardized theme/preset treatment for Cards.
• Best for: Reusable KPI hierarchy across reports.
• Avoid when: Creating custom visual behavior.
• Suitable data: Relevant recovered tags: power ui, card, kpi
• Typical UX usage: Reusable KPI hierarchy across reports.
• Key configuration / design guidance: Use native Card and theme/preset styling; keep KPI composition rules in UX guidance.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Only native Card formatting exposed by Power BI can be standardized.
• Recommended standard configuration: Use native Card and theme/preset styling; keep KPI composition rules in UX guidance.
• Possible reusable Figma component: A design-only representation of Power UI — Card style pattern may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://www.powerui.com/docs/style-presets

Power UI — Table/Matrix style pattern

• Native Power BI: No — Power UI
• Catalog status / standard: Power UI / Recommended
• Purpose: Standardize supported table and matrix typography, grids, headers, totals and effects.
• Best for: Enterprise detail views.
• Avoid when: Trying to theme business-specific conditional-formatting logic centrally.
• Suitable data: Relevant recovered tags: power ui, table, matrix
• Typical UX usage: Enterprise detail views.
• Key configuration / design guidance: Theme static styling centrally; specify business rules per report/component.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Conditional formatting rules are configured on visuals and cannot be authored as theme rules.
• Recommended standard configuration: Theme static styling centrally; specify business rules per report/component.
• Possible reusable Figma component: A design-only representation of Power UI — Table/Matrix style pattern may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://www.powerui.com/docs/style-presets

Design System

Company semantic color tokens

• Native Power BI: No — Design System
• Catalog status / standard: Design System / Recommended
• Purpose: Canonical semantic color decisions for brand, surfaces, text, status and data roles.
• Best for: All report design and theme decisions.
• Avoid when: Local report-specific duplicates of centrally managed colors.
• Suitable data: Relevant recovered tags: design system, tokens, color
• Typical UX usage: All report design and theme decisions.
• Key configuration / design guidance: Design System/token repository remains source of truth; map instead of fork.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Only map tokens into Power BI where the platform exposes an equivalent theme/formatting property.
• Recommended standard configuration: Design System/token repository remains source of truth; map instead of fork.
• Possible reusable Figma component: A design-only representation of Company semantic color tokens may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: #tokens-themes

Company typography tokens

• Native Power BI: No — Design System
• Catalog status / standard: Design System / Recommended
• Purpose: Canonical font families, weights and hierarchy.
• Best for: Page titles, visual titles, labels, data values and helper text.
• Avoid when: Inventing a separate Power BI typography scale without need.
• Suitable data: Relevant recovered tags: design system, typography
• Typical UX usage: Page titles, visual titles, labels, data values and helper text.
• Key configuration / design guidance: Specify approved fallback behavior and map only supported hierarchy.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Power BI font availability and text-class coverage can require fallback/mapping.
• Recommended standard configuration: Specify approved fallback behavior and map only supported hierarchy.
• Possible reusable Figma component: A design-only representation of Company typography tokens may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: #tokens-themes

Company spacing & layout tokens

• Native Power BI: No — Design System
• Catalog status / standard: Design System / Recommended
• Purpose: Canonical spacing rhythm and grouping principles.
• Best for: Figma layout, report page spacing and supported theme padding.
• Avoid when: Assuming Power BI provides responsive CSS spacing tokens.
• Suitable data: Relevant recovered tags: design system, spacing, layout
• Typical UX usage: Figma layout, report page spacing and supported theme padding.
• Key configuration / design guidance: Use tokens in Figma and document manual Power BI equivalents.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Power BI page layout is manually positioned; theme coverage for spacing/padding is partial.
• Recommended standard configuration: Use tokens in Figma and document manual Power BI equivalents.
• Possible reusable Figma component: A design-only representation of Company spacing & layout tokens may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: #layout

Company shape/effect tokens

• Native Power BI: No — Design System
• Catalog status / standard: Design System / Situational
• Purpose: Canonical borders, radius and shadows where supported.
• Best for: Containers, visual outlines and hierarchy.
• Avoid when: Heavy card chrome or decoration around every visual.
• Suitable data: Relevant recovered tags: design system, radius, border, shadow
• Typical UX usage: Containers, visual outlines and hierarchy.
• Key configuration / design guidance: Prefer whitespace/grouping first; use effects only where they improve hierarchy.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Property support varies by visual and theme schema.
• Recommended standard configuration: Prefer whitespace/grouping first; use effects only where they improve hierarchy.
• Possible reusable Figma component: A design-only representation of Company shape/effect tokens may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: #tokens-themes

Custom Visual

Bullet chart

• Native Power BI: No — Custom Visual
• Catalog status / standard: Custom Visual / Use with caution
• Purpose: Compare actual to target in a compact bar-based form.
• Best for: Use only when the analytical requirement cannot be adequately met with approved native Power BI patterns.
• Avoid when: Using custom visuals for cosmetic differentiation when native Power BI can solve the user question.
• Suitable data: Relevant recovered tags: custom visual, comparison, target
• Typical UX usage: Use only when the analytical requirement cannot be adequately met with approved native Power BI patterns.
• Key configuration / design guidance: Document approval, accessibility, performance, export, certification and support ownership.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Use a native bar + target/reference line when sufficient; otherwise use an approved custom visual such as a certified AppSource visual or Deneb.
• Recommended standard configuration: Document approval, accessibility, performance, export, certification and support ownership.
• Possible reusable Figma component: A design-only representation of Bullet chart may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/developer/visuals/power-bi-custom-visuals

Sankey diagram

• Native Power BI: No — Custom Visual
• Catalog status / standard: Custom Visual / Use with caution
• Purpose: Show flows between nodes/categories.
• Best for: Use only when the analytical requirement cannot be adequately met with approved native Power BI patterns.
• Avoid when: Using custom visuals for cosmetic differentiation when native Power BI can solve the user question.
• Suitable data: Relevant recovered tags: custom visual, flow, network
• Typical UX usage: Use only when the analytical requirement cannot be adequately met with approved native Power BI patterns.
• Key configuration / design guidance: Document approval, accessibility, performance, export, certification and support ownership.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Custom visual required; validate whether a simpler stacked/bar flow summary would be clearer.
• Recommended standard configuration: Document approval, accessibility, performance, export, certification and support ownership.
• Possible reusable Figma component: A design-only representation of Sankey diagram may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/developer/visuals/power-bi-custom-visuals

Gantt chart

• Native Power BI: No — Custom Visual
• Catalog status / standard: Custom Visual / Use with caution
• Purpose: Show tasks against a time schedule.
• Best for: Use only when the analytical requirement cannot be adequately met with approved native Power BI patterns.
• Avoid when: Using custom visuals for cosmetic differentiation when native Power BI can solve the user question.
• Suitable data: Relevant recovered tags: custom visual, schedule, project
• Typical UX usage: Use only when the analytical requirement cannot be adequately met with approved native Power BI patterns.
• Key configuration / design guidance: Document approval, accessibility, performance, export, certification and support ownership.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Custom visual required; Power BI does not provide a standard built-in Gantt visual.
• Recommended standard configuration: Document approval, accessibility, performance, export, certification and support ownership.
• Possible reusable Figma component: A design-only representation of Gantt chart may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/developer/visuals/power-bi-custom-visuals

Box-and-whisker plot

• Native Power BI: No — Custom Visual
• Catalog status / standard: Custom Visual / Use with caution
• Purpose: Show distribution, quartiles and outliers.
• Best for: Use only when the analytical requirement cannot be adequately met with approved native Power BI patterns.
• Avoid when: Using custom visuals for cosmetic differentiation when native Power BI can solve the user question.
• Suitable data: Relevant recovered tags: custom visual, distribution, statistics
• Typical UX usage: Use only when the analytical requirement cannot be adequately met with approved native Power BI patterns.
• Key configuration / design guidance: Document approval, accessibility, performance, export, certification and support ownership.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Custom visual or specialist implementation required.
• Recommended standard configuration: Document approval, accessibility, performance, export, certification and support ownership.
• Possible reusable Figma component: A design-only representation of Box-and-whisker plot may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/developer/visuals/power-bi-custom-visuals

Violin plot

• Native Power BI: No — Custom Visual
• Catalog status / standard: Custom Visual / Use with caution
• Purpose: Show distribution density and spread.
• Best for: Use only when the analytical requirement cannot be adequately met with approved native Power BI patterns.
• Avoid when: Using custom visuals for cosmetic differentiation when native Power BI can solve the user question.
• Suitable data: Relevant recovered tags: custom visual, distribution, density
• Typical UX usage: Use only when the analytical requirement cannot be adequately met with approved native Power BI patterns.
• Key configuration / design guidance: Document approval, accessibility, performance, export, certification and support ownership.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Custom/specialist implementation required.
• Recommended standard configuration: Document approval, accessibility, performance, export, certification and support ownership.
• Possible reusable Figma component: A design-only representation of Violin plot may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/developer/visuals/power-bi-custom-visuals

Radar / spider chart

• Native Power BI: No — Custom Visual
• Catalog status / standard: Custom Visual / Use with caution
• Purpose: Compare multivariate profiles around radial axes.
• Best for: Use only when the analytical requirement cannot be adequately met with approved native Power BI patterns.
• Avoid when: Using custom visuals for cosmetic differentiation when native Power BI can solve the user question.
• Suitable data: Relevant recovered tags: custom visual, multivariate, radar
• Typical UX usage: Use only when the analytical requirement cannot be adequately met with approved native Power BI patterns.
• Key configuration / design guidance: Document approval, accessibility, performance, export, certification and support ownership.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Custom visual required; bars/small multiples are usually easier to compare.
• Recommended standard configuration: Document approval, accessibility, performance, export, certification and support ownership.
• Possible reusable Figma component: A design-only representation of Radar / spider chart may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/developer/visuals/power-bi-custom-visuals

Dumbbell / lollipop chart

• Native Power BI: No — Custom Visual
• Catalog status / standard: Custom Visual / Use with caution
• Purpose: Show compact differences between points/categories.
• Best for: Use only when the analytical requirement cannot be adequately met with approved native Power BI patterns.
• Avoid when: Using custom visuals for cosmetic differentiation when native Power BI can solve the user question.
• Suitable data: Relevant recovered tags: custom visual, comparison, delta
• Typical UX usage: Use only when the analytical requirement cannot be adequately met with approved native Power BI patterns.
• Key configuration / design guidance: Document approval, accessibility, performance, export, certification and support ownership.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: No dedicated native visual; approximate where feasible or use approved custom implementation.
• Recommended standard configuration: Document approval, accessibility, performance, export, certification and support ownership.
• Possible reusable Figma component: A design-only representation of Dumbbell / lollipop chart may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/developer/visuals/power-bi-custom-visuals

Deneb visual

• Native Power BI: No — Custom Visual
• Catalog status / standard: Custom Visual / Use with caution
• Purpose: Create custom Vega/Vega-Lite visual specifications inside Power BI.
• Best for: Use only when the analytical requirement cannot be adequately met with approved native Power BI patterns.
• Avoid when: Using custom visuals for cosmetic differentiation when native Power BI can solve the user question.
• Suitable data: Depends on specification
• Typical UX usage: Use only when the analytical requirement cannot be adequately met with approved native Power BI patterns.
• Key configuration / design guidance: Document approval, accessibility, performance, export, certification and support ownership.
• Interaction capabilities: Depends on spec and visual configuration
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Third-party custom visual; powerful but introduces an additional authoring/maintenance layer.
• Recommended standard configuration: Document approval, accessibility, performance, export, certification and support ownership.
• Possible reusable Figma component: Design-only representation; verify against Deneb implementation
• Possible Nudge BI / Power UI equivalent: Nudge: Design-only representation; verify against Deneb implementation | Power UI: Only if approved as an organization pattern
• Native implementation mapping: Custom visual (Deneb)
• Recovered note: Use only after native options are exhausted and governance/performance/accessibility are reviewed.
• Recovered documentation link: https://learn.microsoft.com/en-us/power-bi/developer/visuals/power-bi-custom-visuals

Design Pattern

Pattern — Overview / dashboard

• Native Power BI: No — Design Pattern
• Catalog status / standard: Design Pattern / Recommended
• Purpose: What is happening and where should I look?
• Best for: Filters → 2–4 Cards → primary trend/comparison → exceptions → detail Table/Matrix
• Avoid when: Do not apply mechanically when the user question or data structure differs.
• Suitable data: Relevant recovered tags: design pattern, pattern, overview / dashboard
• Typical UX usage: Filters → 2–4 Cards → primary trend/comparison → exceptions → detail Table/Matrix
• Key configuration / design guidance: Keep the overview decisive. Do not place every metric on the first page.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Keep the overview decisive. Do not place every metric on the first page.
• Recommended standard configuration: Keep the overview decisive. Do not place every metric on the first page.
• Possible reusable Figma component: A design-only representation of Pattern — Overview / dashboard may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: #templates

Pattern — KPI summary

• Native Power BI: No — Design Pattern
• Catalog status / standard: Design Pattern / Recommended
• Purpose: What is the current result and how does it compare?
• Best for: Card → actual → delta vs target → optional delta vs previous period
• Avoid when: Do not apply mechanically when the user question or data structure differs.
• Suitable data: Relevant recovered tags: design pattern, pattern, kpi summary
• Typical UX usage: Card → actual → delta vs target → optional delta vs previous period
• Key configuration / design guidance: Use a few high-priority KPIs and consistent number formatting.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Use a few high-priority KPIs and consistent number formatting.
• Recommended standard configuration: Use a few high-priority KPIs and consistent number formatting.
• Possible reusable Figma component: A design-only representation of Pattern — KPI summary may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: #templates

Pattern — Trend explorer

• Native Power BI: No — Design Pattern
• Catalog status / standard: Design Pattern / Recommended
• Purpose: How is the metric developing?
• Best for: Field Parameter / Button Slicer → Line chart → optional target/reference → small multiples or detail table
• Avoid when: Do not apply mechanically when the user question or data structure differs.
• Suitable data: Relevant recovered tags: design pattern, pattern, trend explorer
• Typical UX usage: Field Parameter / Button Slicer → Line chart → optional target/reference → small multiples or detail table
• Key configuration / design guidance: Primary series dominant; reference series quieter.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Primary series dominant; reference series quieter.
• Recommended standard configuration: Primary series dominant; reference series quieter.
• Possible reusable Figma component: A design-only representation of Pattern — Trend explorer may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: #templates

Pattern — Ranking & exceptions

• Native Power BI: No — Design Pattern
• Catalog status / standard: Design Pattern / Recommended
• Purpose: Which categories perform best/worst?
• Best for: Sorted horizontal bar → conditional emphasis → Table for exact detail
• Avoid when: Do not apply mechanically when the user question or data structure differs.
• Suitable data: Relevant recovered tags: design pattern, pattern, ranking & exceptions
• Typical UX usage: Sorted horizontal bar → conditional emphasis → Table for exact detail
• Key configuration / design guidance: Sort by the analytical measure, not alphabetically.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Sort by the analytical measure, not alphabetically.
• Recommended standard configuration: Sort by the analytical measure, not alphabetically.
• Possible reusable Figma component: A design-only representation of Pattern — Ranking & exceptions may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: #templates

Pattern — Variance analysis

• Native Power BI: No — Design Pattern
• Catalog status / standard: Design Pattern / Recommended
• Purpose: Why is actual different from budget/target?
• Best for: Card delta → Waterfall → contributor ranking → detail table
• Avoid when: Do not apply mechanically when the user question or data structure differs.
• Suitable data: Relevant recovered tags: design pattern, pattern, variance analysis
• Typical UX usage: Card delta → Waterfall → contributor ranking → detail table
• Key configuration / design guidance: Waterfall order must follow a meaningful causal/accounting story.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Waterfall order must follow a meaningful causal/accounting story.
• Recommended standard configuration: Waterfall order must follow a meaningful causal/accounting story.
• Possible reusable Figma component: A design-only representation of Pattern — Variance analysis may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: #templates

Pattern — Overview → detail

• Native Power BI: No — Design Pattern
• Catalog status / standard: Design Pattern / Recommended
• Purpose: What is behind this selected item?
• Best for: Summary visual → Drillthrough button/context menu → dedicated detail page → Back
• Avoid when: Do not apply mechanically when the user question or data structure differs.
• Suitable data: Relevant recovered tags: design pattern, pattern, overview → detail
• Typical UX usage: Summary visual → Drillthrough button/context menu → dedicated detail page → Back
• Key configuration / design guidance: Carry filter context and label the selected entity clearly.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Carry filter context and label the selected entity clearly.
• Recommended standard configuration: Carry filter context and label the selected entity clearly.
• Possible reusable Figma component: A design-only representation of Pattern — Overview → detail may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: #templates

Pattern — Hierarchical analysis

• Native Power BI: No — Design Pattern
• Catalog status / standard: Design Pattern / Recommended
• Purpose: How does performance break down through levels?
• Best for: Matrix or drillable chart → BAF → Product group → Article
• Avoid when: Do not apply mechanically when the user question or data structure differs.
• Suitable data: Relevant recovered tags: design pattern, pattern, hierarchical analysis
• Typical UX usage: Matrix or drillable chart → BAF → Product group → Article
• Key configuration / design guidance: Use native hierarchy; do not fake indentation.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Use native hierarchy; do not fake indentation.
• Recommended standard configuration: Use native hierarchy; do not fake indentation.
• Possible reusable Figma component: A design-only representation of Pattern — Hierarchical analysis may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: #templates

Pattern — Root-cause exploration

• Native Power BI: No — Design Pattern
• Catalog status / standard: Design Pattern / Recommended
• Purpose: Which dimensions are associated with the result?
• Best for: Card → Decomposition Tree → detail Matrix → Drillthrough
• Avoid when: Do not apply mechanically when the user question or data structure differs.
• Suitable data: Relevant recovered tags: design pattern, pattern, root-cause exploration
• Typical UX usage: Card → Decomposition Tree → detail Matrix → Drillthrough
• Key configuration / design guidance: Treat exploratory results as evidence to investigate, not proof of causality.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Treat exploratory results as evidence to investigate, not proof of causality.
• Recommended standard configuration: Treat exploratory results as evidence to investigate, not proof of causality.
• Possible reusable Figma component: A design-only representation of Pattern — Root-cause exploration may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: #templates

Pattern — Filter-first workflow

• Native Power BI: No — Design Pattern
• Catalog status / standard: Design Pattern / Recommended
• Purpose: I know the scope I want to analyse.
• Best for: High-value slicers → optional Apply all → summary → analysis
• Avoid when: Do not apply mechanically when the user question or data structure differs.
• Suitable data: Relevant recovered tags: design pattern, pattern, filter-first workflow
• Typical UX usage: High-value slicers → optional Apply all → summary → analysis
• Key configuration / design guidance: Use only a small visible filter set. Keep advanced filters in the Filters pane.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Use only a small visible filter set. Keep advanced filters in the Filters pane.
• Recommended standard configuration: Use only a small visible filter set. Keep advanced filters in the Filters pane.
• Possible reusable Figma component: A design-only representation of Pattern — Filter-first workflow may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: #templates

Pattern — Search-by-identifier

• Native Power BI: No — Design Pattern
• Catalog status / standard: Design Pattern / Recommended
• Purpose: I know the exact item/store/order I need.
• Best for: Input Slicer → matching summary → Table / detail page
• Avoid when: Do not apply mechanically when the user question or data structure differs.
• Suitable data: Relevant recovered tags: design pattern, pattern, search-by-identifier
• Typical UX usage: Input Slicer → matching summary → Table / detail page
• Key configuration / design guidance: Prefer typed input over enormous dropdown lists.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Prefer typed input over enormous dropdown lists.
• Recommended standard configuration: Prefer typed input over enormous dropdown lists.
• Possible reusable Figma component: A design-only representation of Pattern — Search-by-identifier may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: #templates

Pattern — View switch

• Native Power BI: No — Design Pattern
• Catalog status / standard: Design Pattern / Recommended
• Purpose: I want to inspect the same analysis using another measure/dimension.
• Best for: Button Slicer + Field Parameter → shared chart/table
• Avoid when: Do not apply mechanically when the user question or data structure differs.
• Suitable data: Relevant recovered tags: design pattern, pattern, view switch
• Typical UX usage: Button Slicer + Field Parameter → shared chart/table
• Key configuration / design guidance: Prefer field parameters over duplicated visuals or bookmark hacks.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Prefer field parameters over duplicated visuals or bookmark hacks.
• Recommended standard configuration: Prefer field parameters over duplicated visuals or bookmark hacks.
• Possible reusable Figma component: A design-only representation of Pattern — View switch may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: #templates

Pattern — Mobile priority view

• Native Power BI: No — Design Pattern
• Catalog status / standard: Design Pattern / Recommended
• Purpose: What must I see on a phone?
• Best for: Top KPI(s) → primary trend/exception → essential filter(s) → compact detail
• Avoid when: Do not apply mechanically when the user question or data structure differs.
• Suitable data: Relevant recovered tags: design pattern, pattern, mobile priority view
• Typical UX usage: Top KPI(s) → primary trend/exception → essential filter(s) → compact detail
• Key configuration / design guidance: Use dedicated mobile layout; do not just shrink desktop.
• Interaction capabilities: No component-specific interaction list was recovered in the 133-entry catalog; validate the actual native behavior and apply the standard interaction vocabulary in section 10.
• Accessibility considerations: Apply the shared accessibility standard; verify actual runtime behavior for this item.
• Known limitations / restrictions: Use dedicated mobile layout; do not just shrink desktop.
• Recommended standard configuration: Use dedicated mobile layout; do not just shrink desktop.
• Possible reusable Figma component: A design-only representation of Pattern — Mobile priority view may exist in the approved BI library; no specific mapping was recovered for this entry.
• Possible Nudge BI / Power UI equivalent: Not specifically recovered; verify the current Nudge BI kit and the organization-specific Power UI inventory before claiming a mapping.
• Recovered documentation link: #templates