Tim Mousaw

@sconway That's perfect! RFC4180Parser is indeed what I want and worked without having to modify the output from Prisma Cloud! Hopefully, this output continues to conform to that standard. Thanks a bunch! I'm pretty sure you can close this bug as working to spec. Thanks again for your help!

@sconway - Thanks for your reply. Interesting that a CSV validator wouldn't point this out. This is the format that is coming from an external tool (Prisma Cloud). Knowing this, I can fix it before running it through my tool. I'm still a bit curious why it would validate as valid CSV. I'll have to check the rules the online validator is using to evaluate the CSV. The other thing I am curious about is why Excel can open this document and interpret it how one would "expect" (I use that term loosely)....

@sconway - Thanks for your reply. Interesting that a CSV validator wouldn't point this out. This is the format that is coming from an external tool (Prisma Cloud). Knowing this, I can fix it before running it through my tool. I'm still a bit curious why it would validate as valid CSV. I'll have to check the rules the online validator is using to evaluate the CSV.

Forgot to mention that I'm using the latest version of OpenCSV (5.5.2) as of the writing of this bug.

CSV input with comma between escaped quotes produces "Number of data fields does not match number of headers" exception