CSV importing wrong parsing about colossus HOT 3 CLOSED

Okay. The issue was that I only had email addresses and not names associated with them. The issue is that there is no way to repair this by pasting together the "broken" email lists (example : [email protected] becomes iloveyou as the email address and @gmail.com becomes the name). The only workaround is to force a second column in the CSV file and write names.

from colossus.

The idea here is that you instruct Colossus on how to import your data properly, from a csv file in any format.

On the select input on the header of the table you can define the mapping and tell Colossus what to do with this field. For now we have limited fields. Custom fields are on the roadmap.

from colossus.

Ah that's interesting. Thanks for reporting that!

It is indeed a bug. The way I'm using Python's csv utility, I try to guess what is the column separator (comma, semicolon, tabs, etc).

Because you only had emails in the csv file, the parser thought the "@" was the separator, so it ended up splitting the name and domain into two columns, instead of keeping only one column.

I'll release a fix soon

from colossus.