Data targets are the Openprise objects that connect to your actual systems that store your data for the purpose of pushing data from Openprise to the target system. Your target system can be cloud systems such as Marketo, Salesforce or Eloqua; cloud drives such as Google Drive, Box, Dropbox or even FTP servers; and cloud databases such as Amazon Redshift or Amazon RDS MySQL databases.
To Create a Data Target
- Go to Data -> Data Targets
- Click on "Add Data Target"
- Data Target Name – required name needed in export jobs.
- Data Target Description – optional description.
- Data Target Administrators – required, only users with Administrator rights can export to the Data Target.
- Target Technology and Data Format – Target system (can be a sandbox or production environments).
- Add Account Information – Add a valid user for your system.
- Directory or Entity – Folder to write to for Cloud drives or Entity for Cloud Systems or Cloud Databases.
- Primary/Unique column – Unique ID: for Salesforce and Marketo this must be the ID field.
- List of Fields that are allowed to write – Fields in the Target system that Openprise can write to. Please note that Openprise requires the ability to update and create records for the object selected in the target.
- List of fields that can be blanked out by Openprise – If Openprise is able to write to a field, this gives explicit permission to blank out the field. If the field is not writable by Openprise, it cannot be blanked or changed by Openprise.
- Click save to save your data target configuration.
Export protection feature
Data Targets are the mechanism by which Openprise interacts with source systems and exports updates or changes to them. Therefore, poorly configured exports can adversely impact source systems. The export protection feature offers a way to prevent exports from happening when the number of records expected to export exceeds a certain amount. The amount is determined by a percentage of the total records in the export job's input data source. Upon triggering, the export is aborted and an email alert will be sent to the administrators of the data target of the job where the export occurs and of the bot where the job is scheduled. The export protection configuration is set to 20% by default when creating a new data target.
For example, if the job's input data source has 1000 records and the export protection configuration is set to 80%, then export protection will trigger when the export task exports 800 or more records.
Note that the export protection configuration should be set to 100% when used in export jobs that expect to export all records for each run. This includes use cases such as list loading or task creation.