You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/11/05 23:34:00 UTC

[jira] [Commented] (CAMEL-10193) add support for lookup field using an sObject external id

    [ https://issues.apache.org/jira/browse/CAMEL-10193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239769#comment-16239769 ] 

ASF GitHub Bot commented on CAMEL-10193:
----------------------------------------

GitHub user vspiliop opened a pull request:

    https://github.com/apache/camel/pull/2079

    Salesforce composite api external ids in body support

    Hope it is of use :-)
    
    1. Introducing support for Salesforce Composite REST API (https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_composite_composite.htm). I could not find any related jira..
    
    2. Extending the salesforce maven plugin to generate of DTO(s) for doing updates via Salesforce External Ids in the “body” json field. 
    ` 
             "body" : {
                  "Account__r":
                  {
                    "External_Id_Of_Account__c" : "123456"
                  } ,
                "AnotherField__c":"1234"
              }
    `
    Related jira is https://issues.apache.org/jira/browse/CAMEL-10193. The implementation is the proposed solution mentioned in the discussion.
    
    Thanks!!

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/vspiliop/camel salesforce-composite-api-external-ids-in-body-support

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/2079.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2079
    
----
commit d3f2aebba2e483414c788f11a977bc5f6e22e66e
Author: Spiliopoulos, Vassilis (ELS-CON) <v....@elsevier.com>
Date:   2017-11-04T11:24:31Z

    supporting composite API and externalIds in the json body

commit 56f6517047ed522cadd81deac3c0d3c629840473
Author: Spiliopoulos, Vassilis (ELS-CON) <v....@elsevier.com>
Date:   2017-11-05T22:37:01Z

    introducing salesforce composite api support and usage of external ids in json body

----


> add support for lookup field using an sObject external id
> ---------------------------------------------------------
>
>                 Key: CAMEL-10193
>                 URL: https://issues.apache.org/jira/browse/CAMEL-10193
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-salesforce
>    Affects Versions: 2.17.2
>            Reporter: Satguru Srivastava
>            Assignee: Dhiraj Bokde
>
> A SalesForce object can have a field of type called "lookup". 
> This field is used to by a record in a SalesForce object to reference a record in another SalesForce object. 
> The value of this field could be a string in which case it would be the record id of the other record or it could be an object in which case it would contain the other Object's external field name and its value in that other record. 
> Doing lookup/reference by external id is very useful  specially for insert/upsert operations as otherwise one has to maintain record id of each of the records in the other Object.
> Camel SalesForce component supports lookup by record id. 
> There is no support for the second type that is the external field name and value type.
>  
> See here for more information on this 
> https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/dome_upsert.htm
>  Section "Upserting Records and Associating with an External ID" 



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