Articles in this section

Fireside State Import Errors

Errors in the import process are common. Typically, it is because a row did not include a valid email address or because columns were not mapped to the correct eManager field during Step 2 of the import.

After your import has finished processing, you can click on the blue number of errors under the "Errors Count" column to get a better idea of what happened. 



 You can go back to your original data file, make any corrections and re-upload the entire file.  Or, if you wish only to retry importing the rows that caused errors, you can save the errors display page as a .CSV file and make the corrections there. To do this recommended alternative, right-click anywhere on the Errors Count page and select “Save As.”

 On the Save As screen, give your file a name and then change the Save as type to “All Files.” Once this is done, delete everything after the period in the File name (ex. .aspx or .txt) and replace it with the “.csv” file type ending. Then hit save. Before reimporting the document, you will need to go into this newly saved spreadsheet and fix all of the reported errors displayed in the Error column of your spreadsheet. Make sure that you do not import the Error column when attempting to upload the data. Below are some common errors.
 

File Error: You've completed step 1 of the import process and when you go to step 2 you notice that your headers are now showing and you see one large column with several characters as shown in the screenshot below. This is an indication the the file was not saved as a .CSV file. As a reminder, in order to import files into Fireside, you must save it as a .CSV file. 


Email Address (or other errors): The data ends with a question mark ? or is incomplete. Add another column in the CSV spreadsheet and call it "trimmed Emails." In each of the cells in that column, add the formula =TRIM(A2) where A2 is the cell reference for the email for the current row. Then use that column as the "email" column when you do the import.


 Birthdate Errors: "Birthdate Date Time argument was in wrong format: 19570524"

Dates must be in MMDDYYYY format to be imported into our system. You can convert it to an excel recognized date with the formula where A1 is the cell with the yyyyMMdd date (replace “A1” with the cell that needs editing):

=DATE(LEFT(A1,4),MID(A1,5,2),MID(A1,7,2))

To edit multiple cells in your spreadsheet with this formula, simply enter it in the first cell, and hit tab so that you know it’s working properly. Then click on that cell once again, and using the little box in the lower-right corner, drag the formula down so that all cells needing the change are filled. In the event that an individual never had a birthday in the spreadsheet to start, entering that formula will result in “VALUE!” being entered in the cell. Should this occur, please make sure to delete that out prior to importing, as this will also result in an error.


Zip Errors: Excel will often convert Zips to numbers (FYI: no need to correct or even import Zip+4s) which may or may not have the right number of digits. You can pad extra zeros onto the beginning with the following formula (replace “A1” with the cell number that needs editing):
=REPT(0,5-LEN(A1))&A1

________________________________________________________________________________________________________________________

Phone Number Errors: All phone numbers must be only 10 digits (ex. 2026215121). Extensions and characters     [Ex. (000) 000-000 ] will not be accepted.

________________________________________________________________________________________________________________________

Address Errors: The address must be in separate columns. Street 1, Street 2, City, State, Zip an d Zip+4 . Please note that in order to import an address, you must have the FULL address. You will not be able to import  a zipcode.

 

 As always, if you have any questions while you review import errors, feel free to reach out to us at help@fireside21.com or call us at 202-621-5121

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.