magento2
magento2 copied to clipboard
Credit memo view show wrong increment ID
Preconditions and environment
- Magento version: ver. 2.4.6-p3
- No theme apply for adminhtml
Steps to reproduce
- Create a credit memo/refund from an order
- Go to the Credit memo grid
- Open the credit memo
Expected result
The title of the page display the same credit memo ID that the one showing up on the grid.
Actual result
Seems to be a random ID (not found in the sales_creditmemo
table) but same after page refresh.
For exemple, 000008420
shows on the credit memo grid but, on the view page, we have View Memo for #000215341
. Entity id (between url and table) is correct. The ID on the title is the same if you create more than one credit memo for the same order.
Additional information
From the credit memo grid:
From the credit memo view page:
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.
- [X] 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”.
Hi @tete2soja. 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:
-
@magento give me 2.4-develop instance
- upcoming 2.4.x release - 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. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: 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.
Notice after dumping database that the number showing is the invoice increment ID. Can you tell me how to change title page to display something like View Memo (missing number for now) FOR INVOICE #000215341
?
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: :point_down:
- [ ] 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
branchDetails
- Add the comment@magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure.
- If the issue is reproducible on2.4-develop
branch, please, add the labelReproduced 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.
Hello @tete2soja,
Thank you for the report and collaboration!
Tried to reproduce this on 2.4-develop, in our case it was not reproducible. After creating the credit memo, we were able to see correct memo id in both the grid and inside the credit memo page.
Please take a look at the screenshot below:
Please check if any third party module is causing this issue and let us know.
Thank you.
Hello,
Thank you for the feedback. I will dig deeper then to find where is the code from the extension!
Hello @tete2soja, Any updates on the issue?
Hello @tete2soja,
As there is no activity on this issue for a long time, we believe the issue has been resolved, hence closing this issue. Feel free to raise a new issue or reopen this if you need more assistance.
Thank you.
Oh, yes, sorry. We are doing other tasks and didn't get time to find the source of the override yet. I will update when I find it to maybe help other!