Skip to content
ALLURE
Skip to main content

Allure Analytics

Matrix chart-column types and variants, including Sparklines

Keep the same hierarchy and measures while selecting a per-column renderer: exact numbers, quantitative marks, trends, progress or financial waterfalls.

Table and Chart from the reference

Real renderers, explicit sample fields

These figures were captured from the unchanged current .pbiviz packages with documented sample data. They preserve the referenced chart families and variants. Your screenshots are included in Reference gallery. Full source data was not attached; example values are illustrative unless transcribed from a visible table. Field names and binding roles are explicit, and each example includes downloadable sample data.

Field wellReal field
Rows / hierarchyProduct[ProductCategoryName] → Product[ProductSubcategoryName]
Actual[Sales Actuals]
Previous period / year[Sales LY]

Hierarchical Table with automatic variances

Fields and settings
Field wellReal field / measure
Rows / hierarchyProduct[ProductCategoryName] → Product[ProductSubcategoryName]
Actual[Sales Actuals]
Previous period / year[Sales LY]
  • Table default; row hierarchy Left; headers/values Center; subtotals Top
  • Automatic absolute and relative PY variances

Chart view with overlaps and variance pins

Fields and settings
Field wellReal field / measure
Rows / hierarchyProduct[ProductCategoryName] → Product[ProductSubcategoryName]
Actual[Sales Actuals]
Previous period / year[Sales LY]
  • Chart; Actual Overlapped bar; reference Sales LY
  • Variance scale Per hierarchy level (Level default)

The Table sample transcribes the visible hierarchy and AC/PY values from your reference. Automatic absolute/relative PY variance columns are part of the Matrix, not extra DAX measures. The Chart version changes the Actual renderer to Overlapped bar with a PY reference.

Choose a variant for a specific column

  1. Open Specific column and choose Current view, Table or Chart.
  2. Select the source or custom formula column.
  3. Choose its Chart type and reference measure when needed.
  4. For Sparklines, choose Series source: Columns / groups or Numeric measures, then the series scope.
  5. Set width, units, typography, interpretation, scale and chart-specific options. Values settings affect column values; Row headers affect hierarchy labels.
