Invalid SKU Handling for Linked Products in Magento

[Syamsg]

Preconditions and environment

• Magento version 2.4.x

Steps to reproduce

1. Create a New Product:

   • Navigate to Catalog > Products.
   • Click on Add Product.
   • Fill in the necessary details, and in the SKU field, enter 0.
   • Save the product.

2. Edit an Existing Product:

   • Go back to Catalog > Products.
   • Choose any existing product you wish to link the previously created product to.
   • Scroll down to the Linked Products section (Related Products, Up-Sells, or Cross-Sells).

3. Add the Product with SKU "0":

   • In the linked products section, search for the product you created with the SKU of 0.
   • Add this product as a linked product.

4. Save the Main Product:

   • Click on Save to save the changes made to the main product.

5. Observe the Error:

   • After attempting to save, an error message will appear: "The linked product SKU is invalid. Verify the data and try again."

Expected result

The system should allow the linking of the product with a SKU of "0" without throwing an error, or it should prevent saving a product with "0" as a SKU outright.

Actual result

The system throws an error stating that the linked product SKU is invalid, preventing any changes to the product.

Additional information

This issue arises in the file Magento\Catalog\Model\ProductLink\Repository, specifically in the public function save, where the following condition is used:

if (!$entity->getLinkedProductSku()) {
    throw new NoSuchEntityException(__('The linked product SKU is invalid. Verify the data and try again.'));
}

One approach to resolve this is by adding an explicit check for the SKU value to prevent saving it as "0." For instance, you could add a validation condition to prevent saving a SKU as "0" at the time of saving the product.

Release note

No response

Triage and priority

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [X] 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[bot]]

Hi @Syamsg. 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.

• 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. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: 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[bot]]

Hi @engcom-Bravo. 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: :point_down:

• [ ] 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

  - 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-Bravo]

Hi @Syamsg,

Thanks for your reporting and collaboration.

We have verified the issue in Latest 2.4-develop instance and the issue is reproducible.Kindly refer the screenshots.

The system throws an error stating that the linked product SKU is invalid, preventing any changes to the product.

Hence Confirming the issue.

Thanks.

[github-jira-sync-bot]

:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-13311 is successfully created for this GitHub issue.

[m2-assistant[bot]]

:white_check_mark: Confirmed by @engcom-Bravo. Thank you for verifying the issue.
Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.