Server-side Pivoting

In this section we add Server-side Pivoting to create an example with the ability to 'Slice and Dice' data using the Server-side Row model.

Enabling Pivoting

To pivot on a column pivot=true should be set on the column definition. Additionally the needs to be in pivot mode which is set through the grid option pivotMode=true.

In the snippet below a pivot is defined on the 'year' column and pivot mode is enabled:

gridOptions: { // pivot mode enabled pivotMode: true, columnDefs: [ { field: "country", rowGroup: true }, { field: "year", pivot: true }, // pivot enabled { field: "total" } ], // other options }

For more configuration details see the section on Pivoting.

Pivoting on the Server

The actual pivoting is performed on the server when using the Server-side Row Model. When the grid needs more rows it makes a request via getRows(params) on the Server-side Datasource with metadata containing row grouping details.

The properties relevant to pivoting in the request are shown below:

// IServerSideGetRowsRequest { // pivot columns, cols with 'pivot=true' pivotCols: ColumnVO[]; // true if pivot mode is one, otherwise false pivotMode: boolean; ... // other properties }

Note in the snippet above that pivotCols contains all the columns the grid is pivoting on, and pivotMode is used to determine if pivoting is currently enabled in the grid.

Setting Secondary Columns

Secondary columns are the columns that are created as part of the pivot function. You must provide these to the grid in order for the grid to display the correct columns for the active pivot function.

For example, if you pivot on Year, you need to columns to the grid for each year contained in the data, e.g. 2000, 2002, 2004 etc...

Secondary columns are defined identically to primary columns, you provide a list of Column Definitions passing a list of columns and / or column groups using the following column api method:

columnApi.setSecondaryColumns(pivotColDefs);

There is no limit or restriction as to the number of columns or groups you pass. However it's important that the field (or value getter) that you set for the columns match.

Setting secondary columns will reset all secondary column state which means resized or reordered columns will be reset. To avoid this applications should keep track of the previously supplied secondary columns and only update the secondary columns in the grid if they have changed.

Example: Simple Pivot

The example below demonstrates server-side Pivoting. Note the following:

  • Pivot mode is enabled through the grid option pivotMode=true.
  • A pivot is placed on the Year column via pivot=true defined on the column definition.
  • Rows are grouped by Country with rowGroup=true defined on the column definition.
  • Values in the Total column are aggregated as aggFunc='sum' is defined on the column definition.
  • The pivotCols and pivotMode properties in the request are used by the server to perform pivoting.
  • New column definitions are created from the pivotFields returned from the server and supplied to the grid using columnApi.setSecondaryColumns(pivotColDefs).
  • Open the browsers dev console to view the request supplied to the datasource.

Example: Pivot Column Groups

The example below demonstrates server-side Pivoting with multiple row groups when there multiple value columns ('gold', 'silver', 'bronze') under the 'year' pivot column group. Note the following:

  • Pivot mode is enabled through the grid option pivotMode=true.
  • A pivot is placed on the Year column via pivot=true defined on the column definition.
  • Rows are grouped by Country and Sport with rowGroup=true defined on their column definitions.
  • The Gold, Silver and Bronze value columns have aggFunc='sum' defined on their column definitions.
  • The pivotCols and pivotMode properties in the request are used by the server to perform pivoting.
  • New column group definitions are created from the pivotFields returned from the server and supplied to the grid using columnApi.setSecondaryColumns(pivotColDefs).
  • Open the browsers dev console to view the request supplied to the datasource.

Example: Slice and Dice

A mock data store running inside the browser is used in the example below. The purpose of the mock server is to demonstrate the interaction between the grid and the server. For your application, your server will need to understand the requests from the client and build SQL (or the SQL equivalent if using a no-SQL data store) to run the relevant query against the data store.

The example demonstrates the following:

  • Columns Athlete, Age, Country, Year and Sport all have enableRowGroup=true which means they can be grouped on. To group you drag the columns to the row group panel section. By default the example is grouping by Country and then Year as these columns have rowGroup=true.
  • Columns Gold, Silver and Bronze all have enableValue=true which means they can be aggregated on. To aggregate you drag the column to the Values section. When you are grouping, then all columns in the Values section will be aggregated.
  • You can turn the grid into Pivot Mode. To do this, you click the pivot mode checkbox. When the grid is in pivot mode, the grid behaves similar to an Excel grid. This extra information is passed to your server as part of the request and it is your servers responsibility to return the data in the correct structure.
  • Columns Athlete, Age, Country, Year and Sport all have enablePivot=true which means they can be pivoted on when Pivot Mode is active. To pivot you drag the column to the Pivot section.
  • Note that when you pivot, it is not possible to drill all the way down the leaf levels.
  • In addition to grouping, aggregation and pivot, the example also demonstrates filtering. The columns Country and Year have grid provided filters. The column Age has an example provided custom filter. You can use whatever filter you want, as long as your server-side knows what to do with it.

Next Up

Continue to the next section to learn about Server-side Pagination.