NetSuite Connector Guide > Data Synchronization Tasks with NetSuite > Data Synchronization Task Schedule and Advanced Options for NetSuite
  

Data Synchronization Task Schedule and Advanced Options for NetSuite

When you configure a Data Synchronization task to use a NetSuite source or target, you configure advanced properties on the Schedule page of the Data Synchronization Task wizard.
The following table describes the NetSuite advanced source properties:
Advanced Property
Description
Start Date
Start date and time to capture the changed data. Use the following format: YYYY-MM-DD'T'hh:mm:ss.SSSSZ.
To specify the last date or the last date and time when the task ran successfully, enter the $LastRunDate or $LastRunTime data filter variables.
To perform a full read, do not use the Start Date and End Date properties.
End Date
End date and time to capture the changed data. Use the following format: YYYY-MM-DD'T'hh:mm:ss.SSSSZ.
To specify the last date or the last date and time when the task ran successfully, enter the $LastRunDate or $LastRunTime data filter variables.
To perform a full read, do not use the Start Date and End Date properties.
Page Size
Page size used to get data from a source. Default is 100 rows.
Get Deleted
Includes records that were deleted between the start date and end date for changed data capture.
Concurrent Threads
Number of concurrent threads. To run a Data Synchronization task that uses concurrent threads instead of sequential threads, specify the number of concurrent threads allowed.
To use concurrent threads for Data Synchronization tasks, your NetSuite account must be concurrency-enabled.
To optimize performance results with concurrent threads, your administrator might need to adjust the heap size. For example, a heap size of 512 MB for 10 threads might optimize performance results.
Note: You cannot use a saved search as a source object in a Data Synchronization task that uses concurrent threads.
The default value is 1.
Maximum Number of Records to Be Read
Maximum number of records read from the source. For example, a value of 100 means that the agent reads 100 records from the source. The default value is 0, which means the agent reads all records.
Number of Retry
Number of times the agent attempts to execute the request. Default value is 0.
Note: Retry mechanism works after the transaction starts.
Retry Delay
Number of seconds the agent waits before it executes the request again. Default value is 200.
The agent reconnects to the NetSuite port every time it executes the request and send the existing search ID to the NetSuite port.
The following table describes the NetSuite advanced target properties:
Advanced Property
Description
Replace All
Removes existing data from the child object before writing new data to the target.
Batch Size
Number of rows that the agent writes in a batch to the target. When batch size is 0, the agent writes data to the target one row at a time. When batch size is greater than 0, the agent writes data to the target in batches of the specified size. The default value is 100.
Success File
Name of the file that contains rows successfully written to the target.
The agent writes success log files to the following directory:
<Secure Agent installation directory>\apps\Data_Integration_Server\data\success
Reject File
Name of the file that contains rows that were not written to the target.
The agent writes error log files to the following directory:
<Secure Agent installation directory>\apps\Data_Integration_Server\data\error
Concurrent Threads
Number of concurrent threads. To run a Data Synchronization task that uses concurrent threads instead of sequential threads, specify the number of concurrent threads allowed.
To use concurrent threads for Data Synchronization tasks, your NetSuite account must be concurrency-enabled.
To optimize performance results with concurrent threads, your administrator might need to adjust the heap size. For example, a heap size of 512 MB for 10 threads might optimize performance results. The default value is 1.