Skip to content

MC-23904: Can't Refund Invoice Without 0 Quantities Through REST API #30749

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

Merged
merged 3 commits into from
Nov 14, 2020

Conversation

engcom-Echo
Copy link
Contributor

Description (*)

Related Pull Requests

Fixed Issues (if relevant)

  1. Fixes Can't Refund Invoice Without 0 Quantities Through REST API #23069

Manual testing scenarios (*)

  1. See: Can't Refund Invoice Without 0 Quantities Through REST API #23069

Additional Information:
Endpoint: POST V1/invoice/:invoiceId/refund
If you try to apply the service to an invoice created using an offline payment method, the system will return a validation error.

Questions or comments

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds are green)

@m2-assistant
Copy link

m2-assistant bot commented Nov 2, 2020

Hi @engcom-Echo. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento give me test instance - deploy test instance based on PR changes
  • @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

  • @magento run all tests - run or re-run all required tests against the PR changes
  • @magento run <test-build(s)> - run or re-run specific test build(s)
    For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

  1. Database Compare
  2. Functional Tests CE
  3. Functional Tests EE,
  4. Functional Tests B2B
  5. Integration Tests
  6. Magento Health Index
  7. Sample Data Tests CE
  8. Sample Data Tests EE
  9. Sample Data Tests B2B
  10. Static Tests
  11. Unit Tests
  12. WebAPI Tests

You can find more information about the builds here

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

For more details, please, review the Magento Contributor Guide documentation.

⚠️ According to the Magento Contribution requirements, all Pull Requests 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 Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

@engcom-Echo
Copy link
Contributor Author

@magento run all tests

@engcom-Echo engcom-Echo marked this pull request as draft November 2, 2020 15:09
@ihor-sviziev
Copy link
Contributor

ihor-sviziev commented Nov 2, 2020

I believe right now you can't even do a refund in the admin, not only through the web api, or maybe that's another use case? ❓

@ghost ghost added the Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. label Nov 3, 2020
@gabrieldagama
Copy link
Contributor

@magento run all tests

@engcom-Echo
Copy link
Contributor Author

@magento run all tests

@engcom-Echo engcom-Echo marked this pull request as ready for review November 3, 2020 14:41
@ihor-sviziev ihor-sviziev self-assigned this Nov 3, 2020
@ghost ghost added Progress: review Severity: S1 Affects critical data or functionality and forces users to employ a workaround. and removed Progress: pending review labels Nov 3, 2020
@ihor-sviziev ihor-sviziev added Award: bug fix Award: test coverage Auto-Tests: Covered All changes in Pull Request is covered by auto-tests labels Nov 3, 2020
@ihor-sviziev
Copy link
Contributor

Hi @engcom-Echo ,
Could you explain use case when such request could be valid? I believe creating an order and doing credit memo from the admin with screenshots will be good enough

@engcom-Echo
Copy link
Contributor Author

engcom-Echo commented Nov 4, 2020

@ihor-sviziev. Thank you for your question. It is important.

Example refund with offline payment :

Peek 2020-11-04 10-18

Example refund with online payment (PayPal):

image

Order:
image

@magento-engcom-team
Copy link
Contributor

Hi @ihor-sviziev, thank you for the review.
ENGCOM-8421 has been created to process this Pull Request

@engcom-Oscar engcom-Oscar self-assigned this Nov 4, 2020
@engcom-Kilo engcom-Kilo self-requested a review November 5, 2020 08:58
@engcom-Oscar
Copy link

engcom-Oscar commented Nov 9, 2020

✔️ QA Passed

Manual testing scenario

1.Create an order with online payment method, like PayPal Express Checkout and with $0 shipping cost, ex. free shipping.
2.Invoice the order in admin
3.Try to refund the invoice using the 'POST' restAPI call "invoice/{invoiceId}/refund" - items at quantity 0 and a positive adjustment. For example:
{"items": [{"qty": 0, "orderItemId": 2, "extensionAttributes": {}}], "appendComment": false, "notify": true, "isOnline": true, "arguments": {"adjustment_negative": 0.0, "adjustment_positive": 0.99, "shipping_amount": 0}}

Before applying changes provided in the PR, the API responds with error "We can't create a creditmemo without products." from the QuantityValidator.

Screenshot from 2020-11-09 13-07-09

Afters switching to the PR, refund work properly

Screenshot from 2020-11-09 13-03-28

@zakdma
Copy link
Contributor

zakdma commented Nov 13, 2020

@magento-engcom-team
Copy link
Contributor

@zakdma the pull request successfully imported.

@magento-engcom-team magento-engcom-team merged commit 6b8781e into magento:2.4-develop Nov 14, 2020
@m2-assistant
Copy link

m2-assistant bot commented Nov 14, 2020

Hi @engcom-Echo, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests Award: bug fix Award: category of expertise Award: test coverage Component: Sales Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Progress: accept Progress: extended testing QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope Release Line: 2.4 Severity: S1 Affects critical data or functionality and forces users to employ a workaround.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Can't Refund Invoice Without 0 Quantities Through REST API
7 participants