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.

Sign up for GitHub

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

Jump to bottom

Missing Billing Address Error in Admin Dashboard When Creating Order via REST API with Only Payment Information #39651

Open
1 of 5 tasks
bhushan-cs opened this issue Feb 21, 2025 · 6 comments · May be fixed by #39678
Open
1 of 5 tasks

Missing Billing Address Error in Admin Dashboard When Creating Order via REST API with Only Payment Information #39651

bhushan-cs opened this issue Feb 21, 2025 · 6 comments · May be fixed by #39678
Assignees
@MaximLogic
Labels
Area: APIs Component: Admin Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Reported on 2.4.7-p4 Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch

Comments

@bhushan-cs
Copy link

Preconditions and environment

  • Magento 2.4.7-p4

Steps to reproduce

  1. Authenticate with valid bearer token
  2. Send PUT request to /rest/V1/orders/create with the following payload:
    { "entity": { "payment": { "method": "cashondelivery" } } }

Expected result

The API should return error with message "Please provide billing address for the order." and return a 400 status code.

Actual result

  • If you open the admin dashboard you get this error

Error: Call to a member function getName() on null in /Users/bhushan/Sites/magento_test/vendor/magento/module-backend/Block/Dashboard/Orders/Grid.php:105

Image

Stack trace.txt

  • The API returns success 200 status code and returns created order json

{ "base_grand_total": null, "base_total_due": 0, "created_at": "2025-02-21 18:50:46", "customer_email": null, "entity_id": 4, "grand_total": null, "increment_id": "000000004", "protect_code": "5afbdfaa9f582fa84f271c2ff94452b3", "store_name": "Main Website\nMain Website Store\nDefault Store View", "total_due": 0, "total_item_count": 0, "updated_at": "2025-02-21 18:50:46", "items": [], "payment": { "account_status": null, "additional_information": [ null ], "cc_last4": null, "entity_id": 4, "method": "cashondelivery", "parent_id": 4 }, "status_histories": [] }

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 M2 Assistant
Copy link

m2-assistant bot commented Feb 21, 2025

Hi @bhushan-cs. 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.

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.

@engcom-Bravo engcom-Bravo self-assigned this Feb 24, 2025
@m2-assistant M2 Assistant
Copy link

m2-assistant bot commented Feb 24, 2025

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

  • 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-Bravo engcom-Bravo added the Reported on 2.4.7-p4 Indicates original Magento version for the Issue report. label Feb 24, 2025
@github-project-automation github-project-automation bot moved this to Ready for Confirmation in Issue Confirmation and Triage Board Feb 24, 2025
@engcom-Bravo
Copy link
Contributor

Hi @bhushan-cs,

Thanks for your reporting and collaboration.

We have tried to reproduce the issue in Latest 2.4-develop instance and the issue is reproducible.Kindly refer the screenshots.

Image Image

We are getting error when we open admin dashboard Error: Call to a member function getName() on null in /usr/local/var/www/magentop/magento2/app/code/Magento/Backend/Block/Dashboard/Orders/Grid.php:105

Hence Confirming the issue.

Thanks.

@engcom-Bravo engcom-Bravo added Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Component: Admin Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Area: APIs labels Feb 26, 2025
@github-jira-sync-bot
Copy link

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

@m2-assistant M2 Assistant
Copy link

m2-assistant bot commented Feb 26, 2025

✅ Confirmed by @engcom-Bravo. Thank you for verifying the issue.
Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

@MaximLogic
Copy link

@magento I am working on this

MaximLogic pushed a commit to MaximLogic/magento2-contribute that referenced this issue Feb 28, 2025
@MaksimLogic
magento#39651: Missing Billing Address Error in Admin Dashboard When …
fde8344 
…Creating Order via REST API with Only Payment Information

- added require for billing address in order repository save method
@MaximLogic MaximLogic linked a pull request Feb 28, 2025 that will close this issue
Open
5 tasks
MaximLogic pushed a commit to MaximLogic/magento2-contribute that referenced this issue Feb 28, 2025
@MaksimLogic
magento#39651: Missing Billing Address Error in Admin Dashboard When …
b116e00 
…Creating Order via REST API with Only Payment Information

- fixed copyright
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@MaximLogic MaximLogic

Labels
Area: APIs Component: Admin Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Reported on 2.4.7-p4 Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch
Projects
None yet
Milestone
No milestone
4 participants
@bhushan-cs @engcom-Bravo @github-jira-sync-bot @MaximLogic