topic Re: tSalesforceInput failure in Talend Studio

tSalesforceInput failure

Anonymous — Sat, 16 Nov 2024 04:53:59 GMT

I have created a Talend Job in which I am establishing a connection with Salesforce using tSalesforceConnection and post that using tSalesforceInput to read data from Salesforce.

NOTE: In Advance settings of tSalesforceConnection, I have enabled Bulk Connection.

The issue is when I connect to Salesforce using my production credentials, the job completes successfully and Data from the Salesforce is printed successfully in tLogRow. But when connected with fqa credentials job fails with below error.

[statistics] connected
Exception in component tSalesforceInput_1
java.lang.NullPointerException
at org.talend.components.salesforce.runtime.SalesforceInputReader.executeSalesforceQuery(SalesforceInputReader.java:159)
at org.talend.components.salesforce.runtime.SalesforceInputReader.start(SalesforceInputReader.java:105)

However, when Bulk Connection option is disabled, then job is successful for both prod and fqa. I have already verified in Salesforce both accounts have permissions to support Bulk so this seems to be an issue from Talend Side.

Kindly help to resolve this issue.

Talend 6.3.1

Java 8

.Job DesigntSalesforceConnection-AdvSettingstSalesforceInput

Re: tSalesforceInput failure

JR1 — Wed, 21 Aug 2019 17:35:16 GMT

When you create and use a bulk connection, you have to set the Query Mode to "Bulk" in your tSalesforceInput component. Query Mode "Query" only works with non-bulk connections.

Re: tSalesforceInput failure

Anonymous — Wed, 21 Aug 2019 17:49:38 GMT

Thanks, it worked. But what I still couldn't understand is how come with my previous settings i.e. (Query Mode: Query ) with Prod account job was successful and why only for FQA it was failing ?

Re: tSalesforceInput failure

JR1 — Wed, 21 Aug 2019 18:16:14 GMT

Are you sure, you set "Bulk Connection" to true in the connection and "Query" in tSalesforceInput and then it worked? I am very certain that this cannot work.

Re: tSalesforceInput failure

Anonymous — Sun, 25 Aug 2019 14:12:59 GMT

Sorry, my bad. you are right