[UX] Configurations are not preserved on form reload when new configurable product creation fails

[github-jira-sync-bot]

This is a usability issue.

1. Open backend
2. Go to products grid
3. Create configurable product with 1 attribute named "Configurable One"
4. Save product
5. Create new configurable product configuration basing on 5 attributes with only 2 variations each
6. Enter "Configurable One" as name
7. Configure variations qty and prices (enter different price and qty for each vatiation)
8. CLick Save

(-) Actual: Form is reloaded. Error is displayed:

The value specified in the URL Key field would generate a URL that already exists.

The variations you configured have disappeared. Information that has to be entered manually and requires significant time is lost.

(/) Expected: To be identified by UX team.

• Form is reloaded, configurations are preserved.
  OR
• Form is not reloaded, AJAX validation includes URL Key check.

[github-jira-sync-bot]

The issue was exported from the internal JIRA. The link to the original JIRA issue: https://jira.corp.magento.com/browse/MC-40031

[m2-assistant]

Hi @github-jira-sync-bot. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

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

Please, add a comment to assign the issue: @magento I am working on this

---

• 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, 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

[namlier]

@magento I am working on this