Salesforce Upsert All
The Salesforce Upsert All activity creates new objects or updates existing objects; uses a custom field to determine the presence of existing objects.
- If the external ID does not match, a new object is created.
- If the external ID is matched once, the existing object is updated.
- If the external ID is matched multiple times, an error is reported.
- When batch updating multiple objects where the external ID is the same for two or more objects in your batch call, those records are marked as errors in UpsertResult. The objects are neither created nor updated.
General
On the General tab, you can establish a connection to the Salesforce.com server.
The following table lists the configurations on the General tab of the Salesforce Upsert All activity.
Field | Module Property? | Description |
---|---|---|
Name | No | The name displayed as the label of the activity in the process. |
Salesforce Connection | Yes | The path to the Salesforce shared resource.
Click the
Choose/Create Default Resource icon
|
outputErrorMap | No |
Support the mapping of the error message from the output tab. Select the outputErrorMap checkbox to map the error messages from the output tab for UpsertAll activity. |
Description
On the Description tab, you can enter a short description for the Salesforce Upsert All activity.
Input
On the Input tab, you can specify input values for the Salesforce Upsert All activity.
The following table lists the input elements on the Input tab of the Salesforce Upsert All activity.
Input Items | Data Type | Description |
---|---|---|
connectionInfo (All fields in this section are optional.) | ||
serverUrl | String | The web address of the endpoint that is used by this operation. |
sessionId | String | The unique ID associated with this session. |
externalSessionIdUsed | Boolean | Specifies whether an external session ID is used (true) or not (false).
If the value is set to true, an external session ID is filled in the sessionId field. In this case, when the session has to be refreshed, the refreshed operation cannot be performed, and an exception is generated. |
upsert | ||
batchSize | Integer | Optional. When processing large amounts of data, the activity internally invokes several SOAP calls. This field is used to set the batch size for the number of records created or updated through an SOAP call.
The value must be set between 1 and 200. The default value is 200. When the input value equals -1, it is set to the default value. When the input value is greater than 200, it is set to 200. When the input value is less than 1 (except -1), it is set to 1. |
upsertSObjects | Each
upsertSObjects includes the following elements:
|
|
upsert_Optional (All fields in this section are optional.) | ||
_configData | Each
_configData includes the following element:
|
|
headers | Each
headers includes the following elements:
|
Output
On the Output tab, you can find the output value.
The following table lists the output elements on the Output tab of the Salesforce Upsert All activity.
Output Item | Data Type | Description | |
---|---|---|---|
upsertAllResponse | |||
result | created | Boolean | Indicates whether the record is created (true) or updated (false). |
errors | Complex | If errors occur during the activity, an array of error objects with the error code and description, is returned. | |
id | String | The ID of an sObject that you attempt to create. | |
success | Boolean | Indicates whether the Salesforce Create All activity has succeeded (true) or not (false). |
Fault
On the Fault tab, you can find the error code and error message of the Salesforce Upsert All activity. See Error Codes for more information about error codes and corrective actions to take.
Fault | Generated when |
---|---|
SalesforceExecuteSOAPMethodException | An error occurred when calling an SOAP method.
For example, wrong values are set in the Input fields or the Salesforce session has timed out. |
SalesforceLoginException | An error occurred when logging in to the Salesforce.com server. |
SalesforceConnectionNotFoundException | An error occurred when the external session ID is not used or the Salesforce connection is not configured correctly. |