2

I have recently used Magmi to import all of my product data. The data imports fine and is visible in the frontend, however the layered navigation does not mirror the product data that is visible inside the admin. The attributes that are not working are multiselect and select product attributes.

I have tried reindexing all indexes multiple times and clearing all caches but it doesnt seem to have any effect. It seems as though if I view the product inside the admin and save it with changes to the filterable attribute, then the layered navigation appears reflecting these changes. Magento seems to ignore any data imported from Magmi.

Does anyone know how to ensure the layered navigation reflects the product data stored in the database?

  • Is this Magento1 or magento 2? – Stevie G Mar 2 '17 at 14:50
  • This is Magento 1 – Ryan Copeland Mar 3 '17 at 15:30
1

It turns out that the reason for this not working was that the client had converted a dropdown product attribute to a multiselect via the database and not removed the original values for each product.

As a dropdown attribute Magento stores the values inside the catalog_product_entity_int and as a multiselect attribute stores values inside the catalog_product_entity_varchar. If the values aren't removed from the catalog_product_entity_int table then Magento ignores the values inside the catalog_product_entity_varchar table hence why the fitered navigation wasn't working.

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.