MAGENTO 2.3.5 /V1/products overwrite default values on multi-store site even when only one field is sent to update

[lano-vargas]

Preconditions (*)

1. V:2.3.5, 2.4-develop
2. Product API (catalogProductRepositoryV1)

Steps to reproduce (*)

1. Configure all store view to run under one domain E.G: dev.test.
2. Set one more Environment apart from default website/store/store view.
3. E.G: IE
   
4. Create product on all store view using postman or any other tool:
   URL: rest/all/V1/products
   BODY

{
  "product": {
    "sku": "test-1",
    "name": "Test 1",
    "attribute_set_id": 4,
    "price": 10,
    "status": 1,
    "visibility": 4,
    "type_id": "simple",
    "weight": 100
  },
  "saveOptions": true
}

5. Update product name for IE store view:
   URL: rest/en-ie/V1/products
   BODY:

{
  "product": {
    "sku": "test-1",
    "name": "Test 1 changed",
  },
  "saveOptions": true
}

Expected result (*)

1. When API for en-ie is sent I expect only product name changed/updated for that store view

Actual result (*)

1. Instead all values previously sent for all store view have the checkbox unchecked and populated with the all store view data therefore this values cannot be updated using the all store views again

Thanks

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• 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 @lano-vargas. 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

[lano-vargas]

@magento give me 2.3.5 instance

[magento-deployment-service]

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

[magento-deployment-service]

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

[lano-vargas]

@magento give me 2.4-develop instance

[magento-deployment-service]

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

[magento-deployment-service]

Hi @lano-vargas, here is your Magento Instance: https://b0b3dd658546aaed31c0d7fa585bd8e8-2-4-develop.instances.magento-community.engineering
Admin access: https://b0b3dd658546aaed31c0d7fa585bd8e8-2-4-develop.instances.magento-community.engineering/admin_6579
Login: 3bf9336c
Password: e910c429eb6a

[lano-vargas]

@magento-team The issue however is on 2.3.5 I cannot test REST api USING the instance 2.4 given url:

Can you confirm if this is a bug please ?

Thanks

[lano-vargas]

@magento give me 2.4-develop instance

[magento-deployment-service]

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

[magento-deployment-service]

Hi @lano-vargas, here is your Magento Instance: https://b0b3dd658546aaed31c0d7fa585bd8e8-2-4-develop.instances.magento-community.engineering
Admin access: https://b0b3dd658546aaed31c0d7fa585bd8e8-2-4-develop.instances.magento-community.engineering/admin_2ebd
Login: 38faf779
Password: ba2b1804e1e3

[lano-vargas]

@magento I've replicated the issue on 2.4 instance see updated :

I would spect only the Product Name checkbox to be unchecked but all store view fields checkbox are unchecked!

[m2-assistant]

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