Salesforce Upsert

The Salesforce Upsert step updates existing records and inserts new records into Salesforce using the Salesforce web service.

See also

• Salesforce Input

• Salesforce Insert

• Salesforce Update

• Salesforce Delete

General

• Step name: Specify the unique name of the Salesforce Upsert step on the canvas. You can customize the name or leave it as the default.

Connection

Option	Description
Salesforce webservice URL	URL of the Salesforce web service. The URL depends on the Salesforce API version used by PDI.
Username	User name for authenticating to Salesforce.
Password	Password followed by your security token (for example, PASSWORDTOKEN).
Test connection	Verifies that the connection can be made using the configured settings.

Upsert settings

Option	Description
Time out	Timeout in milliseconds. Default is 60000.
Use compression	Select to use .gzip compression between PDI and Salesforce.
Rollback all changes on error	Select to roll back changes unless all records process successfully. If selected, records with errors are marked as failed in the results. If cleared, partial success is allowed.
Batch size	Maximum number of records to collect before committing the upsert. Default is 10.
Module	Salesforce module/object to upsert into (default is Account). This list is populated after a successful Test connection.
Upsert comparison field	Salesforce field used to determine whether to update an existing record or insert a new one. Default is Id.

Output

• Salesforce ID fieldname: Field that contains the Salesforce ID of updated/inserted records. Default is Id.

Fields

Use the Fields table to map PDI stream fields to Salesforce fields.

Select Get fields to populate the table with input fields from the stream.

Column	Description
Module field	Salesforce object field name.
Stream field	Incoming PDI field name.
Use external id?	Set to Y or N to indicate whether the field links to an external ID. To resolve an external ID, Salesforce uses:

ObjectName.ColumnName/Relationship |

(Optional) Select Edit mapping to define custom mappings.

Metadata injection support

All fields of this step support metadata injection. You can use this step with ETL metadata injection to pass metadata to your transformation at runtime.