Skip to content
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

Closed
1 of 5 tasks
erikvandermey opened this issue Jun 6, 2024 · 4 comments
Closed
1 of 5 tasks
Assignees
Labels
Issue: needs update Additional information is require, waiting for response Reported on 2.4.7 Indicates original Magento version for the Issue report.

Comments

@erikvandermey
Copy link

Preconditions and environment

  • 2.4.7
  • When more than one orders are returned in the Orders list, all orders will have the same Shipping Address.
  • The Shipping Address from the first order in the list is used as the Shipping Address for all subsequent orders.

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

  • 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”.
Copy link

m2-assistant bot commented Jun 6, 2024

Hi @erikvandermey. 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:


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.

Copy link

m2-assistant bot commented Jun 6, 2024

Hi @engcom-Delta. 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- 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-Delta engcom-Delta added the Reported on 2.4.7 Indicates original Magento version for the Issue report. label Jun 7, 2024
@engcom-Delta
Copy link
Contributor

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
2.Fetch order details through API
3.Verify billing address

Please refer the attached screenshots and let us know if we missed anything.

Create orders

Screenshot 2024-06-13 at 8 39 24 PM Screenshot 2024-06-13 at 8 39 42 PM

Fetched orders

Screenshot 2024-06-13 at 8 38 23 PM Screenshot 2024-06-13 at 8 38 44 PM Screenshot 2024-06-14 at 5 17 37 PM Screenshot 2024-06-14 at 5 18 18 PM

@engcom-Delta engcom-Delta added the Issue: needs update Additional information is require, waiting for response label Jun 14, 2024
@engcom-Delta
Copy link
Contributor

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

Screenshot 2024-06-25 at 3 39 43 PM Screenshot 2024-06-25 at 3 39 50 PM

Order 14

Screenshot 2024-06-25 at 3 40 46 PM Screenshot 2024-06-25 at 3 41 00 PM

Order 15

Screenshot 2024-06-25 at 3 42 22 PM Screenshot 2024-06-25 at 3 42 31 PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: needs update Additional information is require, waiting for response Reported on 2.4.7 Indicates original Magento version for the Issue report.
Projects
None yet
Development

No branches or pull requests

2 participants