Biggest issue I have for Excel creating CSV files, is that Excel has a habit of adding empty rows at the bottom if the Excel file had rows deleted. The CSV will end up with rows with just commas on them.
The ERP we use will choke on those empty rows. I then need to remove them up in an editor.
@mdione @RussEby Marcos, don't be that guy... People have to work around stuff they have little control over and had no choice having to use most of the time. I can imagine why an old ERP is not expecting "empty" comma filled lines, and then, some "dev around ERPs" stuff I've seen is like adversarial adaptations, because the ERP vendor doesn't want you to integrate freely with it.
Most of my CSVs, I create using Python and don't have issues.
Where the problem comes up is when others are trying to load a CSV and it shows 400 'failures' out of 900 and they were only trying to load 500 rows.
I have to explain that the 'failures' are the empty rows and can be ignored. Unless some of the records did fail and then I need to filter the results for them so they can corrected and reuploaded.