NetSuite Connector > Mappings and mapping tasks with NetSuite > NetSuite objects in mappings
  

NetSuite objects in mappings

When you create a mapping, you can configure a Source, Target, or Lookup transformation to represent a NetSuite object.

NetSuite sources in mappings

In a mapping, you can configure a Source transformation to represent a single NetSuite source or multiple NetSuite sources.
You can use multiple related NetSuite standard objects as a source. You can select a standard object as the primary source, then you add one or more sibling objects or a single child object. When you select a list/record type object, its related object appears in the sibling list. NetSuite does not support the use of child and sibling objects at the same time.
The following table describes the NetSuite source properties that you can configure in a Source transformation:
Property
Description
Connection
Name of the source connection.
Source type
Select Single Object or Multiple Objects.
Object
For a single source. Select the source object.
Add Source Object
For multiple sources. Select the primary object.
Add Child Object
For multiple sources. Select the desired child object.
Add Sibling Objects
For multiple sources. Select the desired sibling objects.
Filter
Filters value in a read operation. You can add conditions to filter records and reduce the number of rows that the Secure Agent reads from the source.
Sort
Not supported.
The following table describes the NetSuite source advanced properties that you can configure in a Source transformation:
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 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 perform a full read, do not use the Start Date and End Date properties.
Page Size
Number of rows that the Secure Agent fetches per page. Default is 100 rows. The maximum value is 1000.
Get Deleted
Includes records that were deleted between the start date and end date for changed data capture.
Concurrent Threads
Number of concurrent threads. Specify the number of concurrent threads allowed.
To use concurrent threads for mapping 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.
Default value is 1.
You cannot use a saved search as a source object in a mapping task that uses concurrent threads.
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.

Adding multiple source objects

To use multiple source objects in a Source transformation, you select the primary source object and the child or sibling objects on the Source tab of the Properties panel.
    1In the Objects and Relationships section, click the arrow to open the Action menu and then select Add Source Object.
    2Select the primary object.
    3Click the arrow in the primary object's row and from the Related Object Actions menu, select either Add Child Object or Add Sibling Objects.
    4Select the desired child object or one or more sibling objects.
    After you select the source objects, the Objects and Relationships section displays the source objects and the relationship between the objects, as shown in the following image:

NetSuite targets in mappings

In a mapping, you can configure a Target transformation to represent a single NetSuite target or multiple NetSuite targets.
When you use multiple NetSuite target objects, select a standard object as the primary target and then add a child object. You must map at least one source field, in addition to the external ID, from the parent object to the target. Also, you must map at least one source field from the child object to the target. The external ID indicates the parent object that relates to a child object.
You can use a custom object as a single target.
The following table describes the NetSuite target properties that you can configure in a Target transformation:
Property
Description
Connection
Name of the target connection.
Target Type
Select Single Object or Multiple Objects.
Object
Target object for a single target or primary target object for multiple targets.
Child Object
For multiple targets. Displays child objects related to the selected target object. Select a single child object.
Operation
Target operation.
The following table describes the NetSuite target advanced properties that you can configure in a Target transformation:
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 Secure Agent writes in a batch to the target. When the batch size is 0, the Secure Agent writes data to the target one row at a time. When the batch size is greater than 0, the Secure Agent writes data to the target in batches of the specified size. The default value is 100.
For insert and delete operations, the maximum value is 200. For upsert and update operations, the maximum value is 100.
Success File
Name of the file that contains rows successfully written to the target.
Error File
Name of the file that contains rows that were not written to the target.
Concurrent Threads
Number of concurrent threads. Specify the number of concurrent threads allowed.
To use concurrent threads for mapping 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.
Default value is 1.
You cannot use a saved search as a source object in a mapping task that uses concurrent threads.
Success File Directory
Directory for the success log files. Specify a directory path that is available on each agent machine in the runtime environment. By default, the agent writes the success log files to the following directory:
<Secure Agent installation directory>\apps\Data_Integration_Server\data\success
Error File Directory
Directory for the error log files. Specify a directory path that is available on each agent machine in the runtime environment. By default, the agent writes the error log files to the following directory:
<Secure Agent installation directory>\apps\Data_Integration_Server\data\error
Forward Rejected Rows
Determines whether the transformation passes rejected rows to the next transformation or drops rejected rows. By default, the agent forwards rejected rows to the next transformation.

NetSuite lookups in mappings

In a mapping, you can configure a Lookup transformation to represent a NetSuite object. You can use Netsuite standard objects and custom objects as lookups.
When you use a NetSuite object as a lookup, you do not need to configure specific NetSuite properties. You can use a custom field in a lookup condition if the field is filterable.