Angular Data GridSSRM Row GroupingEnterprise

This section covers Row Grouping in the Server-Side Row Model (SSRM).

Enabling Row Grouping

Row Grouping is enabled in the grid via the rowGroup column definition attribute. The example below shows how to group rows by 'country':

<ag-grid-angular
    [columnDefs]="columnDefs"
    /* other grid options ... */>
</ag-grid-angular>

this.columnDefs = [
    { field: 'country', rowGroup: true },
    { field: 'sport' },
    { field: 'year' },
];

For more configuration details see the section on Row Grouping.

Server Side Row Grouping

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

The properties relevant to Row Grouping in the request are shown below:

// IServerSideGetRowsRequest
{
    // row group columns
    rowGroupCols: ColumnVO[];

    // what groups the user is viewing
    groupKeys: string[];

    ... // other params
}

Note in the snippet above the property rowGroupCols contains all the columns (dimensions) the grid is grouping on, e.g. 'Country', 'Year'. The property groupKeys contains the list of group keys selected, e.g. ['Argentina', '2012'].

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

Country and Sport columns have rowGroup=true defined on their column definitions. This tells the grid there are two levels of grouping, one for Country and one for Sport.
The rowGroupCols and groupKeys properties in the request are used by the server to perform grouping.
Open the browser's dev console to view the request supplied to the datasource.

Example: Row Grouping

Open by Default

It is possible to have rows open as soon as they are loaded. To do this implement the grid callback isServerSideGroupOpenByDefault.

`isServerSideGroupOpenByDefault`

Function

Allows groups to be open by default.

isServerSideGroupOpenByDefault = (
    params: IsServerSideGroupOpenByDefaultParams
) => boolean;

interface IsServerSideGroupOpenByDefaultParams {
  data: any;
  rowNode: IRowNode;
  // The grid api. 
  api: GridApi<any>;
  // The column api. 
  columnApi: ColumnApi;
  // Application context as set on `gridOptions.context`. 
  context: any;
}

// Example implementation
function isServerSideGroupOpenByDefault(params) {
    var rowNode = params.rowNode;
    var isZimbabwe = rowNode.field == 'country' && rowNode.key == 'Zimbabwe';
    return isZimbabwe;
}

It may also be helpful to use the Row Node API getRoute() to inspect the route of a row node.

`getRoute`

Function

Returns the route of the row node. If the Row Node is a group, it returns the route to that Row Node. If the Row Node is not a group, it returns undefined.

getRoute = () => string[] | undefined;

Below shows isServerSideGroupOpenByDefault() and getRoute in action. Note the following:

The callback opens the following routes as soon as those routes are loaded:
- [Zimbabwe]
- [Zimbabwe, Swimming]
- [United States, Swimming]
Note [Zimbabwe] and [Zimbabwe, Swimming] are visibly open by default.
Note [United States, Swimming] is not visibly open by default, as the parent group 'United States' is not open. However open 'United States' is open, it's 'Swimming' group is open.
Selecting a row and clicking 'Route of Selected' will print the route to the selected node.

Example: Open by Default

Sticky Groups

To enable sticky groups, set the groupRowsSticky property to true. This behaviour applies to all row group levels.

Example: Sticky Groups

Expand All / Collapse All

It is possible to expand and collapse all group rows using the expandAll() and collapseAll() grid API's.

// Expand all group rows
this.gridApi.expandAll();

// Collapse all group rows
this.gridApi.collapseAll();

Calling expandAll() and collapseAll() will impact all loaded group nodes, including those not visible due to their containing group been closed. This means there could potentially be a huge number of groups expanded, so this method should be used very wisely to not create massive amount of server requests and loading a large amount of data.

Calling expandAll() and collapseAll() will have no impact on rows yet to be loaded.

To open only specific groups, e.g. only groups at the top level, then use the forEachNode() callback and open / close the row using setExpanded() as follows:

// Expand all top level row nodes
this.gridApi.forEachNode(node => {
     if (node.group && node.level == 0) {
         node.setExpanded(true);
     }
 });

The example below demonstrates these techniques. Note the following:

Clicking 'Expand All' will expand all loaded group rows. Doing this when the grid initially loads will expand all Year groups. Clicking it a second time (after Year groups have loaded) will cause all Year groups as well as their children Country groups to be expanded - this is a heaver operation with 100's of rows to expand.
Clicking 'Collapse All' will collapse all rows.
Clicking 'Expand Top Level Only' will expand Years only, even if more group rows are loaded..

Example: Expand All

Providing Child Counts

By default, the grid will not show row counts beside the group names. If you do want row counts, you need to implement the getChildCount(dataItem) callback for the grid. The callback provides you with the row data; it is your application's responsibility to know what the child row count is. The suggestion is you set this information into the row data item you provide to the grid.

`getChildCount`

Function

Allows setting the child count for a group row.

getChildCount = (dataItem: any) => number;

<ag-grid-angular
    [getChildCount]="getChildCount"
    /* other grid options ... */>
</ag-grid-angular>

this.getChildCount = data => {
    // here child count is stored in the 'childCount' property
    return data.childCount;
};

Example: Child Counts

Group via Value Getter

It is possible the data provided has composite objects, in which case it's more difficult for the grid to extract group names. This can be worked with using value getters or embedded fields (i.e. the field attribute has dot notation).

In the example below, all rows are modified so that the rows look something like this:

// sample contents of row data
{
    // country field is complex object
    country: {
        name: 'Ireland',
        code: 'IRE'
    },

    // year field is complex object
    year: {
        name: '2012',
        shortName: "'12"
    },

    // other fields as normal
    ...
}

Then the columns are set up so that country uses a valueGetter that uses the field with dot notation, i.e. data.country.name

Example: Complex Objects

Filters

By default the grid will attempt to only refresh the groups which are directly impacted by the change in filters. Be aware, this can mean your grid may have empty group rows. This is because the grid will not refresh the groups above the groups it deems impacted by the filter. This behaviour can be disabled, instead favouring purging the entire grid by enabling the grid property serverSideRefreshAllLevels.

In the example below, note the following:

Filtering by Gold, Silver or Bronze fully purges the grid, this is because they have aggregations applied.
Applying a filter to the Year column does not purge the entire grid, and instead only refreshes the Year group rows.
The example does not enable serverSideRefreshAllLevels, note that if you apply a filter to Year with the value 1900, no leaf rows exist in any group.

Example: Filtering

Next Up

Continue to the next section to learn about SSRM Pivoting.