Closed
Description
Preconditions
magento 2.2.5 on ubuntu 16.04 with apache and php 7.1.2. Magento is a fresh install, no custom theme nor any custom module is installed. Magento has been installed by downloaded the source via composer and then run the wizard from browser.
Steps to reproduce
- prepare a correct csv to create new products via backend. Use short values (less then 71 characters) for name/sku for a few records, then use a longer strings ((more then 71 characters) for name/sku for other records.
- go to system > import:
-- entity type = products
-- import behaviour = add/update, skip error entries
-- allow errors count = I tried with several numbers from 10 (default) to 500 but issue persists
-- field separator = ; (semicolon)
-- multiple value separator = , (comma, default)
-- field enclosure = unchecked (default) - Select the csv to import and run check data
Expected result
- when strings are too long, I expect to see an error after I run check data. I also expect that import get blocked until all error are fixed so no products gets created until the check data allows you to proceed with the import.
Actual result
Actual results consists in two issues:
- Check data returns no error, so I'm able to proceed with the import. The import fails saying that there's been a system error. But I shouldn't be able to proceed since my csv contains values (the strings too long) that causes my import to fail.
- If I go to my product list, I can see that all the products with too long strings have been created but all the values exept sku are empty (see screenshots). Since the import has failed, no product should have been created.
SCREENSHOTS:
Metadata
Metadata
Assignees
Labels
The issue has been fixed in 2.2 release lineThe issue has been fixed in 2.3 release lineGate 2 Passed. Manual verification of the issue description passedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedGate 1 Passed. Automatic verification of issue format passedGate 4. Acknowledged. Issue is added to backlog and ready for developmentThe issue has been reproduced on latest 2.2 releaseThe issue has been reproduced on latest 2.3 release