join collection to get the customer name (for admin grid)

join collection to get the customer name (for admin grid)

August 20, 2026 · Illustrated author avatarBy Stefan Bogdanescu
join collection to get the customer name (for admin grid)

Retrieving Customer Names for Magento Admin Grid

As a developer working on a custom module in Magento, you might find yourself needing to display customer names alongside other data in your admin grid layout. To achieve this, you’ll need to modify the collection query you’re currently using to join the customer_entity table and retrieve not only emails but also full names for both sellers and buyers.

Understanding Your Current Setup

You have a custom module with a corresponding database table (custom_table) that contains seller_id and buyer_id columns. These IDs link back to the entity_id field in the customer_entity table, where customer information is stored.

Your current code successfully joins this customer_entity table twice—once for sellers and once for buyers—and retrieves their email addresses using the following query:

protected function _prepareCollection()
{
  $collection = Mage::getModel('custommodule/custommodule')->getCollection();
  $collection->getSelect()
        ->join( array('ce1' => 'customer_entity'), 'ce1.entity_id=main_table.seller_id', array('seller_email' => 'email'))
        ->join( array('ce2' => 'customer_entity'), 'ce2.entity_id=main_table.buyer_id', array('buyer_email' => 'email'));
  $this->setCollection($collection);
  return parent::_prepareCollection();
}

This works well for fetching email addresses, but you want to display the customer names instead.

Retrieving Customer Names

To retrieve full names (which are stored in the firstname and lastname fields of the customer_entity table), you need to slightly modify your join conditions. Change this part of your code:

->join( array('ce1' => 'customer_entity'), 'ce1.entity_id=main_table.seller_id', array('seller_email' => 'email'))
->join( array('ce2' => 'customer_entity'), 'ce2.entity_id=main_table.buyer_id', array('buyer_email' => 'email'));

To:

->join(array('ce1' => 'customer_entity'),
  'ce1.entity_id = main_table.seller_id',
  array('seller_firstname' => 'firstname', 'seller_lastname' => 'lastname'))
->join(array('ce2' => 'customer_entity'),
  'ce2.entity_id = main_table.buyer_id',
  array('buyer_firstname' => 'firstname', 'buyer_lastname' => 'lastname'));

This code does the following:

  1. It joins the customer_entity table twice, once for sellers and once for buyers.

  2. Instead of retrieving just the email (email), it retrieves both the first name (firstname) and last name (lastname).

  3. The aliases used in your array (seller_firstname, seller_lastname, etc.) will be available to use in your grid definition later on.

Defining Your Grid Columns

After preparing your collection, you need to define these newly retrieved customer names as columns in your grid layout. You’ll do this in the _prepareColumns method:

protected function _prepareColumns()
{
  $this->addColumn('seller_name', array(
    'header' => Mage::helper('custommodule')->__('Seller Name'),
    'index'  => 'seller_firstname',
    'type'   => 'text'
  ));

  // Similarly, define a column for buyer name using the 'buyer_firstname' and 'buyer_lastname' fields
}

Conclusion

This revised approach successfully retrieves both sellers’ and buyers’ full names from the customer_entity table and displays them in your admin grid layout.

Remember to replace 'custommodule' with the actual module name you’re working on. Also, ensure that you have defined a helper class (Mage::helper('custommodule')) for your module to assist with translation.

By modifying the collection join conditions as shown above, you can seamlessly incorporate customer names into your admin grid without having to create additional database fields or complex queries. This approach is efficient and keeps your code clean.

For more information on working with Magento collections and grids, consider exploring Laravel Company’s comprehensive Magento development resources for in-depth guides and best practices.

Database Extensions Themes Admin

Our network