Use command update product and category will add store id 1 data

[yihang861]

Preconditions and environment

• Magento version
• Anything else that would help a developer reproduce the bug
  magento2.4.4

Steps to reproduce

1 create a new command update product and setCategoryIds
protected function execute(InputInterface $input, OutputInterface $output)
{
$this->appState->setAreaCode('frontend');
$this->areaList->getArea(Area::AREA_FRONTEND)->load(Area::PART_TRANSLATE);
$objectManager = \Magento\Framework\App\ObjectManager::getInstance();
$storeManager = $objectManager->get('\Magento\Store\Model\StoreManagerInterface');
$storeId = $storeManager->getStore()->getStoreId();
$productCollectionFactory = $objectManager->get('\Magento\Catalog\Model\ResourceModel\Product\CollectionFactory');
$collection = $productCollectionFactory->create();
$collection->addAttributeToFilter('sku', 'test product 1');
$collection->addAttributeToSelect('*');
foreach ($collection as $product)
{
$product->setData('name', 'test update product name 0001');
$product->setCategoryIds(['3']);
$product->save();
echo "Product Updated". $product->getId().' storeId:'.$storeId;
}
}

2 execute command
3 will update store_id 1 data ,admin default scope can not see the data change
4 frontend product data changed .
5 table catalog_category_entity_varchar add data with store id = 1
SELECT * FROM catalog_category_entity_varchar WHERE store_id = 1
6 if change product data in magento backend default scope , frontend data can not update any more.

Expected result

use command change product and category data with store id 0

Actual result

in admin backend need change store scope can see the data change.
in default scope can not see the change data.
and in catalog_category_entity_varchar table will add data with store id = 1

Additional information

No response

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 @yihang861. Thank you for your report.
To speed up processing of this issue, 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.

[m2-assistant]

Hi @engcom-Hotel. 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).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas 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-Hotel]

Hello @yihang861,

Thanks for the report and collaboration!

We have tried to reproduce the issue in Magento 2.4-develop branch but the issue is not reproducible for us. In order to reproduce the issue, we have created a custom module. We are attaching the same for reference:

Magz.zip

We have no records found with Store ID 1:

Please let us know if we have missed anything.

Thanks

[yihang861]

Hi @engcom-Hotel .
firstly you need add a product sku test product 1.
then you update the product with the command . you can found the product name change in frontend, but not change in backend with default scope.

SELECT * FROM catalog_product_entity_varchar WHERE store_id = 1

that I want to say . use command to change data the deault store_id is 1.

[engcom-Hotel]

Hello @yihang861,

Thanks for the reply!

You were right, after running the update command, we can see the name is updated in the frontend but in the backend, it shows the old name only. Please refer to the attached screenshots:

Hence confirming the issue.

Thanks