This would help when there are commas within a single field's data that you're trying to import rather than breaking the import because Aha is expecting another row due to the comma. It would also save me several swear words.
Thank you for your idea. Currently the CSV import allows for fields with commas. When importing you can map each field in your import to the corresponding Aha! field. Upon import, the values with commas will be imported as expected into the mapped Aha! field.
I imported several worksheets yesterday and when the value I wanted to import (matching a custom table) included commas, my import failed each time.