Chart-column familyVariantFields / values usedPicture
NumberNumber (or Automatic for source value columns)Rows hierarchy + any numeric Actual/Additional value
SparklinesLine sparklineRows / hierarchy: Product[ProductCategoryName] → Product[ProductSubcategoryName]
Actual: [Sales Actuals]
Columns / groups: Date[Month Name Short] (Jan–Apr)
Plan scenarios: [Sales Plan]
SparklinesColumn sparklineRows / hierarchy: Product[ProductCategoryName] → Product[ProductSubcategoryName]
Actual: [Sales Actuals]
Columns / groups: Date[Month Name Short] (Jan–Apr)
Plan scenarios: [Sales Plan]
SparklinesArea sparklineRows / hierarchy: Product[ProductCategoryName] → Product[ProductSubcategoryName]
Actual: [Sales Actuals]
Columns / groups: Date[Month Name Short] (Jan–Apr)
Plan scenarios: [Sales Plan]
SparklinesOpaque areaRows / hierarchy: Product[ProductCategoryName] → Product[ProductSubcategoryName]
Actual: [Sales Actuals]
Columns / groups: Date[Month Name Short] (Jan–Apr)
Plan scenarios: [Sales Plan]
SparklinesColor sparklineRows / hierarchy: Product[ProductCategoryName] → Product[ProductSubcategoryName]
Actual: [Sales Actuals]
Columns / groups: Date[Month Name Short] (Jan–Apr)
Plan scenarios: [Sales Plan]
Progress / gauges / stateLinear progressRows / hierarchy: Product[ProductCategoryName] → Product[ProductSubcategoryName]
Actual: [Completion] (45–85)
Columns / groups: Date[Month Name Short] (Jan–Apr)
Plan scenarios: [Goal] (100)
Progress / gauges / stateLinear gauge / bulletRows / hierarchy: Product[ProductCategoryName] → Product[ProductSubcategoryName]
Actual: [Completion] (45–85)
Columns / groups: Date[Month Name Short] (Jan–Apr)
Plan scenarios: [Goal] (100)
Progress / gauges / stateRadial gaugeRows / hierarchy: Product[ProductCategoryName] → Product[ProductSubcategoryName]
Actual: [Completion] (45–85)
Columns / groups: Date[Month Name Short] (Jan–Apr)
Plan scenarios: [Goal] (100)
Progress / gauges / statePie chartRows / hierarchy: Product[ProductCategoryName] → Product[ProductSubcategoryName]
Actual: [Completion] (45–85)
Columns / groups: Date[Month Name Short] (Jan–Apr)
Plan scenarios: [Goal] (100)
Progress / gauges / stateStateRows / hierarchy: Product[ProductCategoryName] → Product[ProductSubcategoryName]
Actual: [Completion] (45–85)
Columns / groups: Date[Month Name Short] (Jan–Apr)
Plan scenarios: [Goal] (100)
Progress / gauges / stateState · variable widthRows / hierarchy: Product[ProductCategoryName] → Product[ProductSubcategoryName]
Actual: [Completion] (45–85)
Columns / groups: Date[Month Name Short] (Jan–Apr)
Plan scenarios: [Goal] (100)
Comparison / quantitative marksBarRows / hierarchy: Product[ProductCategoryName] → Product[ProductSubcategoryName]
Actual: [Sales Actuals]
Columns / groups: Date[Month Name Short] (Jan–Apr)
Plan scenarios: [Sales Plan]
Comparison / quantitative marksOverlapped barRows / hierarchy: Product[ProductCategoryName] → Product[ProductSubcategoryName]
Actual: [Sales Actuals]
Columns / groups: Date[Month Name Short] (Jan–Apr)
Plan scenarios: [Sales Plan]
Comparison / quantitative marksData barRows / hierarchy: Product[ProductCategoryName] → Product[ProductSubcategoryName]
Actual: [Sales Actuals]
Columns / groups: Date[Month Name Short] (Jan–Apr)
Plan scenarios: [Sales Plan]
Comparison / quantitative marksVariance barRows / hierarchy: Product[ProductCategoryName] → Product[ProductSubcategoryName]
Actual: [Sales Actuals]
Columns / groups: Date[Month Name Short] (Jan–Apr)
Plan scenarios: [Sales Plan]
Comparison / quantitative marksVariance pinRows / hierarchy: Product[ProductCategoryName] → Product[ProductSubcategoryName]
Actual: [Sales Actuals]
Columns / groups: Date[Month Name Short] (Jan–Apr)
Plan scenarios: [Sales Plan]
Comparison / quantitative marksDotRows / hierarchy: Product[ProductCategoryName] → Product[ProductSubcategoryName]
Actual: [Sales Actuals]
Columns / groups: Date[Month Name Short] (Jan–Apr)
Plan scenarios: [Sales Plan]
Comparison / quantitative marksSized dotRows / hierarchy: Product[ProductCategoryName] → Product[ProductSubcategoryName]
Actual: [Sales Actuals]
Columns / groups: Date[Month Name Short] (Jan–Apr)
Plan scenarios: [Sales Plan]
Comparison / quantitative marksLollipopRows / hierarchy: Product[ProductCategoryName] → Product[ProductSubcategoryName]
Actual: [Sales Actuals]
Columns / groups: Date[Month Name Short] (Jan–Apr)
Plan scenarios: [Sales Plan]
Comparison / quantitative marksBullet comparisonRows / hierarchy: Product[ProductCategoryName] → Product[ProductSubcategoryName]
Actual: [Sales Actuals]
Columns / groups: Date[Month Name Short] (Jan–Apr)
Plan scenarios: [Sales Plan]
Comparison / quantitative marksIntegrated varianceRows / hierarchy: Product[ProductCategoryName] → Product[ProductSubcategoryName]
Actual: [Sales Actuals]
Columns / groups: Date[Month Name Short] (Jan–Apr)
Plan scenarios: [Sales Plan]
Comparison / quantitative marksDumbbellRows / hierarchy: Product[ProductCategoryName] → Product[ProductSubcategoryName]
Actual: [Sales Actuals]
Columns / groups: Date[Month Name Short] (Jan–Apr)
Plan scenarios: [Sales Plan]
Financial running chartWaterfallAccount hierarchy + [Amount]; explicit Result rows; optional [Amount PL]

Sparkline grain is explicit

For the line/area/column/color samples, bind Date[Month Name Short] to Columns / groups and Sales Actuals as the series measure. Show its Grand total column with the sparkline renderer and hide repeated monthly columns if desired. The series still reads the delivered Jan–Apr values. Numeric measures is an alternative when the sparkline is intentionally a sequence across measures.

The mini-chart samples include three product rows. This guide groups the options for navigation; the actual Matrix uses a contextual per-column Chart type dropdown.

Progress, gauge, pie and state inputs

These samples use a numeric Completion measure in 0–100 units and a Goal of 100. Progress and pie show the ratio to the selected reference or configured maximum. Gauges add target/range controls; State uses thresholds and labels. Keep the numeric convention explicit: a decimal 0.69 is not a stored 69 unless the formatter or maximum is configured accordingly.

P&L waterfall and integrated comparison

P&L · waterfall

Fields and settings
Field wellReal field / measure
Rows / hierarchyAccount[Account group]
Actual[Amount]
Plan scenarios[Amount PL]
  • Financial rows: configured Results; negative costs use Mathematical mode
  • Chart waterfall; automatic Plan variances; percent row uses pp

P&L · integrated

Fields and settings
Field wellReal field / measure
Rows / hierarchyAccount[Account group]
Actual[Amount]
Plan scenarios[Amount PL]
  • Financial rows: configured Results; negative costs use Mathematical mode
  • Chart integrated; automatic Plan variances; percent row uses pp

Use Account[Account group], Amount and Amount PL. The running chart marks financial balances as Results; the integrated chart keeps Actual and Plan in the same row. Gross Margin % has its own percentage source formatting and pp variance. For positive-stored costs choose Financial and inherited Invert; for already-negative costs use Mathematical to avoid a second contribution inversion.

Custom formulas are chartable

A custom numeric column created in Formulas uses the same applicable Chart controls as a bound measure. Select it in Specific column and choose, for example, Bar, Bullet, Progress or a Sparkline. A percent-difference formula must opt into pp/bp/bps formatting explicitly. Percentage comparisons: pp, bp and bps without changing the source

Back to the Knowledge Base