camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CAMEL-11919) Salesforce REST API request headers not included in update,upsert,create and query operations
Date Tue, 24 Oct 2017 07:27:00 GMT


ASF GitHub Bot commented on CAMEL-11919:

oscerd commented on issue #2047: CAMEL-11919 Adding new feature
   @DG007 do you need to add something to the fix by @zregvart ? Can we close this and eventually
you'll open a new PR with improvements? Thanks.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Salesforce REST API request headers not included in update,upsert,create and query operations
> ---------------------------------------------------------------------------------------------
>                 Key: CAMEL-11919
>                 URL:
>             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.
> 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

View raw message