Values On Rows

By default, Pivot renders measures as generated value columns. valuesOnRows flips that layout so measures become synthetic row members instead.

Open the full demo and framework source.

Default Layout vs Values On Rows

Default layout:

rows: Region
columns: Quarter
values: Sales, Margin

This usually produces:

• one row branch per region
• one generated value column per quarter and measure

With valuesOnRows: true, the same measures become row members:

• Region
• Sales
• Margin

That is useful when:

• you have many measures and few row dimensions
• you want a more compact column area
• users compare measures vertically rather than horizontally

Configuration

const pivot: PivotConfig = {
  rows: ['region'],
  columns: ['quarter'],
  values: [
    { prop: 'sales', aggregator: 'sum' },
    { prop: 'margin', aggregator: 'avg' },
  ],
  valuesOnRows: true,
};

Explicit Values Position

Interactive example

Values on rows

Switch between Values as columns, Values at beginning/middle/end

The example loads when visible.

Reset

Use rowTree with the $values pseudo-field when measures need to appear at a specific hierarchy level:

rowTree: ['carModel', 'cellId', '$values']
rowTree: ['carModel', '$values', 'cellId']
rowTree: ['$values', 'carModel', 'cellId']

rowTree is the explicit advanced API. If it is provided, it controls value placement even when valuesOnRows is also set.

What Changes Internally

• Pivot adds a synthetic row field called Values.
• Generated value columns become value labels in the row hierarchy.
• Grouping and row drill-down now treat the value label as part of the row structure.

This is why row drill-down helpers account for valuesOnRows when deriving row props.

Tradeoffs

Benefits:

• fewer generated columns
• easier comparison of multiple measures
• clearer layouts on narrow screens

Costs:

• more synthetic rows
• row drill-down can feel deeper because the value label becomes part of the hierarchy
• users expecting a spreadsheet-style “measures across columns” layout may find it less familiar

When Not To Use It

Avoid valuesOnRows when:

• you only have one measure
• your users think in terms of wide analytical columns
• you already have a deep row hierarchy and want to keep rows compact

Next

Continue with Drill-Down to see how row and column expansion behave in both layouts.