Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Difference between Sales Force OutPut Components

Hi,

 

I am trying to learn SalesForce Integration. Can anyone please tell me difference between:-

 

  1. tSalesForceOutPut
  2. tSalesForceOutPutBulkExec

 

Regards

Tarunjit Singh

Labels (3)
23 Replies
TRF
Champion II
Champion II

Untick the option "Cease on Error" if you din't want the job to stop in case of error.

You may also refer to this post where I tried to explain how it works.

Anonymous
Not applicable
Author

Hi,

  

Thanks for the answer. Job is not now not breaking but no response from Sales Force is coming, i.e in main flow and reject flow it is showing 0 rows.

 

It seems that if we use tSalesForceOutPutBulkExec then if a record is rejected i.e. got failed while trying to add then others records are not effected. e.g. 1 out of 5 records are rejected then remaining 4 will get added in to Sales Force.

 

Where as if we use tSalesForceOutPut then if a record is rejected i.e. got failed while trying to add then others records will also be effected. e.g. 1 out of 5 records are rejected then remaining 4 will also not get added in to Sales Force and also there will also be no response from Sales Force regarding success and failure as mentioned in my first paragraph.

Anonymous
Not applicable
Author

Hi,

 

I think I resolved the problem by setting Commit Level To1. Now tSalesForceOutPut is able to add 4 success records in to Sales Force and also I got response for failure.

 

But I think it will be slow as Commit Level is set to 1. As transaction will be created for each record. Please confirm. 

Anonymous
Not applicable
Author

Hi,

 

Here is my understanding as per your comment.

 

  1. Suppose there are 50 records being added from tSalesForceOutPutBulkExec and few of the records got failed due to sales force internal error. In that scenario whole of the batch will get failed.
  2. Suppose there are 50 records being added from tSalesForceOutPut and few of the records got failed due to sales force internal error. In that scenario not whole of the batch will get failed only those of the records will get failed.

Please let me know if my understanding is correct.

 

 

manodwhb
Champion II
Champion II

Yes correct..

Anonymous
Not applicable
Author

Hi,

 

So in case of bulk addition using tSalesForceOutPutBulkExec if there are 100 records and batch size of 50 and first batch got failed due to Sales Force Internal issue then on response I will receive 50 records for success flow and 50 records for reject flow.

 

Please confirm.

manodwhb
Champion II
Champion II

if the any one batch has issue then all the records wil be failed in BULK mode.

Anonymous
Not applicable
Author

Hi,

 

It means if one batch fails then all the records of all the batches will have the same error message received from sales force.

manodwhb
Champion II
Champion II

you will get below kind of error.

 

Exception in component tSalesforceOutputBulkExec_2_tSalesforceBulkExec
java.io.IOException: [AsyncApiException exceptionCode='InvalidBatch'
exceptionMessage='Records not processed'
]

at org.talend.components.salesforce.runtime.SalesforceBulkExecReader.start(SalesforceBulkExecReader.java:76)
at atos.datamig_opportunityitem_unify_1_0.DataMig_OpportunityItem_Unify.tSalesforceInput_3Process(DataMig_OpportunityItem_Unify.java:21166)
at atos.datamig_opportunityitem_unify_1_0.DataMig_OpportunityItem_Unify.tHashInput_10Process(DataMig_OpportunityItem_Unify.java:18922)
at atos.datamig_opportunityitem_unify_1_0.DataMig_OpportunityItem_Unify.tHashInput_1Process(DataMig_OpportunityItem_Unify.java:14040)
at atos.datamig_opportunityitem_unify_1_0.DataMig_OpportunityItem_Unify.tHashInput_18Process(DataMig_OpportunityItem_Unify.java:10458)
at atos.datamig_opportunityitem_unify_1_0.DataMig_OpportunityItem_Unify.tFileList_2Process(DataMig_OpportunityItem_Unify.java:4397)
at atos.datamig_opportunityitem_unify_1_0.DataMig_OpportunityItem_Unify.tSalesforceConnection_3Process(DataMig_OpportunityItem_Unify.java:3942)
at atos.datamig_opportunityitem_unify_1_0.DataMig_OpportunityItem_Unify.tSalesforceConnection_1Process(DataMig_OpportunityItem_Unify.java:3713)
at atos.datamig_opportunityitem_unify_1_0.DataMig_OpportunityItem_Unify.tLoop_1Process(DataMig_OpportunityItem_Unify.java:3416)
at atos.datamig_opportunityitem_unify_1_0.DataMig_OpportunityItem_Unify.tJava_3Process(DataMig_OpportunityItem_Unify.java:2781)
at atos.datamig_opportunityitem_unify_1_0.DataMig_OpportunityItem_Unify.tFileList_1Process(DataMig_OpportunityItem_Unify.java:1923)
at atos.datamig_opportunityitem_unify_1_0.DataMig_OpportunityItem_Unify.tJava_15Process(DataMig_OpportunityItem_Unify.java:23526)
at atos.datamig_opportunityitem_unify_1_0.DataMig_OpportunityItem_Unify.tFTPGet_1Process(DataMig_OpportunityItem_Unify.java:23358)
at atos.datamig_opportunityitem_unify_1_0.DataMig_OpportunityItem_Unify.tFTPConnection_1Process(DataMig_OpportunityItem_Unify.java:23019)
at atos.datamig_opportunityitem_unify_1_0.DataMig_OpportunityItem_Unify.tJava_12Process(DataMig_OpportunityItem_Unify.java:22781)
at atos.datamig_opportunityitem_unify_1_0.DataMig_OpportunityItem_Unify.tJava_9Process(DataMig_OpportunityItem_Unify.java:22613)
at atos.datamig_opportunityitem_unify_1_0.DataMig_OpportunityItem_Unify.tFixedFlowInput_2Process(DataMig_OpportunityItem_Unify.java:24047)
at atos.datamig_opportunityitem_unify_1_0.DataMig_OpportunityItem_Unify.tJava_10Process(DataMig_OpportunityItem_Unify.java:24299)
at atos.datamig_opportunityitem_unify_1_0.DataMig_OpportunityItem_Unify.tSetProxy_1Process(DataMig_OpportunityItem_Unify.java:37203)
at atos.datamig_opportunityitem_unify_1_0.DataMig_OpportunityItem_Unify.runJobInTOS(DataMig_OpportunityItem_Unify.java:37606)
at atos.datamig_opportunityitem_unify_1_0.DataMig_OpportunityItem_Unify.main(DataMig_OpportunityItem_Unify.java:37298)
Caused by: [AsyncApiException exceptionCode='InvalidBatch'
exceptionMessage='Records not processed'

Anonymous
Not applicable
Author

Hi,

 

From the error message it seems that in such case when a batch will fail then the complete job will get fail. That is flow will not move forward from tSalesForOutPutBulkExec. Please confirm.