On this Page

Snap type:

Write

Description:

This Snap provides the ability to delete records in NetSuite based on a given list of internal IDs and object types. The fields that can be set on the object are provided on the input view of the Snap and can be mapped using an upstream Data or Structure Snap. This Snap batches up to 100 records per request.

Expected upstream Snaps: Any Snap that provides a document output view such as a Structure or a JSON Generator Snap.
Expected downstream Snaps: [None] or any Snap that has a document input view such as a Filter or a Data or a JSON Formatter.
Expected input: This Snap provides a schema on its input view for the selected object that can then be used in a Mapper Snap to map the required fields.
Expected output: This Snap provides the result of the delete operation for each record on the output view. Errors can be routed to the error view if enabled or cause the Snap to fail during execution.

Note: Empty number values should be given as 0.0, not as null.

Prerequisites:

[None]

Support and limitations:

Works in Ultra Pipelines.

Known Issues:

This Snap currently does not support custom records.

Account:

This Snap uses account references created on the Accounts page of SnapLogic Manager to handle access to this endpoint. See NetSuite Account for information on setting up this type of account.

Error rendering macro 'excerpt-include' : No link could be created for 'Configuring NetSuite Accounts'.

Views:

Input	This Snap has exactly one document input view.
Output	This Snap has at most one document output view.
Error	This Snap has at most one document error view and produces zero or more documents in the view.

Settings

Label

Required. The name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your pipeline.

Batch size

Required. The maximum number of input documents to batch in a single request. Set to 1 to make a separate request for each input document.

Default value: 100

Route records to appropriate views

If selected, the Snap parses the response and routes resulting records to the output view or the error view depending on the resulting status: success or failure.
If not selected, the Snap would not parse the response and write the document(s) to the output view or the error view per each batch.

Default value: Not selected

Pass through

required

Required. If selected, the Snap passes the input document to the output view under the 'original' key. If not selected, the input document is not passed through to the output view. The error view always has an input document in each error document whether this property is selected or not. This property matters only if the "Route records to appropriate views" property is selected.

Default value: Selected

Request timeout

Required. The timeout for the web service call (in seconds). A value of 0 indicates no timeout.

Example: 0
Default value: 0

Maximum request attempts

Required. Specifies the maximum number of attempts to be made to receive a response. The request is terminated if the attempts do not result in a response.

Default value: 3

Retry request interval

Required. Specifies the interval (in seconds) between two successive requests. A retry happens only when the previous attempt resulted in an exception.

Default value: 2

Snap execution

Select one of the three modes in which the Snap executes. Available options are:

Validate & Execute: Performs limited execution of the Snap, and generates a data preview during Pipeline validation. Subsequently, performs full execution of the Snap (unlimited records) during Pipeline runtime.
Execute only: Performs full execution of the Snap during Pipeline execution without generating preview data.
Disabled: Disables the Snap and all Snaps that are downstream from it.

This Snap does not currently support custom records.

Examples

Example #1

Following example will illustrate the usage of Delete Snap. In this example we will delete two account records by internal ID as a batch operation. One of the input documents deletes a record successfully and the other fails.

Sample pipeline looks as shown below:

The input documents to the Snap are as following:

The output document at the output view is as following:

The error document at the error view is as following:

Example #2

The following example will illustrate the usage of the Delete Snap. In this example, we update an employee record using the NetSuite Upsert Snap, which we later delete using the Delete Snap.

In the pipeline execution:

Mapper (Data) Snap maps the employee details to the input fields of NetSuite Upsert Snap:

NetSuite Upsert Snap updates an employee record using the Employee object:

Mapper (Data)1 Snap maps the output of the NetSuite Upsert Snap to the input fields of NetSuite Delete Snap:

NetSuite Delete Snap deletes the employee record based on the supplied external ID. When the NetSuite Delete Snap is saved, it generates the input schema automatically:

After the pipeline executes, the NetSuite Delete Snap shows the following data preview:

Error rendering macro 'excerpt-include' : No link could be created for 'NetSuite Snap Pack'.