Filter & Sort by Summary Data in GridView Yii 2.0

This web-tip explains how to add summary data from related models into your Yii Framework 2.0 gridview with filtering and sorting by the summary columns.

Note: This is a variation to this web-tip which filters and sorts by related fields. In this web-tip, we will see specifically how to pull in SUMMARY data from related tables.

Example Structure

Let’s say you have the following tables for Customer and Order. A customer can have multiple orders. Your objective is to display a gridview for the Customer with an order amount summary from Order table. You should be able to also sort and filter/search by order amount.

/* Customers */
CREATE TABLE `tbl_customer` (
    `id` INT(11) NOT NULL AUTO_INCREMENT COMMENT 'Unique customer id',
    `name` VARCHAR(150) NOT NULL COMMENT 'Customer name',
     PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COMMENT='Order master table';

/* Orders */
CREATE TABLE `tbl_order` (
    `id` INT(11) NOT NULL AUTO_INCREMENT COMMENT 'Unique order id',
    `created_on` DATE NOT NULL COMMENT 'Order creation date',
    `details` VARCHAR(200) COMMENT 'Order Details',
    `amount` DECIMAL(5,2) NOT NULL COMMENT 'Order Amount',
    `customer_id` INT(11) COMMENT 'Related customer id',
    PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COMMENT='Order transactions table';

/* Foreign Key */
ALTER TABLE `tbl_order`
ADD CONSTRAINT `tbl_order_FK1` 
FOREIGN KEY (`customer_id`) 
REFERENCES `tbl_customer` (`id`) 
, ADD INDEX `tbl_order_FK1` (`customer_id` ASC);


Generate your models and CRUD via Gii. You should now have the following model classes generated:

  1. Customer: The base model for tbl_person
  2. CustomerSearch: The search and filtering model for Customer within gridview.
  3. Order: The base model for tbl_order.
  4. OrderSearch: The search and filtering model for Order within gridview.

Gridview Scenarios

Let’s consider the following scenarios, that you want to display in the GridView within the index view generated for Customer.

Scenario 1: Display Order Amount Summary for each customer (and allow filter and sort)

An example describing how to add a OrderAmount column within the Customer grid with sorting and filtering. This will be a summary of amount
field from tbl_order for each customer_id.

Scenario 1 Steps

STEP 1: Implement a stat relation to get summary for OrderAmount.

Setup base model

 * Order amount for customer 
public function getOrderAmount()
    return $this
        ->hasMany(Order::className(), ['customer_id'=>'id'])

/* Your model attribute labels */
public function attributeLabels() {
    return [
        /* Your other attribute labels */
        'orderAmount'=>Yii::t('app', 'Order Amount')

STEP 2: Add an attribute orderAmount to your model CustomerSearch and configure your rules.

Setup search model

/* your calculated attribute */
public $orderAmount;

/* setup rules */
public function rules() {
   return [
    /* your other rules */
    [['orderAmount'], 'safe']

 * setup search function for filtering and sorting 
 * based on `orderAmount` field
public function search($params) {
    $query = Customer::find();
    $subQuery = Order::find()
        ->select('customer_id, SUM(amount) as order_amount')
    ], 'orderSum.customer_id = id');

    $dataProvider = new ActiveDataProvider([

     * Setup your sorting attributes
     * Note: This is setup before the $this->load($params) 
     * statement below
                'label'=>'Order Name'

    if (!($this->load($params) && $this->validate())) {
        return $dataProvider;


    $query->andFilterWhere(['like', 'name', $this->name]);

    // filter by order amount

    return $dataProvider;

STEP 3: Configure your gridview columns in your view index file

Setup view file

echo GridView::widget([

Voila, yes now, your orderAmount column as well in the grid view should be available for sort and filtering.

Potential Improvements

  1. Even though I created a getter (stat relation), I think there is a scope to improve the getOrderAmount getter function in model by directly getting the sum amount.
  2. There is a possibility probably to even avoid writing a getOrderAmount getter function in model and try to fetch the initial order amount summary based on the eager load with subquery.
  3. Some amount of query optimization with the relational data is possible instead of a left join or when working with summary columns.