Loading

How to Fix the "Failed to Parse Date" Error for DateTime Fields in Salesforce Data Loader

Date de publication: Jun 2, 2026
Description

Error Description

When using Salesforce Data Loader to insert, update, or upsert records that include DateTime fields, you may encounter the following error:
Error converting value to correct data type: Failed to parse date: 1999-01-01T23:01:01+01:00
This error occurs when the DateTime value in your CSV file includes a timezone offset formatted with a colon separator (e.g., +01:00). While this format is valid for the Salesforce SOAP and Bulk APIs, Salesforce Data Loader has its own internal parser with unique formatting requirements that differ from the general API specification.

About DateTime Formatting in Data Loader

Although Salesforce API documentation lists 1999-01-01T23:01:01+01:00 as an acceptable DateTime format, Data Loader cannot parse the colon in the timezone offset portion. You must use one of the Data Loader-specific supported formats described in the Resolution section below.
For a full reference of valid DateTime formats accepted by the Salesforce APIs (not Data Loader), see the Additional Resources section.

Résolution

Supported DateTime Formats for Data Loader

Data Loader has its own set of supported DateTime formats that differ from the broader Salesforce API specification. For the specific example used in this article, the value 1999-01-01T23:01:01+01:00 must be reformatted using one of the following two approaches:
Option 1 — Remove the colon from the timezone offset:
1999-01-01T23:01:01+0100
Option 2 — Use the GMT prefix format:
1999-01-01T23:01:01GMT+01:00
Both formats are accepted by Data Loader and resolve the "Failed to parse date" error. For a complete reference of all DateTime formats supported by Data Loader, refer to the Data Types Supported by Data Loader article in the Additional Resources section below.

Numéro d’article de la base de connaissances

000383025

 
Chargement
Salesforce Help | Article