camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dhiraj Bokde (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-10193) add support for lookup field using an sObject external id
Date Wed, 03 Aug 2016 21:15:20 GMT

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

Dhiraj Bokde commented on CAMEL-10193:
--------------------------------------

[~ssatguru], please avoid editing comments in the future, as this floods mailboxes with duplicate
messages. 

I'll be glad to help out with the PR. But my initial feedback is that this solution won't
scale. The config approach only works when generating DTOs for a small number of SObjects.
Also, if the schema changes, this hand coded configuration becomes invalid. The plugin should
never generate DTOs that _might_ not work. Doesn't the master SObject description not list
all it's external id fields? The plugin should correlate (failing if the plugin config didn't
include SObject description for master SObject) descriptions and generate valid DTOs every
time. 

> 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.3.4#6332)

Mime
View raw message