{"section":"known-issues","requestedLocale":"en","requestedSlug":"new-collections-import-does-not-handle-non-existent-productid-import","locale":"en","slug":"new-collections-import-does-not-handle-non-existent-productid-import","path":"docs/en/known-issues/Catalog/new-collections-import-does-not-handle-non-existent-productid-import.md","branch":"main","content":"## Summary\n\n\n\nCurrently, in the new collection's admin, when the user tries to import a product sheet with a single product ID that does not exist in the account's catalog, the process fails as a whole without either indicating which line/productID has failed or even responding with an assertive message of the origin cause of the issue in the import attempt.\n\n\n\n## Simulation\n\n\n1) Go to an account's /admin/collections/\\{id\\}/ and click the import button.\n\n2) Choose the .XLS format and try importing a single line of a productID that currently is not present in the user's catalog .\n\n3) An unspecific error message will be prompted to the user, something like: \"Error. Your file was not imported. Try to import this file again\"\n\nThis process should either point out where the failure has occurred and/or process the other lines and not interrupt the whole attempt.\n\n(Ex: If I try to import 1000 lines and only 1 line is faulty (does not exist) I will not be able to import anything and without even knowing the reason why).\n\n\n\n## Workaround\n\n\nOption A) Check through roughly if all the productIDs in the sheet really do exist.\nOption B) Use the legacy collections module\nOption C) Use the API insertion"}