Fluence Data Targets
Overview
DataBlend Supports the following data targets for creating and modifying records in Fluence.
Add
Update
Delete
Configuration
Setting | Required/ Optional | Description |
|---|---|---|
Type | Required | Fluence |
Query | Required | Select the query that will generate the data for this target. |
Query Mode | Required | Choose New unless you have a reason for choosing Latest or Specific. |
Credential | Required | Select a Fluence Credential from the list. |
Target Type | Required | Choose the Fluence collector type from the drop-down menu. |
Fluence Data Target Type | Required | Select from the pre-populated drop-down menu. |
Table Name | Required | Enter the desired Table Name to edit. |
To learn more about Fluence API requirements, please visit https://support.fluencetech.com/hc/en-us/articles/18722463191955-About-Fluence-s-REST-API.
Requirements
Add
The way the format of the Add data target is set up is to run a whole table as a batch. Fluence assumes the query that is generated is for a single table. All fields must exist in the table that are called out on the query.
Update
The parameters field is a list of column names and their values, and the remaining data is what the row of data will reflect.
Delete
If there is no parameters field or a blank one in the query, the entire contents of the table will be deleted.
Example Update Query
SELECT
'c1=1' "parameters"
, '1' "c1"
, '2' "c2"Parameters
If users add parameters, Fluence will only remove rows where those parameters are true. For example, we’re using c1=1, which is Column Name C1 contains value 1. Any row of data where C1=1, the row will be deleted. A user can include multiple column names and values, but cannot repeat a column name and a different value like C1=1|C1=2 .
Advanced
History Retention
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.
Schedule & Presets
Link to Schedule and Presets