Currency Price issue for Bundle Product with ElasticSearch 6.8.x in Multi Store views

[sandip5678]

Preconditions (*)

1. Magento 2.3.3 CE & 2.4-develop
2. ElasticSearch Version 6.8.x

Steps to reproduce (*)

1. Create two storeviews under the same website and same store.

2. Set different Default Display Currency for each Store View
   i.e. (For English storeview set US Dollar and For UAE storeview set United Arab Emirates Dirham)

3. Set Allowed Currencies as follows by switching to separate storeview
   i.e. (For English storeview set US Dollar and For UAE storeview set United Arab Emirates Dirham)

4. Set the Currency Rates USD -> AED = 3.67 (Approx.)

5. Create a Bundle Product with Fixed Price Model or Dynamic Price Model and Save it
   I have created bundle product with fixed price model and give SKU - pastel and price $123

6. Perform the reindex php bin/magento indexer:reindex

7. Open the frontend site and switched to UAE storeview

8. From UAE Storeview, Open previously saved bundle product page.
   Pricing will be shown in the AED format

9. Now, Open Bundle Product on the ElasticSearch indexes.

Expected result (*)

1. For English StoreView, price fields values from price_0_1 to price_3_1 are showing in the US dollar currency.
   http://127.0.0.1:9200/magento2_product_1_v19/_search?q=pastel&pretty=true

2. AED StoreView, price fields values from price_0_1 to price_3_1 should show in the AED currency instead of US Dollar. It should show price 451.41.
   http://127.0.0.1:9200/magento2_product_2_v19/_search?q=pastel&pretty=true

Actual result (*)

1. For English Store view, price fields values from price_0_1 to price_3_1 are showing in the US dollar currency.
2. For AED Store view, price fields values from price_0_1 to price_3_1 showing in the US dollar currency only.

[m2-assistant]

Hi @sandip5678. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

@sandip5678 do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[sandip5678]

@magento give me 2.4-develop instance

[magento-engcom-team]

Hi @sandip5678. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[magento-engcom-team]

Hi @sandip5678, here is your Magento instance.
Admin access: https://i-26371-2-4-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[sandip5678]

@magento Can you please setup the Elastic Search version as it is dependent on the ElasticSearch

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

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components 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.

[magento-engcom-team]

✅ Confirmed by @engcom-Hotel
Thank you for verifying the issue. Based on the provided information internal tickets MC-30479 were created

Issue Available: @engcom-Hotel, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.