Skip to main content Skip to complementary content

Creating a Job for upserting Salesforce data based on external IDs

Before you begin

  • An external ID custom field Account_External_ID has been added for the Account object in your Salesforce, which will be used to map the relationship with the Contact object.

  • An external ID custom field Contact_Talend_ID has been added for the Contact object in Salesforce, which will be used as the key column for upserting Contact object data.

Procedure

  1. Create a new Job and add a tSalesforceConnection component, three tSalesforceInput components, four tSalesforceOutput components, three tFixedFlowInput components, and four tLogRow components.
  2. Connect the first tSalesforceInput component to the first tSalelsforceOutput component using a Row > Main connection.
  3. Do the same to connect the first tFixedFlowInput component to the second tSalesforceOutput component, the second tFixedFlowInput component to the third tSalesforceOutput component, the third tFixedFlowInput component to the fourth tSalesforceOutput component, the second tSalesforceInput component to the third tLogRow component, and the third tSalesforceInput component to the fourth tLogRow component.
  4. Connect the third tSalesforceOutput component to the first tLogRow component using a Row > Main connection and to the second tLogRow component using a Row > Reject connection.
  5. Connect the tSalesforceConnection component to the first tSalesforceInput component using a Trigger > On Subjob Ok connection.
  6. Do the same to connect the first tSalesforceInput component to the first tFixedFlowInput component, the first tFixedFlowInput component to the second tFixedFlowInput component, the second tFixedFlowInput component to the third tFixedFlowInput component, the third tFixedFlowInput component to the second tSalesforceInput component, and the second tSalesforceInput component to the third tSalesforceInput component.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!