When imports fail, report the line number that broke
Issue #463
new
When I get a user report that an import failed, it might be an issue with the header line,
or some funky CSV formatting issues on line 10234. Scythebill has the info, just needs to collect it and show it to the user.
Comments (2)
-
reporter
-
reporter
Most of the location failures should get reported with d34369cb3
- Log in to comment
FWIW, this only applies to crash-and-burn when there’s a failed location or taxonomic line (locations being much much more common issues).