[jira] [Resolved] (CAMEL-11919) Salesforce REST API request headers not included in update,upsert,create and query operations

["Zoran Regvart (JIRA)" <ji...@apache.org>]

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

Zoran Regvart resolved CAMEL-11919.
-----------------------------------
    Resolution: Fixed

The issue was that if the header value was not given as {{String[]}} it would be converted to {{null}} and will not be set on the HTTP request.

> Salesforce REST API request headers not included in update,upsert,create and query operations
> ---------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-11919
>                 URL: https://issues.apache.org/jira/browse/CAMEL-11919
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-salesforce
>    Affects Versions: 2.20.0
>            Reporter: Dicken George
>            Assignee: Zoran Regvart
>             Fix For: 2.21.0
>
>
> There few Salesforce Rest API Http-Header parameters as decribed here.
> https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/headers.htm
> Sforce-Auto-Assign
> Sfore-Query-Options
> Sforce-Call-Options
> x-sfdc-packageversion-[namespace]
> and
> Sforce-Limit-Info : This is part of the SFDC response header.
> Out of these four, the "Sforce-Auto-Assign" header perform am implicit chain reaction in salesforce which causes unwanted repercussions which in certain operations needs to be controlled. For example, one of the issues,we have noticed, is that during an update operation if this header is not set to "FALSE", salesforce automatically updates the ownerID of the record although it was not included in the request. There are other side effects which we are currently not aware of. Therefore, the client would need the possibility to set this header parameter within their request to True or False manually. 
> However, currently only the approval requests accept these http headers from the client request, and we have found that it needs to be included in the update, upsert and create queries as well. 
> Sfore-Query-Options : this header is valid for query operations, in order to set the batchsize of your query response. We have implemented this as well since it could come in handy which performing batch / bulk queries.
> For the time being we have implemented only these two header parameters in the camel-salesforce project, however in the future the other two or all three headers could also be include with camel-salesforce to customization.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)