Discussion Forums

Import Question

 
New Member
1 post

A few questions as I test drive Solve360:

1. Do “Free” accounts have the ability to import CSV files? If so…

2. Each time I attempt to upload a file, I get an “Uploaded file is not a valid CSV file” error message. I am not using an export file from Goldmine, Highrise, Outlook (Express or 2003) or Solve360 (old) which seem ot be the only options. I have a plain text .CSV file created in Excel. I also tried creating a CSV from Numbers (Mac spreadsheet). I am using a Mac running 10.5.4.

3. Isn’t there an import choice for Excel .CSV, Excel .XLS or plain text CSV?

4. Does encoding matter? I’ve tried UTF-8 and Latin1.

Any suggestions?

Thx.

Mike

Avatar
Administrator
4123 posts

Greetings Mike,

Nice to *meet* you.  The “trick” is that the field names need to be located in exactly the same order and have exactly the same field names as they would normally have when exported by the specified file type.

I’ve attached a Outlook Express file as an example you can use.  This file was created in Excel and saved as a standard CSV file.  Try and import it using the Outlook Express (CSV Windows) option.

Then, if you match your fields in this order and save as a CSV you should be fine.

Please let me know how you make out.

File Attachments
Outlook express sample.csv  (File Size: 1KB - Downloads: 169)
New Member
3 posts

Hello,

I am testing out Solve360, and just set up an import, exactly matching the column sequence in the Outlook Express Sample.csv file, 50 records.

I left the column headings row 1 intact, and removed the (apparent) duplicate headings in row 2.

When I attempt to import, it analyzes the file, and finds “0” new contacts, 0 Update contacts, 0,0,0.  Suggestions?  do you want to see the file?

Thanks!

Avatar
Administrator
4123 posts

@BarbaraC1977 Sure email us the file to support@ and we’d be happy to take a look at it for you.

Avatar
Administrator
4123 posts
Engineering - Sep 25, 2008 02:36pm

The “trick” is that the field names need to be located in exactly the same order and have exactly the same field names as they would normally have when exported by the specified file type.

The Outlook Express and Outlook 2003 files will now still be recognized and processed even if they don’t have the complete field set i.e. you can exclude/remove columns you don’t need from the Outlook export file.