Skip to main content

Magento 2 add associate Simple Products with custom options to Configurable Product not working

If want to add the simple products with custom options to configurable product.When you want show custom options and simple products for configurable product.

when we save product that time if custom options having of that product while saving time in database catalog_product_entity table required_options will  update as 1 if not having it updating as 0. Based on this field configuration data filtering If take a look in to this file you will get idea public_html\vendor\magento\module-configurable-product\Model\Product\Type\Configurable.php

In this file found below function private function getConfiguredUsedProductCollection
code around line

present code below function line number 1408 to 1411

private function getConfiguredUsedProductCollection(
        \Magento\Catalog\Model\Product $product,
        $skipStockFilter = true
    )

    $collection
                ->addAttributeToSelect($this->getAttributesForCollection($product))
                 ->addFilterByRequiredOptions()
                ->setStoreId($product->getStoreId());
i change like this

 $collection
            ->addAttributeToSelect($this->getAttributesForCollection($product))
             //->addFilterByRequiredOptions()
            ->setStoreId($product->getStoreId());

now you will able to see associated simple products and custom options with config products

Comments

  1. Unisoft Informatics is the Top Magento Development Company who serve their services for every business sector namely healthcare, education sector, real estate website services, mobile app development services, and more. We help you to generate more revenue through the website.

    ReplyDelete
  2. Outsource Laravel Development Company to build an online store with full-fledged features. Unisoft Informatics is the Top Laravel Development Company who provide website design and development services for all business industry no matter how large it is!

    ReplyDelete

Post a Comment

Popular posts from this blog

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...

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']))         ->ad...

Magento 2 UI Component Grid Explanation

1) layout file inside Company/Module/view/adminhtml/layout/routerid_controller_action.xml define grid as uiComponent with: 2) uiComponent is defined in Company/Module/view/adminhtml/ui_component/listing_name.xml file. File name must be the same as uiComponent name used in layout file. The structure of the file may seem pretty complex at first sight but as always these are some repeating nodes. To make it simple lets slice it. Main node of the component file is <listing xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:module:Magento_Ui:etc/ui_configuration.xsd">. It is fixed and I believe it requires namespace location attribute. Next there are typically 4 nodes inside <listing /> node: <argument />, <dataSource />, <container /> and <columns />. This is however not a strict setup as <argument /> node might be duplicated to provide more configuration or <container /> as...