Filtering on date does not work because of ambigous field names

[RobKega]

Preconditions and environment

• Magento version : 2.4.7-p6

When filtering the order grid on date an error occurs.

This is because of the introduction of certain Braintree modules in the last patch version.

The query that is generated :

SELECT main_table.*, braintree_transaction_details.transaction_source, sales_order.dispute_statusFROMsales_order_gridASmain_tableLEFT JOINbraintree_transaction_detailsON braintree_transaction_details.order_id = main_table.entity_id LEFT JOINsales_order ON sales_order.entity_id = main_table.entity_id WHERE (((created_at >= '2025-06-01 22:00:00'))) AND (((created_at<= '2025-06-26 21:59:59'))) ORDER BY main_table.created_at DESC
paypal/module-braintree is required by magento/product-community-edition so cannot be removed

Steps to reproduce

Open admin
Go to order grid
try to filter using a date

Expected result

Filtered order list with orders matching the set filters

Actual result

An error message

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

[m2-assistant]

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

Hello @RobKega ,

Thank you for your report and collaboration.

We attempted to reproduce the issue in the latest 2.4.8 instances by following the provided steps and preconditions. We are able to reproduce the issue. Please refer to the attached screenshot for details.

Steps to Reproduce:

• Login to Magento admin
• Navigate to Sales - Order
• Go to order grid
• try to filter using a date

Hence marking this issue as "Issue:Confirmed".

Thank you!

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-15037 is successfully created for this GitHub issue.