0

Character decoding error occurred. Set correct charset. Current charset is UTF-8.

I always thought that UTF-8 was the standard for encoding our Excel CSV upload files, so not sure why this is happening!

8 comments

Date Votes
-1
Avatar
Patricio Carcani
Hello Greer, CSV input file should be in UTF-8, this is the standard encoding for dataloader.io as you said.

In this case the error you see is related to the format of the field you are attempting to import. I would recommend 1. check the requirements for that field in your SFDC; 2 export the sample data and use it as a template.
0
Avatar
Nicholas Blanchard

I received this same error -- can you explain the solution to this, if found?

-1
Avatar
Patricio Carcani

Hi Nicholas,

I would suggest to export sample data and use it as a template (compare the format of fields exported with your own csv input file). You can also try to encode your file in UTF-8 with BOM (to prevent special characters failures).

Let us know the results!

Regards.

0
Avatar
Nicholas Blanchard

Ariel,

Can you help us a little more on this one? We are having trouble finding the issue with the file. Here is the task: 7451202 can you please take a look?

-1
Avatar
Patricio Carcani

Hello Nicholas,

In order to help you we will need the same CSV input file that you are using (or a sample that reproduce this error). Please send it to us: info@dataloader.io

Regards!

0
Avatar
Bart Hoekstra

I have exported a data set from our production server to import in a Sandbox and I get this error when importing the data into the Sandbox.  I'm unsure what you mean by use it as a template.  Could you explain?

 

0
Avatar
Paul Ludwig

I am trying to import new Contacts, - the .csv file was build using plain text and I continue to get "Character decoding error occurred. Set correct charset. Current charset is UTF-8"  I copied the plain text to Notepad and then saved it as a .csv file, same error.  Earlier I updated Contacts using the exact same process and it worked.  Is Dataloader experiencing some kind of technical failure?  I have no idea what next step to take.

1
Avatar
Pablo Cadoppi

Hi Paul,

Probably the encoding was not really UTF-8 but something slightly different causing dataloader.io to interpret it as UTF-8 while it is not. It is possible that the characters in the file won't cause any problem but if there is some special character you will get an encoding error.

I would suggest to open the file using some advanced plain text editor tool like Sublime Text or Notepad++ and save the file again using UTF-8. This should solve the issue.

Regards,
Pablo

Please sign in to leave a comment.