Updating a product through the API unchecks "Use Default Value" on a bunch of attributes

[ssstankiewicz]

Preconditions and environment

• Magento 2.4.5
• 2 store views

Steps to reproduce

1. Create 2 store views
2. Add a new product with a price
3. Change store view on the product. You can see "Use Default Value" for price is checked.
4. Update the product using the API, for example uploading an image
5. View the product again
6. Notice the "Use Default Value" on Name or Description is now unchecked (other attributes as well)

Expected result

Checkbox "Use Default Value" should remain checked until a user actually unchecks it/add value per store view via API.

Actual result

Checkbox "Use Default Value" unchecks itself when you update the product using the API.

Additional information

In theory this issue was fixed in #26484 but it occurs again.

Product before request:

Product after request:

Request endpoint: /rest/en/V1/products/24-MB01/media
Request body:
24-MB01_request.odt

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 @ssstankiewicz. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

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

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.

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant]

Hi @engcom-Lima. 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.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-Lima]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @engcom-Lima. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @engcom-Lima, here is your Magento Instance: https://7547e88ff263eecc020bfeefd1e5ff6f.instances.magento-community.engineering
Admin access: https://7547e88ff263eecc020bfeefd1e5ff6f.instances.magento-community.engineering/admin_bfe5
Login: 74fc912c
Password: d324036a7654

[engcom-Lima]

Hi @ssstankiewicz ,

Thanks for your contribution and collaboration.

i have tried to reproduce the issue on 2.4-develop but issue is not reproducible to me. Below are the steps which I have followed:

1. Created two views.
2. Created a product.
3. Changed the Store view and verified "Use Default" checkbox.
4. Uploaded image from rest api.
5. Again verified the Use Default checkbox.

Screenshots for your reference:
Before and After update of image:

Before image update:

After Update:

Checked for existing product as well:

Kindly provide more information in order to reproduce the issue. Kindly test it in latest 2.4-develop and let us know if you are facing any issue.

Thanks

[ssstankiewicz]

@magento give me 2.4-develop instance

[magento-deployment-service]

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

[magento-deployment-service]

Hi @ssstankiewicz, here is your Magento Instance: https://7547e88ff263eecc020bfeefd1e5ff6f.instances.magento-community.engineering
Admin access: https://7547e88ff263eecc020bfeefd1e5ff6f.instances.magento-community.engineering/admin_a7b9
Login: f1ed86aa
Password: a41a33f8bed1

[ssstankiewicz]

@magento give me 2.4.5 instance

[magento-deployment-service]

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

[magento-deployment-service]

Hi @ssstankiewicz, here is your Magento Instance: https://13dab3cd439c55c8dfd28d83f96c74fa.instances.magento-community.engineering
Admin access: https://13dab3cd439c55c8dfd28d83f96c74fa.instances.magento-community.engineering/admin_425f
Login: 799e0821
Password: b14d8744b8e2

[ssstankiewicz]

@engcom-Lima I can confirm that issue is not reproducible on 2.4-develop. But on 2.4.5 is. Do you have any idea how to fix it temporarily?

[ssstankiewicz]

@magento give me 2.4.4 instance

[magento-deployment-service]

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

[magento-deployment-service]

Hi @ssstankiewicz, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[engcom-Hotel]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @engcom-Hotel. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @engcom-Hotel, here is your Magento Instance: https://7547e88ff263eecc020bfeefd1e5ff6f.instances.magento-community.engineering
Admin access: https://7547e88ff263eecc020bfeefd1e5ff6f.instances.magento-community.engineering/admin_1496
Login: c0cc2ade
Password: 0153cc8b6a28

[engcom-Lima]

Hi @ssstankiewicz ,

Thanks for your confirmation in above comment.
As this issue is not reproducible in latest Magento 2.4-develop. Hence, closing the issue. But for fix we will get back to you with the commit link

Thanks

[bartbollen93]

Hi @ssstankiewicz , I'm facing the same issue in 2.4.5-p5, did you find a solution for this problem?

[ssstankiewicz]

Hi @bartbollen93, yes. I attach patch for this issue.

ACSD-48133_2.4.4.zip