Wrong price is synced in data exporter for bundle products

[zhovnirigor]

Preconditions and environment

• Magento version 2.4.7-p4
• Bundle product is created with variation price set on both default and website level. Prices on default and website level must differ.

Steps to reproduce

1. Run a catalog_data_exporter_products reindex.
2. Debug a query composed in \Magento\BundleProductDataExporter\Model\Query\BundleProductOptionValuesQuery::getQuery

Expected result

1. price_value for the variation of the bundle product in the result is taken from the website level if set, not default level. This means it is taken from catalog_product_bundle_selection_price table. The price set only on default level is taken from the default level (= from catalog_product_bundle_selection table).

Actual result

1. price_value for the variation of the bundle product in the result is always taken from the default level, not website level - even if set on website level. This means it is always taken from catalog_product_bundle_selection table, never from catalog_product_bundle_selection_price table.

Additional information

Patch fixes this problem (patch assumes the installation is done in 'vendor' folder).

bundle.patch.zip

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

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

[engcom-Hotel]

Hello @zhovnirigor,

We are in discussion with the internal team for this issue. Meanwhile we are moving this On Hold.

Thanks

[m2-assistant]

Hi @engcom-Hotel. 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

  - 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-Hotel]

Hello @zhovnirigor,

Thanks for the report and collaboration!

We have tried to reproduce this issue with the latest development branch i.e. 2.4-develop and after going through the codebase it seems the issue is reproducible. Please refer to the below explanation for the same:

1. In the getQuery method, the price_value column is directly fetched from the catalog_product_bundle_selection table (main_table.selection_price_value).
2. There is no logic in the query to check or prioritize the price set at the website level (from the catalog_product_bundle_selection_price table).
3. As a result, the price_value is always taken from the default level (catalog_product_bundle_selection table), ignoring the website-level price.

Hence confirming the issue.

Thanks