NetSuite Destination Component is SSIS Data Flow Component for loading data into NetSuite record. The configuration parameters are provided in the standard data flow destination component dialog. A separate input is setup for the main record and each related composite record.
Use the parameters below to configure the component.
Select destination record action. This property has the options listed in the following table.
Create new instance in the destination NetSuite record.
Update existing instance in the destination NetSuite record. You have to specify internalId for the update to work.
Delete existing instance from the destination NetSuite record.
Update and insert record in the destination NetSuite record. You have to specify externalId for action to work.
After action change, you have to use Refresh command in the 'Column Mappings' tab to reload destination page metadata.
Specify the destination NetSuite record where the data is loaded.
Specify the number of rows to be sent as a batch.
Specify how to handle rows with errors.
Contains the unique identifier of the added, updated or deleted record.
The composite record input accepts sets of rows, one set for each parent record. Each set of rows must be separated with blank row (all NULLs). The parent record will not finish processing its record, until all composite record children have received blank row to indicate completion.
The component's Error Output is used for providing both error information and the processed record identifier. Check the ErrorCode column:
Not an error record.
Error record. Check the ErrorDescription column for more details.
You can set up a standard Conditional Split component to filter non-error records.
The input for list reference field is a string containing both list type identifier and record internal identifier. The input format is:
<type id>;<internal id>
Multiple list references are separated with semicolon (;).
Fixed: Component failed to set custom fields to NULL (Thank you, Dave).
Fixed: Failed to process transaction item custom fields (Thank you, Vijay).
Fixed: Component failed to delete records from custom record type (Thank you, Mark).
Fixed: NetSuite's pricingMatrix composite object was not available for use (Thank you, Rahim).
New: Redesigned for better support of composite data.