Exporting and reimporting products out of the box creates massive CSV bugs

[piotrekkaminski]

From @grasdaggel on March 29, 2016 14:15

Hi there,

we tried to export products from one store to another. This caused errors on ALL rows in the respective CSV.

We are using Magento 2.0.2

Validation Results

Data validation is failed. Please fix errors and re-upload the file..
Following Error(s) has been occurred during importing process:
Only first 100 errors are displayed here. Download full report
1. Value for 'visibility' attribute contains incorrect value, see acceptable values on settings specified for Admin in rows: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49
2. Value for 'msrp_display_actual_price_type' attribute contains incorrect value, see acceptable values on settings specified for Admin in rows: 1, 2, 3, 4, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49
3. Value for 'country_of_manufacture' attribute contains incorrect value, see acceptable values on settings specified for Admin in rows: 1
4. Value for '%s' attribute contains incorrect value in rows: 1
Checked rows: 49, checked entities: 49, invalid rows: 49, total errors: 97

We did not modify the file nor did we have opened it. This problem should be reproduceable by exporting products without any further configuration and reimporting the very same file into another different Magento2 store.

Only thing is that there are custom fields, which are exported, too.

Copied from original issue: magento/magento2#3923

[piotrekkaminski]

From @grasdaggel on March 29, 2016 14:29

Problem already tracked down a little. Export throws in HTML content and uses linebreaks (probably \r\n) in the CSV which might create those bugs.

[piotrekkaminski]

From @grasdaggel on March 29, 2016 14:35

It seems that this isnt't the problem, since HTML is correctly encapsulated in "'s. I've found out that class="NNN" references are in the CSV with class=""NNN"" (double "). This might be a problem. Replacing all the "" with " or ' does not solve the problem, however.

[piotrekkaminski]

From @grasdaggel on March 29, 2016 14:44

Heres the CSV: http://www33.zippyshare.com/v/ENnw16d2/file.html

[piotrekkaminski]

From @gagaxj on April 10, 2016 14:24

I have similar problem to import only two products on a freshly installed magento 2.0.4

1. Value for 'visibility' attribute contains incorrect value, see acceptable values on settings specified for Admin in rows: 1, 2

[piotrekkaminski]

From @grasdaggel on April 11, 2016 11:5

Any updates on this? Its been a while..

[piotrekkaminski]

From @Thommas on June 16, 2016 3:4

Just a guess, have a look at this:

<select id="visibility" name="product[visibility]" class="select admin__control-select" data-ui-id="product-tabs-attributes-tab-fieldset-element-select-product-visibility">
<option value="1">Not Visible Individually</option>
<option value="2">Catalog</option>
<option value="3">Search</option>
<option value="4" selected="selected">Catalog, Search</option>
</select>

Well I just tried with 1/2/3/4, not working.

[piotrekkaminski]

From @Thommas on June 22, 2016 8:58

OK, so I just figured out you need to translate the labels in your import file.

I'm using spanish, so with 'No es visible individualmente' instead of 'Not Visible Individually', the validation works fine.

[piotrekkaminski]

From @veloraven on August 18, 2016 13:31

@grasdaggel thank you for your report.
Do you use any localization in your stores?

[piotrekkaminski]

From @Laura021 on August 25, 2016 22:14

I do not have labels in other languages and still having a bunch of errors with the exported file.

Must of them have the message :

Value for 'gift_message_available' attribute contains incorrect value, see acceptable values on settings specified for Admin,Value for 'color' attribute contains incorrect value, see acceptable values on settings specified for Admin

[piotrekkaminski]

From @grasdaggel on August 26, 2016 8:56

Yes, we do use the Splendid Internet de_DE CSV with round about 10k Lines of translations.

[piotrekkaminski]

From @Laura021 on August 26, 2016 21:34

@grasdaggel Are you using a different attribute_set than Default?

[piotrekkaminski]

From @grasdaggel on August 29, 2016 8:39

No.

[piotrekkaminski]

From @veloraven on October 21, 2016 13:53

I was able to reproduce this issue: in case when admin who import products uses different locale than the one who made export.
Internal ticket: MAGETWO-59946

[piotrekkaminski]

From @PieterCappelle on December 19, 2016 18:56

Any update on this?

[piotrekkaminski]

From @grasdaggel on December 21, 2016 10:53

This is STILL buggy. The Importer says that there are defect rows, however, the import is still successful.

This needs to be addressed, as the import function is necessary for customers with higher stocks and invetories.

[piotrekkaminski]

From @chickenland on April 12, 2017 10:51

I'm using 2.1.4 and this is still an issue.

It's not ideal, but I've found adding logging to the validateOptions() function in \Magento\CatalogImportExport\Model\Import\Product tells me what the acceptable values are (despite exporting/reimporting the exact same CSV).

For instance, visibility set to "Catalog,Search" in the export, won't import, but validateOption is expecting "catalog, search" - updating my CSV makes this work.

[piotrekkaminski]

From @magento-engcom-team on October 17, 2017 12:44

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