August 15, 2023

tSalesforceBulkExec – Docs for ESB 6.x


Gains in performance while carrying out the intended data operations into your

The tSalesforceOutputBulk and tSalesforceBulkExec components are used together
in a two step process. In the first step, an output file is generated. In the second
step, this file is used to feed the Salesforce database. These two steps are fused
together in the tSalesforceOutputBulkExec component. The advantage of using two separate
steps is that the data can be transformed before it is loaded in the database.

tSalesforceBulkExec Standard properties

These properties are used to configure tSalesforceBulkExec running in the Standard Job framework.

The Standard
tSalesforceBulkExec component belongs to the Business and the Cloud families.

The component in this framework is generally available.

Basic settings

Property Type

Select the way the connection details
will be set.

  • Built-In: The connection details will be set
    locally for this component. You need to specify the values for all
    related connection properties manually.

  • Repository: The connection details stored
    centrally in Repository > Metadata will be reused by this component. You need to click
    the […] button next to it and in the pop-up
    Repository Content dialog box, select the
    connection details to be reused, and all related connection
    properties will be automatically filled in.

This property is not available when other connection component is selected
from the Connection Component drop-down list.

Connection Component

Select the component whose connection details
will be used to set up the connection.

Connection type

Select the type of the connection from the drop-down list, either Basic or OAuth.

  • Basic: select this option to access by entering your user ID and password. With this option selected,
    you need to specify the following properties:

    • User Id: the ID of the user in

    • Password: the password associated
      with the user ID.

    • Security Key: the security

  • OAuth: select this option to access by entering your consumer key and consumer secret. This way, your
    user name and password will not be exposed, but extra work is

    With this option selected, you need to specify the following

    • Client Id and Client Secret: the OAuth consumer key and consumer
      secret, which are available in the OAuth Settings
      area of the Connected App that you have created at

    • Callback Host and Callback Port: the OAuth authentication
      callback URL. This URL (both host and port) is defined during the
      creation of a Connected App and will be shown in the OAuth
      area of the Connected App.

    • Token File: the path to the token
      file that stores the refresh token used to get the access token without

Module Name

Click the […] button next to the field and in the
dialog box displayed, select the module that will be used or select the Use custom object check box and specify the module name in the
Object Name field.

Schema and Edit schema

A schema is a row description. It defines the number of fields (columns) to
be processed and passed on to the next component. The schema is either Built-In or stored remotely in the Repository.

Click Edit schema to make changes to the schema.
If the current schema is of the Repository type, three
options are available:

  • View schema: choose this option to view the
    schema only.

  • Change to built-in property: choose this
    option to change the schema to Built-in for
    local changes.

  • Update repository connection: choose this
    option to change the schema stored in the repository and decide whether to propagate
    the changes to all the Jobs upon completion. If you just want to propagate the
    changes to the current Job, you can select No
    upon completion and choose this schema metadata again in the [Repository Content] window.

Click Sync columns to retrieve the schema from
the previous component connected in the Job.

This component offers the
advantage of the dynamic schema feature. This allows you to retrieve unknown columns
from source files or to copy batches of columns from a source without mapping each
column individually. For further information about dynamic schemas, see
Talend Studio

User Guide.

This dynamic schema
feature is designed for the purpose of retrieving unknown columns of a table and is
recommended to be used for this purpose only; it is not recommended for the use of
creating tables.

Output Action

Select one of the following operations to be
performed from the drop-down list.

  • INSERT: insert one or more new records into

  • UPDATE: update one or more existing records
    in Salesforce.

  • UPSERT: create new records and update
    existing records. In the Upsert Key Column
    field dispalyed, specify the key column for the upsert operation.

  • DELETE: delete one or more records in

Bulk File Path

Specify the path to the file that stores the data to be processed.

Advanced settings

Salesforce URL

Enter the Webservice URL required to connect to
the Salesforce database.

Need compression

Select this check box to activate SOAP message compression, which can result in increased
performance levels.

Trace HTTP message

Select this check box to output the HTTP interactions on the console.

Client Id

Enter the ID of the real user to differentiate between those who use the same account and
password to access the Salesforce website.

Timeout (milliseconds)

Enter the intended number of query timeout in

Use Proxy

Select this check box to use a proxy server, and in the Host, Port, User Id, and Password fields displayed, specify
the connection parameters of the proxy server.

Concurrency Mode

Select the concurrency mode for the job.

  • Parallel: process batches in parallel

  • Serial: process batches in serial

Rows to Commit

Specify the number of lines per data batch to
be processed.

Bytes to Commit

Specify the number of bytes per data batch to
be processed.

Wait Time Check Batch State (milliseconds)

Specify the wait time for checking whether the
batches in a Job have been processed until all batches are finally processed.

tStatCatcher Statistics

Select this check box to gather the Job processing metadata at the Job level
as well as at each component level.

Global Variables

Global Variables

NB_LINE: the number of rows read by an input component or
transferred to an output component. This is an After variable and it returns an

NB_SUCCESS: the number of rows successfully processed.
This is an After variable and it returns an integer.

NB_REJECT: the number of rows rejected. This is an After
variable and it returns an integer.

ERROR_MESSAGE: the error message generated by the
component when an error occurs. This is an After variable and it returns a string. This
variable functions only if the Die on error check box is
cleared, if the component has this check box.

A Flow variable functions during the execution of a component while an After variable
functions after the execution of the component.

To fill up a field or expression with a variable, press Ctrl +
to access the variable list and choose the variable to use from it.

For further information about variables, see
Talend Studio

User Guide.


Usage rule

This component is more commonly used with the tSalesforceOutputBulk component. Used together, they
gain performance while feeding or modifying information in


The bulk file to be processed should be .csv

Due to license incompatibility, one or more JARs required to use this component are not
provided. You can install the missing JARs for this particular component by clicking the
Install button on the Component tab view. You can also find out and add all missing JARs easily on the
Modules tab in the
perspective of your
studio. You can find more details about how to install external modules in Talend Help Center (

Related Scenario:

Document get from Talend
Thank you for watching.
Notify of
Inline Feedbacks
View all comments
Would love your thoughts, please comment.x