Action

Action defines what operation runs against the target object once Scoping, Match, and Mapping have produced the records to be processed.

Action Settings include:

Target Object & Action — Choose the target object and the operation to perform: Insert, Update, Upsert, Delete, Undelete, Merge, Publish, or extended actions like Lead Conversion, Send Email, and Bell Notification.
Update Behavior — Skip Record Update if No Changes, Skip Fields if Target Value Exists, and Skip Null Value Fields give precise control over when and how target fields are written.
DML Controls — All or Nothing governs whether partial successes are allowed; Bypass Duplicate Rule Alerts suppresses Salesforce duplicate warnings; Use Salesforce Upsert API opts into the native upsert behavior; Disable Feed Tracking suppresses Chatter feed entries for the operation.
Source Writeback — Optionally write a value back to the source record after a successful action — useful for marking records as processed, deployed, or synced. Configured via Source Object Writeback Field and Source Object Writeback Value.
Action Result Processor — Plug in custom logic to process the result of each action (e.g., post-action handling, custom logging).

Action step configuring the target operation and DML behavior

`Target Object Name`	Name of the Target Object.
`Target Matching Field`	API name of the target field(case-sensitive) used to identify matching target records. If multiple matches are found for a source record and the Principal Selection Rule is defined, only the principal record is selected—otherwise, all matches are used. Actions then execute based on these results (e.g. Insert is skipped when matches exist, Update runs only for matched records, and Merge consolidates secondary matches into the principal record).
`Target Connection Name`	Name of the Target Connection.
`Skip Record Update if No Changes?`	When checked, records without changes in the target data are excluded from the update operation, preventing unnecessary DML calls and downstream automation from executing.
`Use Salesforce Upsert API?`	When enabled and the Action is Upsert, DSP will utilize the standard Salesforce Upsert API to execute the action in a single DML operation, without attempting to match the target and treating the Insert and Update as separate processes.
`Use Default Assignment Rule?`	When enabled, DSP applies the default assignment rule on action.
`Fill Missing Fields on Merge?`	If checked, when merging, blank fields on the principal record are filled with values from the losing records; existing master values are not overwritten.
`Target Big Object Index Fields`	Comma-separated API names of the target Big Object's index fields, which Big Objects use (rather than the standard ID) to identify records.
`Merge Trigger Action DML?`	When enabled, DSP consolidates and defers DML operations across multiple trigger Executables that have this setting enabled, targeting the same SObject type, and executes them together at the end of the trigger event to minimize total DML usage. Note that this enforces All-or-Nothing behavior — a single record failure will roll back the entire transaction.
`Action in Future Method?`	When enabled — or when the target connection is remote — DSP runs this action asynchronously via @future. If the Executable is already running in a future context, the action is skipped, since @future cannot invoke @future. Applies to #Trigger only.
`Skip Fields if Target Value Exists?`	When enabled, DSP skips assigning values to any target fields that already contain data, preserving existing values during synchronization or import.
`All or Nothing?`	When enabled, DSP rolls back DML on any failure. In batch executions, only the batches that encounter errors are rolled back. When the Native Upsert API is disabled, DSP splits upserts into separate Insert and Update calls and rolls back only the failing calls. Note: In Trigger contexts, DML always follows all-or-none semantics regardless of this setting.
`Skip Null Value Fields?`	When enabled, target fields evaluated as NULL per the mapping will be excluded from the request payload.
`Bypass Duplicate Rule Alerts?`	When enabled, DSP bypasses the Duplicate Rule Alert during target execution. Note: System Administrators always bypass this alert—regardless of this setting—per standard Salesforce behavior.
`Source Object Writeback Field`	API name of the source object field that receives DSP write-back results for succeeded target actions—including skipped updates.
`Source Object Writeback Value`	Stores the value written back to the source object's field after a successful target operation, including cases where updates are skipped. When configured for 'Target Record ID(s)', this field contains a comma-separated list of matching target record IDs for each source record.
`Disable Feed Tracking?`	Applies only when the Target is an integrated Connection.
`Action Result Processor`	Apex class name that implements ActionResultProcessor. If set, DSP calls it after the action with the results so you can perform custom logging or trigger follow-up processes.