Wrong dashboard totals with aggregated data

[gexxx05]

Preconditions and environment

• Magento version 2.4.4
• PHP 8.1

Steps to reproduce

1. Create some orders in your shop for testing (you need some older orders in the past few days)
2. Enable dashboard chart and use aggregated data
3. In dashboard select "Order" tab and in dropdown select "Today"
4. Change dropdown to "Last 24 hours"

Expected result

The totals below the chart should be different.

Actual result

The totals are the same whether i select "Today" or "Last 24 hours".

Additional information

The sql select for "Today": SELECT SUM(main_table.total_revenue_amount) AS revenue, SUM(main_table.total_tax_amount_actual) AS tax, SUM(main_table.total_shipping_amount_actual) AS shipping, SUM(orders_count) AS quantity FROM sales_order_aggregated_created AS main_table WHERE (period >= '2023-02-16 00:00:00' AND period <= '2023-02-16 23:59:59') AND (main_table.order_status NOT IN('Canceled')) AND (store_id = '0')

And here the result without the SUM:

The sql select for "Last 24 hours": SELECT SUM(main_table.total_revenue_amount) AS revenue, SUM(main_table.total_tax_amount_actual) AS tax, SUM(main_table.total_shipping_amount_actual) AS shipping, SUM(orders_count) AS quantity FROM sales_order_aggregated_created AS main_table WHERE (period >= '2023-02-15 11:58:12' AND period <= '2023-02-16 11:58:12') AND (main_table.order_status NOT IN('Canceled')) AND (store_id = '0')

And here the result without the SUM:

The result stay the same and so the total values. The problem is, that the field "period" in "sales_order_aggregated_created" is a date field and not datetime. The graph is also messed up because of this problem.

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.
• [X] 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[bot]]

Hi @gexxx05. 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. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: 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.

[m2-assistant[bot]]

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: :point_down:

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

[devchris79]

Hi @gexxx05, this is a repeat of my issue #36199 by the looks of it.

[gexxx05]

Hi @devchris79, Sorry, I didn't see your issue, although I was looking for related ones.

However, my problem does not only occur on page load and is more related to aggregate data. The problem is with the options today and 24h, because with aggregate data there is no time reference and so the result is not correct. When i switch to live data the sql selects table sales_order and field created_at which is a timestamp and so the result is correct.

But i can confirm that i have the same behaviour as you described in your issue. On the first load the today data is not correct, but if i switch to 24h and then back again, its correct.

Thank you

[m2-assistant[bot]]

Hi @engcom-Alfa. 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: :point_down:

• [ ] 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]

@devchris79 Thanks for your contribution & collaboration over here.

Hi @gexxx05,

Thanks for your contribution & collaboration.

Verified the issue on Magento 2.4-develop instance and the issue is reproducible but There is an ongoing confirmed issue https://github.com/magento/magento2/issues/36199 for the same. Kindly move on to this issue for latest updates / solutions on the same.

We are closing this as duplicate.

Thanks.

[gexxx05]

Thanks, but this is not the same as https://github.com/magento/magento2/issues/36199. I have already described it here: https://github.com/magento/magento2/issues/36875#issuecomment-1434415074

[engcom-Bravo]

@gexxx05 we have updated the main description of ongoing confirmed issue https://github.com/magento/magento2/issues/36199

Thanks.

[gexxx05]

You're mixing things up here. The description for this problem is only valid in this specific case if the setting "Use Aggregated Data" is set to "Yes". The issue https://github.com/magento/magento2/issues/36199 has nothing to do with aggregated data at all and is already fixed with https://github.com/magento/magento2/commit/dd769504d2a56e510b1632e8f1a5f42c9571af52.

So I would not just copy descriptions together even though the issues are different. But i will leave it for now.