Using Components: Salesforce Destination (Beta)

Use the Salesforce Destination component to store the output of your package into a Salesforce object.

To define the Salesforce destination:

  1. Add a Salesforce Destination component at the end of your dataflow.
  2. Open the component and name it.

Destination settings

  1. Define the parameters for connecting to your Salesforce as follows:
    • salesforce connection - either click the drop-down arrow and select an existing connection, or click (create new) to create a new connection.
    • destination object - select the target object in your Salesforce org.
    • salesforce fields - select fields from the target object to map data-flow fields into, or click "auto fill fields" to map fields automatically (see below).
    • operation type - the method of data manipulation in Salesforce:
      • insert - appends data into the object. Note that you can't insert data into the 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.
    • batch sizenumber of records that are inserted to Salesforce in each batch (default 1000).
  2. Map fields from your dataflow to fields in the target object. You can click the Auto-fill fields icon to automatically map data-flow fields to object fields according to name. When mapping fields to table columns, take into consideration the mapping of data types. If you map mismatched data types, the job will fail. When you map a data-flow field into a relation field, you should also select the relation field in the reference object. This can be either the internal Salesforce id field, or an external key. The external key in the referenced object should not allow duplicate values.

Creating packages

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

Feedback and Knowledge Base