Product website assignment can be removed from REST API, but admin UI still does not reflect that

[github-jira-sync-bot]

Issue

When we send a REST API like below to remove the product's website assignment it correctly works, we can see records in catalogproductwebsite data are correctly removed.

But when we go to admin panel and check we can see UI still show the product is assigned to the default store.

 I used a simple product to check the issue on 2.4-develop

PUT: rest/all/V1/products/

{
    "product": {
        "id": <product id>,
        "name": "Power Board SP 6 Way W/ Switches (test-5)",
        "visibility": "3",
        "extension_attributes": {
            "website_ids": []
        }
    }
}

 

Steps to replicate

1. Assign website to a simple product from admin UI and save, you can see the record is available in catalogproductwebsite DB table. 

2. Send the above REST API call to remove the websites assigned to that product.

3. Check the catalogproductwebsite DB table again, you can see the product website reocrd is now deleted correctly

4. Go to admin UI product edit page and check, the UI still show the product is assigned to a website.

 

Expected Result

Admin UI should correctly show that the product is not assigned to any website

 

Actual Result

Admin UI shows that the product is not assigned to any website, even when the product to website records are not available in catalogproductwebsite table.

 

[github-jira-sync-bot]

The issue was exported from the internal Jira. The link to the original Jira issue: https://jira.corp.adobe.com/browse/ACP2E-1136

[m2-assistant]

Hi @github-jira-sync-bot. 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

[chittima]

Issue is fixed and here is the commit:
ef9a763