Overview
DataBlend supports a variety of data targets for creating, modifying, and deleting specific records in your databases.
Configuration
Setting |
Required/ Optional |
Description |
---|---|---|
Name |
Required |
Free text. |
Query |
Required |
Select the query that will generate the data for this target. |
Query Mode |
Required |
Select New unless you have a reason to select Latest or Specific. |
Credential |
Required |
Select a Database from the drop-down menu. |
Table Name |
Required |
Enter the Table name you wish to send data. |
Primary Key Name |
Required |
Enter the column name you wish to use to associate the data you are sending to the database with the corresponding table. A Primary key is a column within your table as well as within your query. This field does not currently support composite keys. If your primary key is an auto incrementing ID, be sure to also use the Auto Increment setting. |
Use Multi-Value Insert |
Optional |
Enable or disable the Use Multi-Value Insert toggle to insert multiple records into the database. This setting is useful when inserting (will not be available for updates) large volumes of net new records. The action DataBlend takes will batch the transactions for more efficient processing of data being sent into the database. If this is not selected, the rows will be created one at a time. Be mindful that when batching via this setting you may lose per row granularity in the logs which can impact troubleshooting so it is best practice to test your data target sufficiently before enabling this setting. |
Delete Records |
Optional |
Enable or disable the Delete Records toggle to delete records based on a unique id used in the created Query. This changes the action DataBlend is taking from an Insert Statement to a Delete Statement. |
Auto Increment |
Optional |
Enable or disable the Auto Increment toggle to auto increment data based on a unique ids used in the created Query. If the primary key is auto incremented, this setting will allow it to be excluded from the fields to insert/update. |
Disable Commit |
Optional |
Enable or disable the Disable Commit toggle to ensure a commit is disabled when sending data to a database. This starts a transaction but doesn't commit it and is useful for testing. |
Transaction per Row |
Optional |
Enable or disable the Transaction per Row toggle to create transactions per row in the database. |
Continue on Error |
Optional |
Enable or disable the Continue on Error toggle to send data regardless of error. This is useful in conjunction with transaction per row. If one records fails, others may still be inserted. |
History Retention (Days) allows users to decide how long they want the information from their data targets to be stored. This field is optional.
Timeout (seconds)
The Timeout section allows users to determine if they would like to timeout collections taking longer than a set number of seconds to collect data.
Skip If No Records Found
The “Skip if No Records Found” button is used to eliminate sending information to Data Targets unnecessarily. Simply enable the “Skip if No Records Found” toggle. The use of this toggle is optional.
Agent
The Agent drop-down for users to select any agent they have established. This is optional.
Run As
Run As allows users to select from a drop-down list of users to run the Workflow. This is optional. Please note that Run As is only available to Admin users. If a user is set as the Run As and then demoted to a Member, the user which demoted the Run As user will instead be set as the Run As.