Undefined value sets in the variant's sku

[Dhaval410]

Preconditions and environment

• Magento version: 2.4.5
• Add sample data by using this command bin/magento sampledata:deploy

Steps to reproduce

1. Go to the Stores menu -> select 'Attribute set' under the Attributes section.

2. Select any one attribute set from the list and it will open.

3. Move any group to the top above the 'Product Details' group in the group section like in the below image.
   

4. Open any product from that attribute set in which you move the group (In my case I have taken one product as marked in the below image where the attribute set is 'Bag').
   

5. Now go to the 'Configurations' tab and create a simple product by clicking the 'Create Configurations' as in the below image.
   

6. Now follow the steps mentioned below:

• Step 1: Select Attributes - select any attribute from the list and click next.
• Step 2: Attribute Values - Select options and click on the next.
• Step 3: Bulk Images, Price, and Quantity - Don't do anything and click on the next.
• Step 4: Summary - you can see the grid of the products you are about to create. But in the 'SKU' column, you can see it sets the undefined text instead of the parent SKU's text as in the below image.

Expected result

when we create variants of the product while the other tab is on the top above the 'Product Details', it should create variants with the proper SKU names like in the image.

Actual result

It sets the undefined value to the SKU as shown in step 6 of Steps to reproduce.

Additional information

As I checked the file -

/vendor/magento/module-configurable-product/view/adminhtml/web/js/variations/steps/summary.js

in this file, there is a function name 'calculate()' at line 93 as in image.

In this function getting productSku by calling function getProductValue() with passing argument 'sku'. This function is defined in the file -

/vendor/magento/module-configurable-product/view/adminhtml/web/js/variations/variations.js

at line 132 as in the image.

in the getProductValue() function, there is a code to get the value of the SKU at line 135. Here, if the 'Product Details' tab is not open by default in the product edit page in the admin then it can't able to get the value for the SKU. Because if the 'Product Details' tab is not opened then their elements don't load.

By default, the first tab will be open. So, if we add another tab to the top above the 'Product Details' tab then this tab will collapse (not open) by default. And the elements of this tab will not load. And we will get the undefined text instead of the proper SKU name for the variants. The same thing happens with the product name also.

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 @Dhaval410. 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-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: 👇

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

@magento give me 2.4-develop instance

[magento-deployment-service]

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

[magento-deployment-service]

Hi @engcom-Bravo, here is your Magento Instance: https://de38a7c58a993b0e935cde1c9780fcbd.instances.magento-community.engineering
Admin access: https://de38a7c58a993b0e935cde1c9780fcbd.instances.magento-community.engineering/admin_5241
Login: 9002c8ca
Password: ecfe93430312

[engcom-Bravo]

Hi @Dhaval410,

Thank you for reporting and collaboration.
Verified the issue on Magento 2.4-develop and 2.4.5 instances and the issue is reproducible on both the instances.We are getting Undefined value sets in the variant's sku. Kindly refer the screenshots.

Steps to reproduce:

1.Go to the Stores menu -> select 'Attribute set' under the Attributes section.

2.Select any one attribute set from the list and it will open.

3.Move any group to the top above the 'Product Details' group in the group section like in the below image.

4.Open any product from that attribute set in which you move the group

5.Now go to the 'Configurations' tab and create a simple product by clicking the 'Create Configurations' as in the below image.

6.Now follow the steps mentioned below:

Step 1: Select Attributes - select any attribute from the list and click next.
Step 2: Attribute Values - Select options and click on the next.
Step 3: Bulk Images, Price, and Quantity - Don't do anything and click on the next.
Step 4: Summary - you can see the grid of the products you are about to create. But in the 'SKU' column, you can see it sets the undefined text instead of the parent SKU's text as in the below image.

Hence Confirming the issue.

Thanks.

[github-jira-sync-bot]

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