-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.4.7 GetOrders Response always returns the same shipping address for all orders in the list #38808
Comments
Hi @erikvandermey. Thank you for your report.
Join Magento Community Engineering Slack and ask your questions in #github channel. |
Hi @engcom-Delta. Thank you for working on this issue.
|
Hi @erikvandermey , Verified the issue on 2.4.7 and we are not able to reproduce this issue. Steps to reproduce:- 1.Create two orders two shipping address Please refer the attached screenshots and let us know if we missed anything. Create orders ![]() ![]() Fetched orders ![]() ![]() ![]() ![]() |
Hi @erikvandermey , We have verified this issue again with 2.4.7 and 2.4-develop and we are not able to reproduce this. Actual Result:The correct Shipping Address per Order are returned. Hence we are closing this. Please refer the attached screenshots. Order 13 ![]() ![]() Order 14 ![]() ![]() Order 15 ![]() ![]() |
Preconditions and environment
Example:
Order A with Shipping Address A
Order B with Shipping Address B
Query for both orders returns:
Order A with Shipping Address A
Order B with Shipping Address B (!)
It appears the same thing that was reported in 2016 is happening again?
#4019
Steps to reproduce
Query multiple orders and compare the Shipping Addresses in the Order Response list.
Expected result
The correct Shipping Address per Order should be returned.
Actual result
The Shipping Address from the first order in the list is used as the Shipping Address for all subsequent orders.
Additional information
I noticed this started to happen after I updated to 2.4.7. Calling a Single Order returns the correct address, so that may be a workaround.
Release note
No response
Triage and priority
The text was updated successfully, but these errors were encountered: