Staring at a CSV file full of data looking for that one extra comma or stray double quote or some out of place Unicode character that might exist but you don't know which of the hundreds it could be feels like staring into a pit of despair.

I feel for you. Can you script it?

@chadd17 I wish. But it is frequently an unknown pattern that a human being has to figure out, and it differs every time. It could be fixed if the third party developer weren't ignoring the problem, and my emails to him about it, and just sanitize his data before outputting the file.

@stackodev poor guy :/ have a ++

frequency analysis on each row on separator characters and print out the special ones?

linters are your friend. And there are many online for free

@raldo94 maybe. We are switching vendors soon so all of this will be a thing of the past in a week or two with a REST API upgrade. Might as well just stick it out until then.

@Baxtex I'm not always sure what random Unicode char is causing the CSV to fail to import each time.