magento2
magento2 copied to clipboard
Coupon codes export to Excel XML not working as expected
Preconditions (*)
- Magento 2.4.5
Steps to reproduce (*)
-
Create a salesrule of type "Specific Coupon" and check "Use auto generation":

-
Hit "Save and Continue Edit"
-
Head to "Manage Coupon Codes" Tab and generate e.g. 500 Coupons:

-
Hit generate and wait for completion
-
Go to generated coupon code list and hit "Mass actions" -> "Select all"

-
All coupons (500) should now be shown as selected.
-
Choose "Export to CSV" and hit the "Export" button.

-
The generated and downloaded file contains all 500 coupons.
-
Choose "Export to Excel XML" and hit the "Export" button.

-
The generated and downloaded file only contains as much items, as choosen in the items per page selector. In the above mentioned example that would be 20.
Expected result (*)
- The export of Excel XML should contain all selected coupons. In the above mentioned example 500.
Actual result (*)
- The generated and downloaded file only contains as much items as selected in the items per page selector instead of the selected items itself.
Hi @zohmi. Thank you for your report. To speed up processing of this issue, make sure that you provided the following information:
- Summary of the issue
- Information on your environment
- Steps to reproduce
- Expected and actual results
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.
:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel
Hi @engcom-Dash. 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:
-
- Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
Details
If the issue has a valid description, the labelIssue: Format is validwill be added to the issue automatically. Please, edit issue description if needed, until labelIssue: Format is validappears.
- Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
-
- Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add
Issue: Clear Descriptionlabel to the issue by yourself.
- Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add
-
- Add
Component: XXXXXlabel(s) to the ticket, indicating the components it may be related to.
- Add
-
- Verify that the issue is reproducible on
2.4-developbranchDetails
- Add the comment@magento give me 2.4-develop instanceto deploy test instance on Magento infrastructure.
- If the issue is reproducible on2.4-developbranch, 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!
- Verify that the issue is reproducible on
- Join Magento Community Engineering Slack and ask your questions in #github channel.
Hi @zohmi ,
We are trying to reproduce the issue in 2.4.5 magento instance....But we are not able to reproduce the issue. When we trying to generate the coupon code it is not listed out in respective fields....So with coupon codes we are not able to reproduce the bug....
Here i attached the screenshots for your reference:

Steps we Followed: 1.Install magento instance 2.Go to admin panel 3.Click the Marketing option 4.Create the Cart price rule 5.Generate Coupon codes 6. Coupon codes is not generated
Let us know if we missing anything!!!
Thanks!!!
Hi @zohmi ,
We are trying to reproduce the issue in 2.4.5 magento instance....But we are not able to reproduce the issue. When we trying to generate the coupon code it is not listed out in respective fields....So with coupon codes we are not able to reproduce the bug....
Here i attached the screenshots for your reference:
![]()
![]()
Steps we Followed: 1.Install magento instance 2.Go to admin panel 3.Click the Marketing option 4.Create the Cart price rule 5.Generate Coupon codes 6. Coupon codes is not generated
Let us know if we missing anything!!!
Thanks!!!
Hi @engcom-Dash,
you have to wait for the generation of the coupon codes. As the message says, the job has been queued and will be processed asynchronously. It takes a while and then the codes are there.
Thanks
@magento give me 2.4-develop instance
Hi @engcom-Lima. Thank you for your request. I'm working on Magento instance for you.
Hi @engcom-Lima, here is your Magento Instance: https://63df51bc498c53b45db90aac329f1678.instances.magento-community.engineering Admin access: https://63df51bc498c53b45db90aac329f1678.instances.magento-community.engineering/admin_ea66 Login: b76e29e1 Password: 4a26307c9d30
:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-6688 is successfully created for this GitHub issue.
:white_check_mark: Confirmed by @engcom-Lima. Thank you for verifying the issue.
Issue Available: @engcom-Lima, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.