Magento sales order grid customization

Magento sales order grid customization

September 2, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Magento sales order grid customization

Customizing Magento Sales Order Grid: A Comprehensive Guide

Hello developers! Today, we’re going to tackle a common challenge - customizing the Magento sales order grid by adding an additional column from a related table. We’ll be using the sales_flat_order_address and sales_flat_order_grid tables as references.

The aim is to join these two tables in such a way that the entity_id field from sales_flat_order_address matches the parent_id field in sales_flat_order_grid. This will allow us to pull data for the new column.

The Error: Column ‘Entity_Id’ Is Ambiguous

When attempting this join, you might encounter an error message:

“Integrity constraint violation: 1052 Column ‘entity_id’ in group statement is ambiguous”

This occurs because both tables have a field named entity_id, causing the database to be unsure which table’s field you’re referring to.

The Solution: Specifying the Table Alias

To resolve this ambiguity, we need to specify the table alias when joining the fields. Here’s how to modify your join statement:

$collection = Mage::getResourceModel($this->getCollectionClass());
$collection->getSelect()
    ->joinLeft(array('table_alias2' => $collection->getTable('sales/deliveryinfo')),
               'main_table.entity_id = table_alias2.parent_id',
               array('table_alias2.entity_id'));

In this code:

  • main_table is an alias for the main collection table (sales_flat_order_grid).
  • table_alias2 is the alias we give to our secondary table (sales_flat_order_address).
  • The second argument is the join condition: main_table.entity_id = table_alias2.parent_id.
  • The third argument lists the fields we want to retrieve from the secondary table.

Ensuring Proper Functionality

Remember, adding a new column requires not just joining the tables but also ensuring that the grid’s layout and save functions are modified accordingly. You’ll need to add the new field to your grid configuration XML file:

<column id="new_column_id" index="entity_id" type="text">
    <header translate="label">New Column</header>
    <sortable sort="desc"/>
</column>

Conclusion

Customizing Magento order grids requires a deep understanding of database joins and the Magento grid system. By properly specifying table aliases, you can successfully join tables even when they have identical field names.

Remember to test your changes thoroughly after making these modifications, as they can impact other parts of your store’s functionality.

For more advanced customization techniques in Magento 2, I recommend checking out our comprehensive guide on Magento 2 Development Best Practices.

Happy coding! Let me know if you have any other questions about Magento or need help with a specific feature.

Database Admin Orders Errors

Our network