Using components: Salesforce Destination

Use the Salesforce destination component to store the output of a data flow in Salesforce Sales cloud object.

The destination component uses Salesforce Bulk API.


Select an existing Salesforce connection or create a new one (for more information, see Allowing Xplenty access to my data on Salesforce.)

Destination Properties

  • Target object - select the name of the target object in your Salesforce org. By default, if the table doesn't exist, it will be created automatically.

Operation type

Append (Insert only) - default behavior. Data will only be appended to the target object. Note that you can't insert data into the internal id field.

Upsert - inserts new data into the object and updates existing data according to the selected upsert key.
Upsert key - when operation type is upsert, you must map a key field and select it as the upsert key. This can be either the internal id field, or an external key field. The external key should not allow duplicate values.

Delete - deletes data in the destination object by Salesforce internal id field.

Advanced options

  • Batch size - number of records that are inserted to Salesforce in each batch (default 1000).
  • Maximum errors - maximum number of errors to tolerate when inserting data into Salesforce. Note that the actual number of errors may be greater than the maximum due to the parallel nature of the process.

Schema Mapping

Map the dataflow fields to the target object fields. When using the insert operation, fields defined as mandatory in the object must be mapped to input fields. When using the upsert operation, you should map the mandatory fields if you expect to insert data. If you use the internal id field as the upsert key, make sure to use null in the mapped field's value for new records. When using the delete operation, the internal id field must map to an input field.

Creating packages

  1. Creating a new package in New Xplenty
  2. Creating a workflow
  3. Working in the new package designer
  4. Validating a package
  5. Using components: Amazon Redshift Source
  6. Using components: Bing Ads Source
  7. Using components: Database Source
  8. Using components: Facebook Ads Insights Source
  9. Using components: File Storage Source
  10. Using components: Google Adwords source
  11. Using components: Google Analytics Source
  12. Using components: Google BigQuery Source
  13. Using components: Google Cloud Spanner Source
  14. Using components: MongoDB Source
  15. Using components: NetSuite Source
  16. Using components: Salesforce source
  17. Using components: Rest API Source
  18. Using components: Aggregate Transformation
  19. Using components: Assert Transformation
  20. Using components: Clone transformation
  21. Using components: Cross Join Transformation
  22. Using components: Distinct Transformation
  23. Using components: Filter Transformation
  24. Using components: Join Transformation
  25. Using components: Limit Transformation
  26. Using components: Rank Transformation
  27. Using components: Sort Transformation
  28. Using components: Union Transformation
  29. Using components: Window Transformation
  30. Using components: Sample Transformation
  31. Using components: Cube transformation
  32. Using components: Amazon Redshift Destination
  33. Using components: Database Destination
  34. Using components: File Storage Destination
  35. Using components: Google BigQuery Destination
  36. Using components: Google Spanner Destination
  37. Using components: MongoDB Destination
  38. Using components: Salesforce Destination
  39. Using components: Snowflake Destination
  40. Using Components: Rest API Destination
  41. Using and setting variables in your packages
  42. System and pre-defined variables
  43. Using pattern-matching in source component paths
  44. Using ISO 8601 string functions
  45. Using Expressions in Xplenty
  46. Xplenty Functions

Feedback and Knowledge Base