July
June
May
April
March
February
January
 | 
|
 | Date issue when migrating with Salesforce Data LoaderCategory: Salesforce | |||||||||||||||||||||||||||||||
When migrating from a source system to Salesforce using the Apex Data Loader a date becomes the date it was minus 1 day. This happens for all of my objects that contains a date. The source system is MySQL but the data originally comes from Lotus Notes. Example: We are migrating customer information into an Account. In MySQL a query generates x rows where a specific date is one of the field values. The rows are via the Data Loader migrated into an Account using upsert.
Since this causes problems of different kinds for example when creating reports and just the fact that we get wrong data in the system I would like to have it fixed. Anyone know of a simple explanation? During our discussion internally we were thinking that it might be a time zone issue between Sweden and America. I have asked Salesforce for an explanation and I will update this post when I get it. |  | |||||||||||||||||||||||||||||||
| Tags: data loader, salesforce, migration, date | |||||
| Related blog entries: - Backing up your Salesforce data - How to disable and enable chatter and the new user interface - Importing a Salesforce field to a BigMachines attribute - Record Type ID: id value not valid for the users profile - Modifying the Salesforce Partner Edit page - List has no rows for assignement to SObject - The Thames Lodge in Staines - Creating an attachment instance in a testMethod - Where to change the Salesforce API version of a class - Prevent delete on a button or link in Salesforce - The salesforce id can be 15 or 18 digits long - Two ways of logging in with Salesforce Data Loader - Salesforce training podcasts - Standard Salesforce object prefixes - Copying a Salesforce object instance and keeping the id? - The select statement in Apex Data Loader and Apex Explorer sometime differs - Login error when logging into BigMachines - A look at BigMachines - Lessons learned when deleting large amounts of data with the Salesforce Dataloader - Swedish characters become strange characters during upsert with the Salesforce dataloader - Migrating from Lotus Notes - Learning about cloud computing and Salesforce - Basic date operations in JavaScript - A JavaScript date picker | |||||
| Created by Niklas Waller - 2009-06-01 22:01:24 |
| ||||
|
|
Comments: | |
| Comment posted 2009-06-24 07:46:56 by Niklas Waller A little update: I got an answer from Salesforce with an explanation on why it works the way it does regarding the above issue. The DataLoader is running on Java which uses the installed machines default time zone. In Salesforce Dates need to be imported in GMT so that dates will not appear a day out. Dates need to be loaded with a GMT time component in the following format: YYYY-MM-DDT00:00:00.000Z, e.g. for 18 July 2009 => 2009-07-18T00:00:00.000Z | |
| Comment posted 2009-09-02 15:41:03 by Hemant Solanki Hi... I m getting same error......while importing data using Apex Data Loader, Can please tell me in detail what I have to do next... Please Help....... | |
| Comment posted 2009-09-02 18:43:18 by Niklas Waller Hi Hermant, As I see it you have two options: 1. Import dates the way suggested by Salesforce which were explained in the first comment above, i.e. on the format YYYY-MM-DDT00:00:00.000Z, e.g. for 18 July 2009 => 2009-07-18T00:00:00.000Z 2. Manipulate the dates you are using to current date plus one day. But I would definately recommend option 1. Do you have the possibility to manipulate the data before importing it with the data loader in a good way? | |
| Comment posted 2009-09-06 09:56:46 by Hemant Solanki hi Niklas I tried option 1. I changed date format in my csv file into ISO YYYY-MM-DDT00:00:00.000Z, but still I am getting same result.........will I have to change format any other place...... | |
| Comment posted 2009-10-13 11:39:11 by Frank Great help - thanks. 
| |
| Comment posted 2009-11-17 12:42:11 by Colin Also running this in Daylight Saving (before Oct 25, 2009) hours seemed to make a one hour difference and put the dates back a day, if you used YYYY-MM-DDT01:00:00.000Z all would be well again (ie. 1AM on the date in question). Now, as we are out of Daylight Saving hours again plain old YYYY-MM-DDT00:00:00.000Z should work again. | |
| Comment posted 2010-01-19 13:51:14 by manish Please suggest how to import old dates in salesforce created date field using data loader because it is taking the sales force default created date . i want to overwrite the created date field by the one i m having in the csv | |
| Comment posted 2010-03-24 11:49:38 by Pardeep Chadha Manish, For Importing the legacy created date into sfdc Audit field 'CreatedDate', You have to enable 'Create Audit Fields' on your Org | |
