Best answer

Salesforce lead setup - 'cannot deserialize instance of time' error

  • 17 September 2021
  • 3 replies
  • 921 views

Userlevel 3
Badge

I have created a Zap to setup a lead on Salesforce. I pass the time value in the “03:00:00 PM” format to the time field of the Salesforce lead. But Zapier takes it in the “2021-09-17T15:00:00-05:00” format. Why?

And then, it throws the following error.
Could not create record of the "Lead" object: Cannot deserialize instance of time from VALUE_STRING value 2021-09-17T15:00:00-05:00 or request may be missing a required field at [line:1, column:287]

Attaching screenshots.

Time value that I pass.

 

Time value that Zapier takes and throws an error.

 

Looking for help. Thank you in advance!

icon

Best answer by christina.d 15 November 2022, 02:19

View original

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

3 replies

Userlevel 7
Badge +14

Hi @thinker500 

Salesforce help article about expected datetime formats: https://help.salesforce.com/s/articleView?id=000325035&type=1

Try using a Formatter > Date / Time > Format step: https://zapier.com/help/create/format/modify-date-and-time-formats-in-zaps

 

Additional info about the Date/Time field format in Zaps: https://zapier.com/help/create/basics/different-field-types-in-zaps#step-1

Userlevel 7
Badge +11

Just wanted to pop in here as saw we have an existing bug report open for this very same error, where a datetime rather than a time value is passed to Salesforce.

I’ve added @thinker500 to the list of affected users. While we don’t have an ETA on when it will be resolved we’ll be sure to email as soon as it has been. :)

Userlevel 7
Badge +9

Just wanted to pop in here as saw we have an existing bug report open for this very same error, where a datetime rather than a time value is passed to Salesforce.

I’ve added @thinker500 to the list of affected users. While we don’t have an ETA on when it will be resolved we’ll be sure to email as soon as it has been. :)

Hey there, squad! I wanted to swing by and let ya’ll know a fix for this is now live and the bug officially closed. 🎉

Thanks for for your patience on this!