- Export data from a Data Source to a Data Target with user-specified mapping between attributes from the input Data Source to the attributes in the output Data Target.
- Use this task to write data to a Data Target such as Salesforce, Marketo, etc. at the end of a Job.
- Records that were updated after – will only export records updated after the date specified.
- Export all filtered records regardless of whether it was updated in the job – if this box is checked, all the records in the job will be exported. In order to export only modified records, leave the box unchecked.
Background: Openprise has built-in intelligence to reduce redundant work when exporting data. When this box is unchecked, Openprise checks each record selected by the task's filter to see if any target data attributes have been modified, and only exports those records that have been changed. For example, if the email field has been cleaned, and the clean result is the same as the original value, and that is the only field being exported, Openprise will omit updating that record if the box is unchecked. However, this checking does not always produce the desired results, so Best Practice is to check this box. Please check with your CSM for a detailed explanation of when this box can remain unchecked.
- Select Data Target – Select a Data Target to export data.
- To – fields in the Data Target
- From – fields from job to upload
Note: if an attribute containing an ID of the target system is supplied on the Export task, Openprise assumes the action should be an update to the target system. If there is no attribute supplied for ID, Openprise assumes the action should be the creation of a new record in the target system. Therefore, you cannot mix inserts and updates in the same task.
If an ID is not mapped, records will be created in the Target system. In the screenshot below, the Id attribute is not supplied which will create records.
The op_export_status field will contain "created".
If the Id attribute is supplied, the record will be updated in the target system.
The outputs will show "updated" in the op_export_status attribute.
Lastly, if an Id attribute is supplied, but the Id is not found in the target system, the following will occur.
You can see below that the Id attribute is mapped.
In the task outputs, the op_export_errors field will be populated with [ENTITY_IS_DELETED:entity is deleted:--]. This indicates that the record could not be located in the target system.
- If you supply an attribute for ID, Openprise assumes you are updating the record associated with the The Data Target must already exist.
- If the Data Target has required attributes, they are marked in red and must have mappings defined.
- In order to map an attribute from the Data Target, the attribute must be part of the Data Target configuration.
- It is possible to have multiple tasks output to the same Data Target, so be careful to avoid unintended collisions.
- The output data set will contain the following attribute fields which can be used for additional processing:
- op_export_errors – This is a text field that contains error messages that occurred (if any).
- op_export_reference – This contains a reference to the element in the target data set operated on by the task. For instance, if you are adding leads to Salesforce, this will contain the lead ID of the lead added.
- op_export_status – This contains the action performed: insert, update or delete
- op_export_success – Boolean field that contains yes/no depending on the success of the operation.
- op_export_time – Time stamp of the action taken by the task.
- For creating a CSV file in Google drive, Box or Dropbox, use the Upload File task.
- Push cleaned and normalized data back into SFDC, Marketo, Eloqua, Pardot, etc.
- Push enriched and cleaned data into a data warehouse (Redshift, RDS).
There are additional options under the Advanced Configurations section of the Export task.
- Records that were updated after .... This option checks all records in the job to see when any data element was updated, and will only push records to the target system if they were updated after the date value supplied.
- Prefer Bulk API (or Transactional API) while exporting data. optional, only for systems that support this. This option allows you to select either mode when updating records. Transactional APIs are generally faster than Bulk APIs. However the number of Transactional API calls allowed by a system is often limited. Additionally, sending a large number of updates via Transactional APIs can sometimes overwhelm a target system, resulting in failed updates.
- Number of records exported - use this option to limit the number of records updated per job run. For Salesforce users, this is not the same as supplying a batch size in data loader. If you would like to use this option, please consult Openprise support or your CSM for assistance.
Best Practice note: We recommend having 1 Export task write to the API source per job, since two export tasks to an API source may drop records between them.
If you have any additional questions, please feel free to contact us at firstname.lastname@example.org.