Salesforce connector troubleshooting in Jitterbit Integration Studio

Overview

This topic provides troubleshooting information specific to the Salesforce connector. It may also apply to the Salesforce Service Cloud and ServiceMax connectors.

Testing and logging

If you experience issues with the Salesforce connector, these troubleshooting steps are recommended:

1. Ensure the Salesforce connection is successful by using the Test button in the configuration screen. If the connection is not successful, the error returned may provide an indication as to the problem.

2. Check the operation logs for any information written during execution of the operation.

3. Enable operation debug logging (for cloud agents or for private agents) to generate additional log files and data.

4. If using private agents, you can check the agent logs for more information.

5. For additional troubleshooting considerations, see Operation troubleshooting.

Error fetching data during activity configuration

The following error may be returned when fetching data during activity configuration:

Invalid username, password, security token; or user locked out. [INVALID_LOGIN]

One reason for this error is that the password provided in the Salesforce connection uses extended ASCII characters, such as £. In this case, the connection test may still be successful. If you receive this error and are using special characters in the password, try changing the password.

Record limits imposed by the Salesforce API

Many web service APIs have size limitations, and Salesforce's API is no exception. If you are running into such limits, you may want to use chunking to split the source data into multiple chunks.

Use chunking

In Jitterbit Integration Studio, chunking can be enabled for each operation under the operation options.

When using chunking on an operation where the source is a Salesforce activity, the data will be chunked in the transformation, not when the data is retrieved. The target data will first be written to numerous temporary files (one for each chunk). These files will then be combined into one target file.

Similarly, when using chunking on an operation where the target is a Salesforce activity, the transformation is performed on each chunk separately, with each source chunk producing one target chunk. The resulting target chunks combine to produce the final target.

For example, a Salesforce upsert accepts only 200 records for each call. With sufficient memory, you could configure the operation to use a chunk size of 200. The source would be split into chunks of 200 records each, and each transformation would call the web service once with a 200-record chunk. This would be repeated until all records have been processed. The resulting target files would then be combined.

When using chunking with Salesforce bulk activities, it is recommended to change the default chunk size of 200 to a large number, such as 10,000.

For instructions and best practices on using chunking, see Operation options.