Talend Connect
Virtual Summit
JOIN US!
And visit the Customer
& Community Lounge.
May 27-28, wherever you are.

tSalesforceOutputBulkExec problem

Highlighted
One Star
One Star

tSalesforceOutputBulkExec problem

Hi
i need help to find the solution of my problem : i have a tSalesforceOutputBulkExec job that reject lines in a csv file (Row -> Reject) and i would like to do some jobs if at least 1 row is rejected (so maybe after the rejected job) and other stuff if all lines are inserted without error. And the problem is that i do not find the solution for having a branch that is trigger only if all lines are inserted without error.
The problem may be that the job is always OK even is all lines are rejected.
Maybe with an if statement but i dont know how.
thank you for your help.
Highlighted
Moderator

Re: tSalesforceOutputBulkExec problem

Hi,
i would like to do some jobs if at least 1 row is rejected (so maybe after the rejected job) and other stuff if all lines are inserted without error. And the problem is that i do not find the solution for having a branch that is trigger only if all lines are inserted without error.

For your further processing, you can use "RunIf" connection which triggers a subjob or component in case the condition defined is met.
Please take a look at document about:TalendHelpCenter:RunIf Connection Setting
Let us know if it is Ok with you.
Best regards
Sabrina

--
Don't forget to give kudos when a reply is helpful and click Accept the solution when you think you're good with it.

2019 GARTNER MAGIC QUADRANT FOR DATA INTEGRATION TOOL

Talend named a Leader.

Get your copy

OPEN STUDIO FOR DATA INTEGRATION

Kickstart your first data integration and ETL projects.

Download now

Best Practices for Using Context Variables with Talend – Part 2

Part 2 of a series on Context Variables

Blog

Best Practices for Using Context Variables with Talend – Part 1

Learn how to do cool things with Context Variables

Blog

Migrate Data from one Database to another with one Job using the Dynamic Schema

Find out how to migrate from one database to another using the Dynamic schema

Blog