Magento REST API returns not existing SKU when custom option was set #25461

ihor-sviziev · 2019-11-04T12:21:02Z

Preconditions (*)

Magento 2.3.2 or 2.3-develop

Steps to reproduce (*)

Create simple product with one custom option type drop-down with name "Color", and values "Red", "Green", also fill up SKU field for customizable options
Create Configurable product with one custom option type drop-down with name "Color", and values "Red", "Green", also fill up SKU field for customizable options
Go to Frontend, add to cart two these products
Get information about quote via REST API
Go to checkout, execute following JS in developer console, see result:

require(['mage/storage'], function(storage) {
	storage.get('/rest/default/V1/guest-carts/' + window.checkoutConfig.quoteData.entity_id + '/')
	.done(function(result) {
		console.log(result.items);
	});
});

Expected result (*)

You should have an ability to get real product SKU, it's useful for different types of integrations

sku: "Simple-1"
sku: "Configurable 2-a"

Actual result (*)

You're having not real product SKU, but added all custom options

sku: "Simple-1-Red"
sku: "Configurable 2-a-Red"

The text was updated successfully, but these errors were encountered:

m2-assistant · 2019-11-04T12:21:04Z

Hi @ihor-sviziev. 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.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@ihor-sviziev do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

yes
no

Join Magento Community Engineering Slack and ask your questions in #github channel.

ihor-sviziev · 2019-11-04T12:21:10Z

@magento give me 2.3-develop instance

magento-engcom-team · 2019-11-04T12:21:13Z

Hi @ihor-sviziev. Thank you for your request. I'm working on Magento 2.3-develop instance for you

magento-engcom-team · 2019-11-04T12:21:51Z

Hi @ihor-sviziev, here is your Magento instance.
Admin access: https://i-25461-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

m2-assistant · 2019-11-05T09:58:21Z

Hi @engcom-Charlie. 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.3-develop branch
Details
- Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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.

magento-engcom-team · 2019-11-05T10:40:17Z

✅ Confirmed by @engcom-Charlie
Thank you for verifying the issue. Based on the provided information internal tickets MC-22785 were created

Issue Available: @engcom-Charlie, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

ihor-sviziev · 2019-11-07T10:16:29Z

Hi,

As we discussed in Slack - this issue appears only when "sku" field is shown.

The result SKU is following:

<original_product_sku>-<sku_option_1>-<sku_option_2>

There is an issue not in the SKU itself, the issue that we can't really find product in the catalog by this SKU, (<original_product_sku> in this case).

I see there at least two possible solutions:

Drop functionality that appends option SKUs (backward incompatible change)
This probably it's backward compatible change, but I'm not sure if this case is valid at all.
Create new field that will contains only real product SKU (backward compatible change)
Something like original_sku=<original_product_sku>

I think there might be more possible cases to fix this issue.

@akaplya could you review this issue as architect and decide what is expected result in this case?

caitlinmekita · 2019-11-21T15:19:19Z

@magento-engcom-team give me 2.2.10 instance

magento-engcom-team · 2019-11-21T15:19:23Z

Hi @caitlinmekita. Thank you for your request.
Unfortunately, I can only deploy instances for 2.3 release line

sagar-vasani · 2020-10-09T14:08:30Z

@magento add to contributors team

m2-assistant · 2020-10-09T14:08:36Z

Hi @sagar-vasani! 👋
Thank you for joining. Please accept team invitation 👉 here 👈 and add your comment one more time.

sagar-vasani · 2020-10-09T14:09:26Z

@magento I am working on it

magento-engcom-team added the Issue: Format is valid label Nov 4, 2019

engcom-Charlie self-assigned this Nov 5, 2019

engcom-Charlie added Component: Catalog Issue: Clear Description Issue: Confirmed Reproduced on 2.3.x labels Nov 5, 2019

ghost unassigned engcom-Charlie Nov 5, 2019

magento-engcom-team added the Issue: Ready for Work label Nov 5, 2019

sdzhepa added the Progress: ready for dev label Mar 26, 2020

ihor-sviziev added the Severity: S2 label Jul 30, 2020

sdzhepa added the Triage: Dev.Experience label Aug 4, 2020

ihor-sviziev mentioned this issue Aug 17, 2020

fix "parent" products sku inconsistency with product_id #28847

Open

4 tasks

gabrieldagama added the Priority: P2 label Sep 22, 2020

gabrieldagama added this to the 2.5 milestone Sep 22, 2020

sivaschenko added the CD label Oct 7, 2020

m2-assistant bot assigned sagar-vasani Oct 9, 2020

m2-community-project bot added Progress: dev in progress and removed Progress: ready for dev labels Oct 9, 2020

sagar-vasani mentioned this issue Oct 10, 2020

Magento REST API returns not existing SKU when custom option was set #30430

Closed

4 tasks

ghost added Progress: PR in progress and removed Progress: dev in progress labels Oct 20, 2020

sdzhepa removed the Progress: PR in progress label Oct 22, 2020

ghost added the Progress: PR in progress label Oct 22, 2020

engcom-Hotel added Reproduced on 2.4.x and removed Reproduced on 2.4.x labels Oct 27, 2020

ghost unassigned sagar-vasani Oct 27, 2020

engcom-Hotel linked a pull request Oct 27, 2020 that will close this issue

Magento REST API returns not existing SKU when custom option was set #25461 #30667

Open

4 tasks

ghost assigned engcom-Hotel Oct 27, 2020

ghost added Priority: P2 Severity: S2 and removed Priority: P2 Severity: S2 labels Oct 27, 2020

gabrieldagama added WIP and removed WIP labels Jan 25, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Magento REST API returns not existing SKU when custom option was set #25461

Magento REST API returns not existing SKU when custom option was set #25461

ihor-sviziev commented Nov 4, 2019 •

edited

Loading

m2-assistant bot commented Nov 4, 2019 •

edited by ihor-sviziev

Loading

ihor-sviziev commented Nov 4, 2019

magento-engcom-team commented Nov 4, 2019

magento-engcom-team commented Nov 4, 2019

m2-assistant bot commented Nov 5, 2019

magento-engcom-team commented Nov 5, 2019

ihor-sviziev commented Nov 7, 2019 •

edited

Loading

caitlinmekita commented Nov 21, 2019

magento-engcom-team commented Nov 21, 2019

sagar-vasani commented Oct 9, 2020

m2-assistant bot commented Oct 9, 2020

sagar-vasani commented Oct 9, 2020

Magento REST API returns not existing SKU when custom option was set #25461

Magento REST API returns not existing SKU when custom option was set #25461

Comments

ihor-sviziev commented Nov 4, 2019 • edited Loading

Preconditions (*)

Steps to reproduce (*)

Expected result (*)

Actual result (*)

m2-assistant bot commented Nov 4, 2019 • edited by ihor-sviziev Loading

ihor-sviziev commented Nov 4, 2019

magento-engcom-team commented Nov 4, 2019

magento-engcom-team commented Nov 4, 2019

m2-assistant bot commented Nov 5, 2019

magento-engcom-team commented Nov 5, 2019

ihor-sviziev commented Nov 7, 2019 • edited Loading

caitlinmekita commented Nov 21, 2019

magento-engcom-team commented Nov 21, 2019

sagar-vasani commented Oct 9, 2020

m2-assistant bot commented Oct 9, 2020

sagar-vasani commented Oct 9, 2020

ihor-sviziev commented Nov 4, 2019 •

edited

Loading

m2-assistant bot commented Nov 4, 2019 •

edited by ihor-sviziev

Loading

ihor-sviziev commented Nov 7, 2019 •

edited

Loading