Product custom option of type 'Drop-down' retains values in the database after being changed to type 'Field'

[ksenia-zlotin]

Preconditions and environment

2.4.4-p6

Steps to reproduce

1. Create a product with a dropdown custom option and 1 value, save the product
2. Change the existing custom option type to 'Field' and save the product
3. View the database - old values are retained

Expected result

There is no reason to retain the option's values after saving

Actual result

Values are retained and if the custom option is never used as a dropdown again- are just cluttering the database

Additional information

No response

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.
• 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”.

[m2-assistant]

Hi @ksenia-zlotin. 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.
⚠️ 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, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

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: 👇

• 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 branch
     Details

     - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
     - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced 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!

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant]

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: 👇

• 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 branch
  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced 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.

[engcom-November]

Hello @ksenia-zlotin,

Thank you for the report and collaboration!

Do you mean the options are still present in eav_attribute_option_value table after changing the type of the custom attribute?
Can you please let us know where the value is being retained.

Thank you.

[ksenia-zlotin]

When a product custom option (not to be confused with attribute) which used to be a dropdown type with values stored in the table catalog_product_option_type_value gets changed to a field type, the values in the aforementioned table remain.

[NetStorm84]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @NetStorm84. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @NetStorm84, here is your Magento Instance: https://005d6d66c7de4d7910d32a116b66ad1b.instances-prod.magento-community.engineering
Admin access: https://005d6d66c7de4d7910d32a116b66ad1b.instances-prod.magento-community.engineering/admin_c152
Login: ed01dc9d
Password: 66a25475a1f1

[engcom-November]

Hello @ksenia-zlotin,

Thank you for the quick response!

Verified this issue on 2.4-develop.
The product with a customizable Option which was a dropdown with option value 1, when changed to type field, the product retained the old option value.

Please take a look at the screenshot below:
Here we have changed the dropdown to type field

But the old option value is still retained

Hence confirming the issue.

Thank you.

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-11387 is successfully created for this GitHub issue.

[m2-assistant]

✅ Confirmed by @engcom-November. Thank you for verifying the issue.
Issue Available: @engcom-November, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.