The Salesforce connector is accessed from the Connectivity tab of the design component palette:
This connector is used to first configure a Salesforce connection to establish a connection with a Salesforce instance, and then to configure one or more Salesforce activities associated with that connection to use as a source or target within an operation:
Salesforce bulk activities are faster and scale better than non-bulk Salesforce activities, but should be used only if you do not need to use a transformation to change data prior to reaching the target.
NOTE: Cloud Studio supports Salesforce API version 47 from the Salesforce Winter '20 release.
Together, a specific Salesforce connection and its activities are referred to as a Salesforce endpoint. Once a connection is configured, activities associated with the endpoint are available from the Endpoints filter:
It is recommended to use a custom field in Salesforce to associate records with an external ID for Jitterbit. These steps show how create a custom field in Salesforce on the Account object to create an external ID called "Jitterbit_Account_ID":
You should be returned to the Fields & Relationships screen for the Account object. Verify that you see the new custom field with the same parameters as shown below.
For more information, refer to Salesforce's documentation for Create Custom Fields.
A number of Salesforce functions can be used within scripts to provide login and session information and lookups for Salesforce instances, including these:
In addition, certain Jitterbit variables are provided specifically for use with Salesforce endpoints, including these: