Magento – How to Delete attribute VALUES

ce-1.5.1.0importmagento-1.7

Importing blank columns using "Replace" action does not result in deletion of attribute values.
Magento 1.5, 1.7

E.g. a csv containing a list of skus whose sale end date has passed to try to delete those dates and sale prices from the db does not work.

sku   | special_price | special_price_to_date
MX300 |               | 
MX301 |               |
MX302 |               |

etc…

Blank columns do not effect any change. So how do I delete values for a product attribute using import?

Best Answer

Your attributes are being filtered out by array_filter() in Mage_ImportExport_Model_Import_Entity_Product::_filterRowData()

Empty rows would be filtered out again in Mage_ImportExport_Model_Import_Entity_Product_Type_Abstract::prepareAttributesForSave() during Mage_ImportExport_Model_Import_Entity_Product::_saveProducts()

It therefore looks like the importer isn't built to handle this.

Related Solutions

Magento1 Attributes – Delete Unused Attribute Values

delete c,b
from eav_attribute a
inner join eav_attribute_option b on a.attribute_id = b.attribute_id
inner join eav_attribute_option_value c on c.`option_id` = b.option_id
LEFT join catalog_product_entity_int pi on b.option_id=pi.value and pi.store_id=0 and b.attribute_id=pi.attribute_id
where entity_id is null

Try this Query..

Magento – Avoid invalidating product flat table reindexing upon product attribute value save

If you only want to update a single product attribute without running the indexer, use the following method. It will be possible to update a couple of hundred products per second that way.

First, add a new product attribute estimated_time_of_arrival.
The, in your update script:

$product->addAttributeUpdate(
    'estimated_time_of_arrival',
    $date,
    $storeId // numeric store id value, e.g. Mage::app()->getStore()->getId()
);

If it's a global scope attribute, the $storeId doesn't even matter.
If you don't care about the store ID scope, you can also use:

$product->setData('estimated_time_of_arrival', $date)
    ->getResource()
    ->saveAttribute($product, 'estimated_time_of_arrival');

Both methods are equivalent (the latter will use $product->getStoreId()if the attribute has a website or store view scope).

Of course, if you use that attribute in some way that requires indexing, you will have to reindex after the updates.

Best Answer

Related Solutions

Magento1 Attributes – Delete Unused Attribute Values

Magento – Avoid invalidating product flat table reindexing upon product attribute value save

Related Topic