[Magento 2.4.6-p1] Bundle Products - Child Product Visibility set to "Not visible individually" doesn't get returned in GraphQl Bundle Selections

[MihaiComan90]

Preconditions and environment

Magento 2.4.6-p1 Enterprise Edition.
Creating a new bundle with a child selection that has the Visibility attribute set to "Not visible individually" doesn't get returned in the product information under the options node in GraphQl Products Query, see screenshot below:

Now for some reason i saw this as core intended behaviour although it seems awfully odd, i should be able to create a product specifically for a bundle that wouldn't be visible individually.

Initial investigations led me to check the catalog_category_product indexer which stores the visibility information in the catalog_category_product_index_store* table, although it strips any VISIBILITY_NOT_VISIBLE products from getting added into that indexer.

Also what would happen if i decide not to assign this child product to a category, i should still be able to see it as the selection product response.

Steps to reproduce

1. Login to the admin
2. Create a new Simple Product with random data, Enabled, and set the visibility to VISIBILITY_NOT_VISIBLE.
3. Create a new Bundle Product and assign the above product as an option.
4. Run the catalog_category_product indexer and check the catalog_category_product_index_store1 table
5. Notice that the child product doesn't exist.
6. Run the products graphql query to get the bundle product along with options:
   options { id qty uid quantity position is_default price price_type can_change_quantity label product { name } }
7. Notice the label and product being empty.
8. Go back to the child product created at step 2
9. Change the visibility to VISIBILITY_IN_CATALOG / VISIBILITY_BOTH and repeat step 4
10. Notice the product is added to the catalog_category_product_index_store1 table and thus is available as the selection product

Expected result

I should be able to set a child product of a bundle as VISIBILITY_NOT_VISIBLE and/or without category and still see it in the graphql selection response

Actual result

Selection is displayed but with no label or product information, see below,

Additional information

No response

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @MihaiComan90. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[MihaiComan90]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @MihaiComan90. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @MihaiComan90, here is your Magento Instance: https://a20ec4f079a1f7cb8e609e6ba976028b.instances-prod.magento-community.engineering
Admin access: https://a20ec4f079a1f7cb8e609e6ba976028b.instances-prod.magento-community.engineering/admin_16ea
Login: a84b0715
Password: 9a5d1bbb36fe

[MihaiComan90]

Tested on the above instance and issue seems not reproducible, although if we take a look at the vendor/magento/module-catalog-graph-ql/Model/Resolver/Products/DataProvider/Product.php class, which is responsible for retrieving the information about the product inside the selection, we can see the following line:

if ($isChildSearch) { $visibilityIds = $isSearch ? $this->visibility->getVisibleInSearchIds() : $this->visibility->getVisibleInCatalogIds(); $collection->setVisibility($visibilityIds); }

If the $isSearch flag is set then it returns 2,4 if not 3,4 as the visibility flags. As such, any non visible individually products will not be retrieved, i don't know exactly what am i missing in the picture. Any help would be much appreciated.
Again, mentioning the above instance is 2.4-develop and i have the issue on 2.4.6-p1 Enterprise

[paales]

I can confirm this issue, we just ran into this as well.

[m2-assistant]

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

Hi @MihaiComan90,

Thank you for reporting and collaboration.

Verified the issue on Magento 2.4-develop instance and the issue is not reproducible.kindly refer the screenshots.

Steps to reproduce

• Login to the admin
• Create a new Simple Product with random data, Enabled, and set the visibility to VISIBILITY_NOT_VISIBLE.
• Create a new Bundle Product and assign the above product as an option.
• Run the catalog_category_product indexer and check the catalog_category_product_index_store1 table
• Notice that the child product doesn't exist.

• Run the products graphql query to get the bundle product along with options:

We are able to get the child products for Bundle products in the response even though when we set visibility to Not Visible individually child products returned in Bundle product graphql response.

Kindly recheck the behaviour on Magento 2.4-develop instance and elaborate steps to reproduce if the issue is still reproducible

Thanks.