Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik and ServiceNow Partner to Bring Trusted Enterprise Context into AI-Powered Workflows. Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

[resolved] unparseable date in mysql to salesforce

I am going from mysql to salesforce and I am trying to insert records that have a date value in one of the fields. In mysql, the format is "yyyy-mm-dd hh:mm:ss" and I know the format that salesforce accepts in a datetime data type is "yyyy-mm-ddThh:mm:ss.000Z".
I am just doing a simple mapping in the tmap without any expressions. I get the following error when I run my job:
Exception in component tSalesforceBulkExec_1
java.lang.RuntimeException: Unparseable date: "2010-10-06T16:53:27.000Z"
at routines.system.ParserUtils.parseTo_Date(ParserUtils.java:164)

Thanks for the help in advance.
Labels (4)
14 Replies
Anonymous
Not applicable
Author

Hi,
I am using TalendDate.getCurrentDate() mapped to a variable as input string and on the right side i am setting the format as "yyyy-MM-dd'T'HH:mm:ss" which fails with parsing error on selecting parallel execution.
But the same gets executed if parallel execution is not selected.
Thanks,
Sanket
Anonymous
Not applicable
Author

Hi,
I also found out a case where the input is a date column from a table.
The values in the date column are not in sync..i.e few values are with timestamp and few values are without timestamp(just the date part) and hence it throws parsing error on selection of parallel execution.
On de selecting parallel execution the job executes without any error.
Any way by which such cases can be handled using parallel execution ?
Thanks,
Sanket
Anonymous
Not applicable
Author

Hi Sanket
This error is not caused by parallel execution, but the different date formats in the column, you need to check the length of the string which need to be parsed to a date, and use different date pattern to parse it. 
BR
Shong
Anonymous
Not applicable
Author

Hi,
Thanks for your reply.
Yes, the issue was due to different date formats.
I changed it to single common date format for all the date columns and hence it worked.
Thanks,
Sanket
Anonymous
Not applicable
Author

great, thanks for your feedback. 
BR
Shong