|Stage Type - Update||Will perform an update-only operation on matched records for each Origin row. Unmatched records will be skipped.|
|Stage Type - Insert||Will perform an insert-only operation for each Origin row. Use this operation when performing a “dump” of the data.|
|Stage Type - Delete||Will perform a delete operation on the Destination database for each Origin row, based on the match.|
|Stage Type - Update/Insert||Will first perform a lookup, based on matches. If a match is found, an update operation will be performed. If no match is found, an insert operation will be performed.|
Stage Type - Skip/Insert
Will first perform a lookup, based on matches. If a match is found, the record will not be modified. If no match is found, an insert operation will be performed.
|Use Origin Connection|
By default all stages write to the destination connection, use this checkbox to override this behavior and instead select a table from your origin connection to write to. This is useful for setting things such as a "process flag" or "last processed date".
|Omit Blank Field Value Writes||If checked, the insert/operation will ignore NULL/blank fields while building the SQL statement – resulting in NULL values on the destination. Said another way, if a mapping on a particular field results in a blank or null value, it won’t bother to write that value to the destination at all. This way, if you had a value in the destination, it won’t be overwritten with a blank/null.|
This is used in conjunction with the "Skip If Blank" checkbox column in the mapping screen. When a mapping is blank this setting will control whether just the current stage gets skipped or if the entire row gets skipped.
|Multiple Skip Logic||When multiple mappings are being checked for blank this controls when a row is skipped. If "Or" is used then the record will be skipped if any one of the mappings are blank. If "And" is used then the record will only be skipped if all the mappings are blank.|