
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.
I received this same error -- can you explain the solution to this, if found?
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.
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?
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!
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?
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.
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.
8 comments