dynamic-rows.js:658 Uncaught TypeError: dataRecord.slice while editing bundle products

github-jira-sync-bot commented 7 months ago

Short issue description

Error in console when deleting bundle product option.

Steps to reproduce

Create a bundle product with two options. Make sure to set the first option input type as < Radio Button ] and the second option as [ Checkbox ].
Save the product.
Open the browser console.
Delete the first option [ Radio Button >, and observe the output in the console.
Actual results

The console shows the following error.

dynamic-rows.js:658 Uncaught TypeError: dataRecord.slice is not a function
    at UiClass.getChildItems (dynamic-rows.js:658:31)
    at UiClass.setDefaultState (dynamic-rows.js:348:35)
    at executeBound (underscore.js:986:71)
    at UiClass.<anonymous> (underscore.js:1018:20)
    at UiClass.setDefaultState (underscore.js:74:37)
    at UiClass.onChildrenUpdate (dynamic-rows.js:317:22)
    at executeBound (underscore.js:986:71)
    at underscore.js:1018:20
    at underscore.js:74:37
    at events.js:85:26

Expected results

No errors in the console.

github-jira-sync-bot commented 7 months ago

The issue was exported from the internal Jira. The link to the original Jira issue: https://jira.corp.adobe.com/browse/ACP2E-2909

m2-assistant[bot] commented 7 months ago

Hi @github-jira-sync-bot. 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.

chittima commented 7 months ago

Internal team is working on this issue

magento / magento2