Importing a Dial List

Follow

Importing a Dial List

Import DialList is a section of the Database Management link. Here is a screenshot below showing this section.


When you import a DialList, there are 2 steps that you must complete to get the data into the campaign.

  1. Import the Database
  2. Map the Fields

Step 1: Import the Database

As you see in the screenshot above, you will need to click "Browse" and locate the database that you want to import. This database must be in .xls, .xlsx, .csv, or .txt format.

If you are using .xls or .xlsx, then multiple sheets will not work. The system will only take the first sheet it reads.

There is also strict validation on the Mime Type of the file. We do not support octet-stream which is the most common Mime Type that customers experience on failed imports.

Here is the list of Mime Types that we do support:

CSV FORMAT:

text/csv
text/comma-separated-values
text/plain

XLS FORMAT:

application/vnd.ms-excel
application/msexcel
application/x-msexcel
application/x-ms-excel
application/vnd.ms-excel
application/x-excel
application/x-dos_ms_excel
application/xls
application/xlt
application/x-xls

XLSX FORMAT:

application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
application/vnd.openxmlformats-officedocument.spreadsheetml.template
application/xlsx
application/xltx

I found an online tool that can help to detect MIME TYPES. If this link is broken at any point or returns a value that is supported AND you find the file to still fail on import, please notify support immediately so we can re-evaluate methods on making your experience better.

MIME TYPE DETECTOR (Opens in New Window)

Mime Types can be different from browser to browser so be sure to use the same browser that returns a matching value if you are diagnosing a file upload issue.

 

Step 2: Map the Fields

After you Import the database, you will see a screen that lets you map your database fields to the fields of the DialList that we use to store data. Here is a screenshot of some data I have mapped as an example.

I have carefully selected a database with the field names FirstName, LastName, Telephone, Latitude, Email, and State.

The reason I selected this specific order is to show you an example of the 4 rules that must be followed to map your data correctly. They are:

  1. Fields Names that we currently have can be matched to our database. (i.e. - John is a first name and we have a matching field called FirstName)
  2. Field Names you do not want to map can be set as Null so that the data can be ignored.
  3. Field Names we do not have can be mapped to as many as 10 Custom Fields such as Custom1, Custom2, etc.
  4. All Fields must be mapped from left to right.

To show you how the #4 rule can be an inconvenience when not followed, lets go back and change Johnson from LastName to Custom2.

You will notice that as soon as you change Johnson to Custom2, the following field which was previously set as Telephone now says Please Select. We would have to continue remapping from left to right on the spot we went back to edit. This is why we mention that all fields should be mapped from left to right. It avoids frustration as the code is sensitive to changes such as this.


Dealing with Failures Due to Octet-Stream

  • The most common issue with import failures on Step1 is the Content Type. Octet-Stream is a Content Type that is known to cause vulnerabilities with security and therefore we have blocked it from our allowed Content Types.
  • This can usually be fixed simply by using a different browser as some browsers force this Content-Type
  • Other methods to get around this include using the "Save As" feature of Microsoft Excel OR your word processing program to change the format to another type.
  • Support can convert files that you have trouble handling and provide you with a step by step on handling your specific formats so you can use them in the future with no issues.

 

 

 

 

Have more questions? Submit a request

Comments

Powered by Zendesk