Skip to main content

Magento 2 product collection Filtering multi-select attribute values

 If you have multi-select attribute of product like below




If you want filter value for this option Use below syntax to get product data:

->addAttributeToFilter('store_model', array('finset' => $params['store_model']))

finset key is used for multiselect attribute filter.


$objectManager = \Magento\Framework\App\ObjectManager::getInstance();

$products = $objectManager->get('Magento\Catalog\Model\Product')

        ->getCollection()

        ->addAttributeToSelect('*')

        ->addAttributeToSelect('store_brand')

        ->addAttributeToSelect('store_model')

        ->addAttributeToSelect('store_year')

        ->addAttributeToFilter('store_brand', array('finset' => $params['store_brand']))

        ->addAttributeToFilter('store_model', array('finset' => $params['store_model']))

        ->addAttributeToFilter('store_year', array('finset' => $params['store_year']))

        ->addAttributeToFilter('status', array('eq' => \Magento\Catalog\Model\Product\Attribute\Source\Status::STATUS_ENABLED))

        ->setFlag('has_stock_status_filter', false)

        ->joinField('stock_item', 'cataloginventory_stock_item', 'is_in_stock', 'product_id=entity_id', 'is_in_stock=1')

        ->addCategoriesFilter(array('eq' => 296));


same like mysql if you have one value find in array of data you will FIND_IN_SET like here we use finset

SELECT * FROM `catalog_product_entity_varchar` WHERE FIND_IN_SET(5680,value) AND entity_id = 29162 AND attribute_id=183

if this post useful pls comment 

Thank you

Comments

  1. Thank you for sharing such useful information. I really enjoyed while reading your article and it is good to know the latest updates. Do post more. And also read about Magento 2 Development Company

    ReplyDelete
  2. Nice Article. Useful information you have provided. Keep it up for your tech blog success. Also Read Magneto 2.4 features

    ReplyDelete
  3. Thanks for the sharing this amazing info. Read my blog in Why Magento is the Best eCommerce Platform for Enterprise.

    ReplyDelete
  4. Upgrade from Magento1 to Magento 2 for your website, read on to find the key differences between the two versions and then decide. Find out the differences between Magento 1 vs Magento 2.

    ReplyDelete
  5. This comment has been removed by the author.

    ReplyDelete

Post a Comment

Popular posts from this blog

magento 1 extension converted in to magento 2 process

Simple Install =================================== Download as a zip below link. unzip and upload it to your public_html or other rootdoc directory. https://github.com/magento/code-migration. login to your server via shell switch to the code-migration-develop directory by running following command   cd code-migration-develop Run command following command in root directory of this toolkit composer instal Before running the migration, the following directories need to be prepared: ===================================== * `<src>` - Directory that contains custom Magento 1.x code that is intended to be migrated. The code must follow the Magento 1.x directory structure.   Magento1.x core files must not be included. * `<dst>` - Empty directory for the toolkit to put the generated Magento 2 code to * `<m1>` - Directory that contains: * Vanilla Magento 1.x codebase, and * Custom Magento 1.x code same as...

Magento Debug HEADERS ALREADY SENT error

When you  receiving the following error in  system.log file: app\code\core\Mage\Core\Controller\Response\Http.php:44  [1] \www.pawan.com\lib\Zend\Controller\Response\Abstract.php:727  [2]  \www.pawan.com\app\code\core\Mage\Core\Controller\Response\Http.php:75  [3]  \www.pawan.com\app\code\core\Mage\Core\Controller\Varien\Front.php:188  [4]  \www.pawan.com\app\code\core\Mage\Core\Model\App.php:304  [5]  \www.pawan.com\app\Mage.php:596  [6]  \www.pawan.com\index.php:81 if you have no idea what file is causing this. Here is the steps to debug. That error is thrown from Mage_Core_Controller_Response_Http -> sendHeaders(). This function calls the super class function that actually does the check to see whether or not headers have already been sent, Zend_Controller_Response_Abstract -> canSendHeaders(). The Zend_Controller_Response_Abstract class handles, among other things, sending response header...