Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CSV upload removing configurable_variations from configuarble products #21636

Closed
tkymuk opened this issue Mar 7, 2019 · 7 comments
Closed

CSV upload removing configurable_variations from configuarble products #21636

tkymuk opened this issue Mar 7, 2019 · 7 comments
Labels
Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed

Comments

@tkymuk
Copy link

tkymuk commented Mar 7, 2019

Preconditions (*)

  1. Magento 2.3.0 CE running on siteground shared host.

Steps to reproduce (*)

  1. I created a configurable product with 4 simple products as variations. I downloaded the CSV for these a template. Deleted the products on the site. Added 5 more configurable products with 4 simple products for each configurable. I uploaded this CSV to find that the simple products linked to the Configurables via configurable_variations i.e. sku=TK-BGSA-222-10,adult_boxing_glove_size=10 oz|sku=TK-BGSA-222-12,adult_boxing_glove_size=12 oz, were not linked and were seperate in the product view. I then downloaded the data for the products and found that there was no data in the configurable_variations. It looks like Magento has stripped the data out and ignored it. This raises an issue of how do you bulk upload configurable products?

Expected result (*)

I expected configurable products with variations to be uploaded.

Actual result (*)

It didn't happen. Variations were seperate from their configurable parents.

@magento-engcom-team magento-engcom-team added the Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed label Mar 7, 2019
@magento-engcom-team
Copy link
Contributor

Hi @tkymuk. 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-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

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

@tkymuk do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

  • yes
  • no

@ghost ghost self-assigned this Mar 11, 2019
@magento-engcom-team
Copy link
Contributor

Hi @engcom-backlog-nazar. 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).

    DetailsIf 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-engcom-team 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. Verify that the issue is reproducible on 2.2-develop branch.

    Details- Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

  • Next steps are available in case you are a member of Community Maintainers.

  • 6. Add label Issue: Confirmed once verification is complete.

  • 7. Make sure that automatic system confirms that report has been added to the backlog.

@ghost
Copy link

ghost commented Mar 11, 2019

HI @tkymuk thank you for your report, issue already here -> magento-engcom/import-export-improvements#90

@ghost ghost closed this as completed Mar 11, 2019
@tkymuk
Copy link
Author

tkymuk commented Mar 11, 2019

@engcom-backlog-nazar is there a fix or a work around in place for this yet?

@harshvardhanmalpani
Copy link

harshvardhanmalpani commented Mar 11, 2019

@tkymuk can you check type_id and has_options in table catalog_product_entity for your configurable products?
I had a similar issue #21682 and I worked around it using the following command
UPDATE catalog_product_entity SET type_id = "configurable" where sku in ("configurable-sku-1","configurable-sku-2","configurable_sku_3");

use backticks around column and table names

@tkymuk
Copy link
Author

tkymuk commented Mar 11, 2019

@harshvardhanmalpani thanks for the reply...is this a code edit or a table in phpMyAdmin?

@harshvardhanmalpani
Copy link

table catalog_product_entity
check for the product which you are trying to update

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed
Projects
None yet
Development

No branches or pull requests

3 participants