This page has moved to Adobe Experience League and will be redirected soon.
MDVA-36718: Custom options remain after API change
MDVA-36718: Custom options remain after API change
The MDVA-36718 Magento patch fixes the issue when the old custom options remain after being changed via API.
This patch is available when the Quality Patches Tool (QPT) 1.0.22 is installed. The patch ID is MDVA-36718. Please note that the issue is scheduled to be fixed in Magento version 2.4.3.
Affected products and versions
The patch is created for Adobe Commerce version:
Adobe Commerce on cloud infrastructure 2.4.1
Compatible with Magento versions:
Adobe Commerce (all deployment methods) 2.3.0-2.4.2
NOTE
The patch might become applicable to other versions with new Quality Patches Tool releases. To check if the patch is compatible with your Adobe Commerce version, update the magento/quality-patches package to the latest version and check the compatibility on the [!DNL Quality Patches Tool]: Search for patches page. Use the patch ID as a search keyword to locate the patch.
Issue
Steps to reproduce:
- Create a simple product.
- Add a drop-down type custom option.
- Update the custom option via API: Send
PUT request to /V1/products/options/{optionId}.
Expected results:
The custom options are updated, as expected.
Actual results:
New custom options are added, but the old custom options remain.
Apply the patch
o apply individual patches, use the following links depending on your deployment method:
To learn more about Quality Patches Tool, refer to:
For info about other patches available in QPT tool, refer to the Patches available in QPT tool section.