Insert / Update

Description:

Insert / Update writes rows to a database table by first looking up each row using specified key fields. If a matching record exists, it updates the row; if no match is found, it inserts a new row. Use this step when your workflow needs to maintain a target table that stays current with incoming data — for example, keeping a customer master table in sync with daily feed files or maintaining a product catalog from periodic imports.

Configurations:

Field Name	Description
Step Name	Name of the step. This name has to be unique in a single workflow.
Connection	Name of the database connection on which the target table resides.
Target Schema	The name of the Schema for the table to write data to.
Target Table	Name of the target table.
Commit Size	The number of rows after which to commit.
Don’t perform any updates	Select this checkbox to perform only insert.
The keys to lookup the values:
Table field	Field in the table to lookup
Comparator	Select from the list of comparators
Stream field1	Table field is compared with Stream field1 using comparator
Stream field2	Table field is compared with Stream field2 using comparator
Update Fields:
Table field	The field to be updated in the table
Stream field	The field in the stream used to update the table field.
Update	Select Y/N to confirm update
Plain Text	When a field receives a secret status in an upstream step, that status automatically travels with the data to the step. Use the Plain text setting to control how the step handles this incoming secret data. Select Y to write the actual, unmasked value of the incoming secret field to the output target. Select N (the default setting) to safely remove the secret field from the output entirely. The step never writes secret values to the target, and the step excludes the column from the INSERT or UPDATE statements. The target database then applies its own default value or uses NULL. Important: · Select Y only when the target system requires the actual value and no secure alternative exists. Whenever possible, configure downstream tools to read credentials directly from a credential parameters or credential attribute rather than writing sensitive data to an output file or database. · The system saves the Y selection directly within the workflow file. This ensures security reviewers can easily audit the workflow and identify any field configured to expose plain text data. · Ensure the secret status remains intact before the data reaches the output step. Modifying the data upstream (for example, using a Calculator step to build "Token: " + secretField), or renaming the column using the Rename Fields step removes the secret status.
	Update Fields:
Table field	The field to be updated in the table
Stream field	The field in the stream used to update the table field.
Update	Select Y/N to confirm update
Plain Text	When a field receives a secret status in an upstream step, that status automatically travels with the data to the step. Use the Plain text setting to control how the step handles this incoming secret data. Select Y to write the actual, unmasked value of the incoming secret field to the output target. Select N (the default setting) to safely remove the secret field from the output entirely. The step never writes secret values to the target, and the step excludes the column from the INSERT or UPDATE statements. The target database then applies its own default value or uses NULL. Important: · Select Y only when the target system requires the actual value and no secure alternative exists. Whenever possible, configure downstream tools to read credentials directly from a credential parameters or credential attribute rather than writing sensitive data to an output file or database. · The system saves the Y selection directly within the workflow file. This ensures security reviewers can easily audit the workflow and identify any field configured to expose plain text data. · Ensure the secret status remains intact before the data reaches the output step. Modifying the data upstream (for example, using a Calculator step to build "Token: " + secretField), or renaming the column using the Rename Fields step—removes the secret status. The output step treats these modified fields as standard data and writes them directly to the target.