New to Telerik UI for BlazorStart a free 30-day trial

Grid Aggregates

Updated on Sep 10, 2026

The Grid component provides built-in aggregates for column values based on grouping and also a grand total row.

In this article:

Available Aggregate Functions

There are several available aggregate functions under the Telerik.Blazor.GridAggregateType enum:

  • Average
  • Count
  • Max
  • Min
  • Sum

The Count aggregate can be applied to any type of field. The other aggregates can only be applied to numerical fields (e.g., int, decimal, double, etc.).

Where You Can Use Aggregates

You can use aggregates in the following templates:

  • GroupFooterTemplate of a GridColumn - a footer in the respective column that renders when the grid is grouped.
  • GroupHeaderTemplate of a GridColumn - a header in the respective column that renders when the grid is grouped by that column. The Value field in the context carries the current group value.
  • FooterTemplate of a GridColumn - a grand total row of footers for the entire grid.

Access The Aggregate Values

You can access the aggregate values through the template context:

  • All templates expose the aggregate values for the current column.
  • The context of the GroupHeaderTemplate and the GroupFooterTemplate has an AggregateResults property of a type Dictionary<string, GridGroupAggregateResult>. This dictionary allows you to access the aggregates for the other columns in the Grid.

How to Enable Aggregates

To enable aggregates:

  1. Under the GridAggregates tag, define the GridAggregate entries to enable the aggregations per field you want to use.
  2. If the Grid is bound to a dynamic object (Expando), set the FieldType attribute of the GridAggregate tag (it is of type Type).
  3. Set the grid's Groupable property to true.
    • If you will be using only FooterTemplates - grouping is not required.
  4. Group the grid to see the effect on group-specific templates.

Example

Use Aggregates in the Telerik Blazor Grid

Example
View Source
Loading ...

Notes

  • You should define only aggregates that you will use to avoid unnecessary calculations that may be noticeable on large data sets.

  • If you try to use an aggregate that is not defined, you will get a null value.

  • If you try to use an aggregate that is not compatible with Field type, a runtime error will occur.

  • If you update a field of a model the Data collection in the view-model, aggregates will not be updated automatically - the grid needs to re-evaluate that data first, and since this is an expensive operation a UI render does not trigger it. You can update the data collection yourself, or fetching it anew from the service (example here, see how the Create/Update/Delete events fetch data anew).

  • If you bind the Grid via OnRead event, make sure to set AggregateResults in the GridReadEventArgs event argument object. Otherwise the Grid will calculate aggregates from the data on the current page only.

CS
private async Task OnGridRead(GridReadEventArgs args)
{
    DataSourceResult result = AllGridData.ToDataSourceResult(args.Request);

    args.Data = result.Data;
    args.Total = result.Total;
    args.AggregateResults = result.AggregateResults;
}

See Also