| Execution Settings |
Action to Bulk API? | When enabled, DSP utilizes the bulk API for data submission rather than direct DML operations. Adjust the Batch Size for the best performance outcome with the considerations of the governor limits to be consumed especially the CPU time and heap size if too many records are involved in a single batch. The actual DML results can be checked in the Setup -> Bulk Data Load Jobs, instead of in the Batch Executions. |
Batch Size | The number of source records taken into each batch execution. |
Stop Execution When a Batch Fails? | When enabled, DSP will attempt to stop the remaining batches if any batch fails. |
Log to File? | When enabled, DSP stores the matched target records and the pre-action request and response payloads in a ContentDocument linked to each Batch Execution. These logs provide an audit trail and allow data restoration if required. Note: File logging increases runtime overhead and consumes additional storage. |
Log All Target Fields? | When enabled, the log captures all accessible fields on the target object, rather than only the mapped target fields. Only fields the running user has read access to are included. Has no effect unless "Log to File" is enabled. |
Auto Retry Failed Batches? | When enabled, upon the completion of the batch job execution, DSP will automatically retry the failed batches. |
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. |
Serial Mode? | When enabled, DSP runs in serial mode. Note: serial mode executes slower since one batch has to wait for the previous one to complete before getting started. Check it if you need to guarantee the execution order or when you face the limitation - 'Future method cannot be called from a future or batch method'. |
Execution Finalizer | Apex class name that implements the ExecutionFinalizer interface and runs after the Execution is completed. |
Source Big Object Index Fields | Comma-separated API names of the source Big Object's index fields, which Big Objects use (rather than the standard ID) to identify records. |
Record-Based Configuration Deployment? | Specifies whether this Executable deploys record-based configuration. When enabled, the Data Sync Pro VS Code plugin can export the source data as JSON for local backup and metadata-driven version control in a code repository. |
Bypass Queueable Delegation? | Specifies whether batch executions bypass delegation to a Queueable process and run directly. (Queueable delegation improves execution speed — disable only when necessary, such as when the daily async execution limit is approaching.) |
Access Permissions | Comma separated custom permission names. If set, access is restricted to users who possess at least one of the listed permissions. |
Retrieve Limit | The maximum number of records to be retrieved from the source. |
| Incremental Retrieval |
Incremental Retrieval Since | Defines the date-time option used to derive the cut-off timestamp for incremental batch executions; DSP retrieves only records whose value in the selected field is later than that calculated timestamp. |
Incremental Retrieval Field | Enter the API name of the date-time field to use for incremental batch executions. If left blank, "SystemModstamp" is used by default. |
Incremental Retrieval Seed Time | Timestamp defining the starting point for the initial incremental batch execution. For subsequent runs, DSP recalculates the cut-off using the "Incremental Retrieval Since" setting. |
| Notifications |
Notify When Execution Completes | If enabled, DSP sends an email notification when an Execution(batch) is completed. This also depends on the Email Deliverability setting if running in Sandbox. |
Notify Email Addresses | Comma seperated email addresses. |
Notify Owner? | When enabled (and 'Notify When Execution Completes' is active), adds the Executable owner to the email notification recipients upon execution completion. |
