Skip to content
This repository has been archived by the owner on Apr 29, 2019. It is now read-only.

Export error causing "invalid option value" on import on configuarable Products 2.1.5 #87

Closed
piotrekkaminski opened this issue Jan 3, 2018 · 5 comments

Comments

@piotrekkaminski
Copy link
Contributor

From @torchtrust on March 13, 2017 14:18

Preconditions

Bitnami Magento Stack 2.1.5-0

Steps to reproduce

  1. Create Product Attributes that have a different value for the Admin and Store View
  2. Create a product that is configurable
  3. export Products
  4. import Products

Expected result

  1. import should complete without error

Actual result

  1. "invalid option value" on the configurable Product.

Copied from original issue: magento/magento2#8867

@piotrekkaminski
Copy link
Contributor Author

From @torchtrust on March 13, 2017 14:20

If I edit the 'configurable_variations' of the configurable Product to match the 'additional_attributes' of the virtual Product then the import will work

@piotrekkaminski
Copy link
Contributor Author

From @AlexWorking on June 30, 2017 8:28

Hello @torchtrust . An internal issue - MAGETWO-70368 has been created based on Your issue. You”ll be informed as the issue is fixed. Thank You for applying.

@piotrekkaminski
Copy link
Contributor Author

From @rtroncoso on July 18, 2017 22:7

I'm experiencing this same issue using a Magento 2.1.7 install. I found that in my case this was produced by the "Multiple Value separator" in the products import form, which was set by default as a comma instead of a pipe character ( | ).

Changing the text field to use a pipe instead of a comma as the separator fixed this issue for me. Will be gathering more information and try to reproduce the fix on a fresh install, if this is the case I'll go ahead and create a PR to change this default value in the products import form.

@piotrekkaminski
Copy link
Contributor Author

From @magento-engcom-team on October 4, 2017 6:30

@torchtrust, thank you for your report.
We've created internal ticket(s) MAGETWO-70368 to track progress on the issue.

@dmanners
Copy link
Contributor

Duplicate of #90

@dmanners dmanners marked this as a duplicate of #90 Jan 17, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants