[Magento Cloud] There is a problem with the magento report order screen

[github-jira-sync-bot]

ISSUES:
Wrong data in REPORTS>Sales>Orders if website currency is different than default one

STEPS TO REPLICATE:

• Install clean 2.4-develop
• Go to Stores > Config > Catalog > Catalog > Price and set:
  -- Catalog Price Scope = Website
• Create an additional Website, Store and Store view
• Go to Stores > Config > General > Currency Setup > Currency Options and set:
  -- Default Config:
  --- Base Currency: USD
  --- Default Display Currency : USD
  --- Allowed Currencies: EUR, USD and THB (Thai Baht)
  -- Main Website:
  --- Base Currency: EUR
  --- Default Display Currency : EUR
  --- Allowed Currencies: EUR
  -- Additional new Website:
  --- Base Currency: THB (Thai Baht)
  --- Default Display Currency : THB (Thai Baht)
  --- Allowed Currencies: THB (Thai Baht)
• Go to Stores > Currency > Currency Rates and set the empty conversion rates for the THB (set rates to 1.0000)
• Create a product, assign it to both websites, and place an order with this product in the additional Website previously created
• Make sure that the order is in status Processing (invoice it)
• In the backend, go to Reports > Sales > Orders
• Click on the Yellow warning to refresh the statistics
• Set the scope of the report on the additional website previously created and set the filter as following:
  -- Date Used: created
  -- Period: day
  -- From and To: the same day of when the test order was placed
  -- Order Status: any
  -- Empty rows: No
  -- Show Actual Values: No

ACTUAL RESULT:

• The totals are zero

EXPECTED RESULT:

• Sales Total should show the total of the placed order, converted in the currency of the website

ADDITIONAL NOTES:

• If we change the scope of the report and set it to "All Websites", the totals are shown correctly
• During my debugging, I identified that the issue is related to app/code/Magento/Reports/Block/Adminhtml/Grid/Column/Renderer/Currency.php, method getStoreCurrencyRate

[github-jira-sync-bot]

The issue was exported from the internal Jira. The link to the original Jira issue: https://jira.corp.adobe.com/browse/ACP2E-1541

[m2-assistant]

Hi @github-jira-sync-bot. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

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

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.

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant]

Hi @o-iegorov. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
• 2. 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!
• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

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

[o-iegorov]

Internal team start working on the issue

[chittima]

commit id: 993e00c

[chittima]

Issue already fixed. Here is the commit id 993e00c