Fatal Error: Magento Add Column to Admin Customer Grid

Fatal Error: Magento Add Column to Admin Customer Grid

September 17, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Fatal Error: Magento Add Column to Admin Customer Grid

Adding Columns to Magento Admin Customer Grid: A Comprehensive Guide

As a senior developer, I often encounter complex issues faced by our clients who work on large-scale e-commerce platforms like Magento. Adding columns to the admin customer grid is a common requirement, but it can be challenging due to Magento’s unique architecture and data structure.

The Challenge: Adding an ‘is_onHold’ Column

Imagine you want to add a column named is_onHold to the admin customer grid in Magento. This column would display a boolean value (Yes/No) indicating whether each customer is currently on hold or not. Sounds straightforward, right? However, as our client discovered, there are a few pitfalls that can lead to fatal errors when trying to filter results based on this new column.

Code: Attempting to Add the Column

Let’s first look at the code our client tried:

$this->addColumn('is_onHold', array(
    'header' => Mage::helper('customer')->__('On Hold?'),
    'width' => '150',
    'index' => 'is_onHold',
    'type' => 'options',
    'options' => array(
      1 => 'Yes',
      0 => 'No',
  )
));

And in the _prepareCollection() method:

->addAttributeToSelect('is_onHold')

As you can see, our client followed the standard Magento process for adding a column: using the addColumn() method to define the new column and its properties, and using addAttributeToSelect() to ensure the required attribute is included in the collection.

The Fatal Error: Filtering by ‘is_onHold’

However, when trying to filter records based on the newly added is_onHold column, our client encountered a fatal error:

Invalid attribute name: is_onHold.

This error occurs because Magento’s EAV (Entity-Attribute-Value) model doesn’t recognize is_onHold as a valid customer attribute. While this attribute exists in the database table (customer_entity), it isn’t defined in the configuration.

The Solution: Defining the Attribute

To resolve this issue, we need to define the is_onHold attribute in Magento’s configuration. This involves creating an install script that adds the attribute to the eav_attribute table during installation or upgrade:

$installer = new Mage_Eav_Model_Entity_Setup('core_setup');
$installer->startSetup();

$installer->addAttribute('customer', 'is_onHold',
    array(
        'type' => 'int',
        'backend' => '',
        'frontend' => '',
        'label' => 'On Hold Status',
        'input' => 'boolean',
        'source' => '',
        'visible' => true,
        'required' => false,
        'user_defined' => false,
        'default_value' => 0,
        'is_global' => Mage_Catalog_Model_Resource_Eav_Attribute::SCOPE_GLOBAL
    )
);

$installer->endSetup();

This script defines the is_onHold attribute with the appropriate data types and settings. After running this script, the fatal error should be resolved.

Conclusion: Adding Columns to Magento Admin Grid

Adding columns to the admin customer grid in Magento requires a careful balance between standard grid configuration and EAV model management. Remember to:

  1. Define your column using addColumn() with appropriate options.
  2. Select the required attribute using addAttributeToSelect().
  3. Ensure the attribute is defined in the EAV configuration.

By following this approach, you can extend the admin customer grid functionality without encountering fatal errors during filtering operations. If you’re looking for more advanced solutions or need help with your Magento development projects, don’t hesitate to reach out to our team at LaravelCompany.com. We specialize in providing expert Magento services and support.

Happy coding!

Admin Customers Errors CLI

Our network