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

[grasdaggel]

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.

[grasdaggel]

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.

[grasdaggel]

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.

[grasdaggel]

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

[gagaxj]

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

[grasdaggel]

Any updates on this? Its been a while..

[Thommas]

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.

[Thommas]

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.

[veloraven]

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

[Laura021]

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

[grasdaggel]

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

[Laura021]

@grasdaggel Are you using a different attribute_set than Default?

[grasdaggel]

No.

[veloraven]

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

[PieterCappelle]

Any update on this?

[grasdaggel]

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.

[chickenland]

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.

[magento-engcom-team]

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

[piotrekkaminski]

This issue was moved to magento-engcom/import-export-improvements#61

[gfxguru]

How many years and this is still an issue? Really? Yes I can confirm this is still an issues with 2.2.5

[elburro1887]

Still an issue in 2.3.0

If the default store view has a different locale then the one used in the import, the attribute validation will fail.

Help: https://magento.stackexchange.com/a/289935/81745

[Adam-Young]

... any updates yet on this - I'm also getting the exact same color and size validation errors form a direct export / import on the same site without any differences in locale. Unless somehow this means that when uploading new product data it can't accept any actual new data and it needs to be loaded separately? If so what is the expected flow to first upload color / size csv?

[SolsWebdesign]

I can't believe I ran into this again. This bug has been around for ever. I had to replace all "Catalog, Search" with "catalog, search" and Search with search to import exported products from one M2.3.5 shop in another M2.3.5 shop. Both shops are identical with the same locale and the same language.

[bibz0r]

Still an issue in 2.4.1

[elburro1887]

Can this issue please be re-opened?

It was closed and moved to https://github.com/magento-engcom/import-export-improvements/issues/61 , but that repo is now archived?

Not sure what's going on here but this issue needs to be fixed, definitely.