Rest-API updating product stock_item deletes downloadable_product_links

[EyalAmir]

Preconditions (*)

1. Magento 2.4-develop
2. Create regular downloadable product, upload downloadable content

Steps to reproduce (*)

1. Update product stock_item values using a PUT call. For example: {"product": {"sku": "Download1", "status": "1", "name": "Test Name", "price": "11.99", "type_id": "downloadable", "extension_attributes": {"stock_item": {"manage_stock": false}}}}

Expected result (*)

1. The stock_item data would be updated and downloadable product links and samples are preserved since they're not included in the extension_attributes being sent in the update.

Actual result (*)

1. After update product has no links to download content (no downloadable information). This is similar to Downloadable product links removal on update via API #15923 except that didn't resolve being able to post a subset of extension_attributes.
   

[magento-engcom-team]

Hi @EyalAmir. 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-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

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

@EyalAmir do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

[EyalAmir]

yes Eyal Amir | Co-Founder & COO * <http://www.farapp.com>* (800) 876-4109

…

On Mon, Mar 18, 2019 at 1:40 AM Magento Community Engineering < ***@***.***> wrote: Hi @EyalAmir <https://github.com/EyalAmir>. 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-engcom-team give me 2.3-develop instance - upcoming 2.3.x release For more details, please, review the Magento Contributor Assistant <https://devdocs.magento.com/guides/v2.2/contributor-guide/contributing.html#contributor-assist> documentation. @EyalAmir <https://github.com/EyalAmir> do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce? - yes - no — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#21811 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABdaJ8GX8MvFv9MEgsL7BeXvSRsuE729ks5vX1DwgaJpZM4b5OFO> .

[magento-engcom-team]

Hi @EyalAmir. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @EyalAmir, here is your Magento instance.
Admin access: https://i-21811-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[magento-engcom-team]

Hi @engcom-backlog-nazar. 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).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

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

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• Next steps are available in case you are a member of Community Maintainers.

• 6. Add label Issue: Confirmed once verification is complete.

• 7. Make sure that automatic system confirms that report has been added to the backlog.

[magento-engcom-team]

✅ Confirmed by @engcom-backlog-nazar
Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-98758, MAGETWO-98759 were created

Issue Available: @engcom-backlog-nazar, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.