You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2021/04/03 09:24:00 UTC

[jira] [Updated] (CAMEL-16447) camel-salesforce - Error in parsing some fields in AbstractSObjectBase

     [ https://issues.apache.org/jira/browse/CAMEL-16447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-16447:
--------------------------------
    Summary: camel-salesforce - Error in parsing some fields in AbstractSObjectBase  (was: Error in parsing some fields in AbstractSObjectBase)

> camel-salesforce - Error in parsing some fields in AbstractSObjectBase
> ----------------------------------------------------------------------
>
>                 Key: CAMEL-16447
>                 URL: https://issues.apache.org/jira/browse/CAMEL-16447
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-salesforce
>    Affects Versions: 3.7.3
>            Reporter: Jawad Ahmad
>            Priority: Major
>
> org.apache.camel.component.salesforce.api.SalesforceException: Error parsing JSON response: Cannot deserialize value of type {{java.time.ZonedDateTime}} from String "2021-01-08": Failed to deserialize java.time.ZonedDateTime: (java.time.format.DateTimeParseException) Text '2021-01-08' could not be parsed at index 10
> at [Source: (ByteArrayInputStream); line: 1, column: 475] (through reference chain: com.r3.integration.salesforce.dto.Project__c["LastActivityDate"])
> There are few fields in the base class that is generated as ZonedDateTime but these are Dates hence parsing fails. This happens when we try to get objects which have activities tracking enabled against them in salesforce.
> AbstractSObjectBase :
> private ZonedDateTime LastActivityDate;
> private ZonedDateTime LastViewedDate;
> private ZonedDateTime LastReferencedDate;
> [https://help.salesforce.com/articleView?id=000326119&type=1&mode=1]
> I am testing this on camel version 3.7.3. But I have checked in 3.9 and the AbstractSObjectBase is the same there as well. So I guess this issue persists in the latest versions as well.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)