Versions Compared

Old Version 26

changes.mady.by.user Kalpana Malladi

Saved on

compared with

New Version Current

changes.mady.by.user Kalpana Malladi

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

On this Page

Table of Contents
maxLevel2
excludeOlder Versions|Additional Resources|Related Links|Related Information

Snap type:

Read


Description:

This Snap gets the list of records from NetSuite based on the given list of internal IDs and object types. The object becomes suggestible once the account is defined. 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 Mapper or Structure Snap.

The Snap batches up to 100 records per request.

  • Expected upstream Snaps: Any Snap that provides a document output view, such as Mapper or Structure or a JSON Generator Snap.
  • Expected downstream Snaps: Any Snap that has a document input view, such as Filter or Mapper or 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 get 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 Task 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.

Insert excerpt
Configuring NetSuite SOAP Accounts
Configuring NetSuite SOAP Accounts
nopaneltrue

Views:


InputThis Snap has exactly one document input view.
OutputThis Snap has at most one document output view.
ErrorThis 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. 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. Timeout for the web service call (in seconds). 0 indicates no timeout.
Default value: 0

Maximum request attempts

Required. The maximum number of requests to attempt in case of failure.

Default value: 3 

Retry request interval


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

Default value:  2

Multiexcerpt include macro
nameSnap Execution
pageAnaplan Read


Multiexcerpt include macro
nameSnap_Execution_Introduced
pageAnaplan Read


Note

This Snap does not currently support custom records.

Troubelshooting

Troubleshooting

Multiexcerpt include macro
nameNetsuite_Troubleshooting
pageNetSuite Async Get

Examples


Expand
titleAccount records by internal ID as batch operation

The following example will illustrate the usage of Get List Snap. In this example we will get the account records by internal ID as batch operation. The Snap receives four input documents. The first three documents produce three records at the output view and the last one fails.

Sample pipeline looks as shown below:

 

The input documents to the NetSuite Get List Snap are following:

 


The output documents at the output view are as following:

 


The error document at the error view is as following:

 


Expand
titleRetrieve a list of employee records using their employee internal ID

The following example illustrates the usage of Get List Snap. In this example, using the following pipeline, we retrieve a list of employee records using their employee internal ID. 

In the pipeline execution:

  1. JSON Generator provides employee internal IDs for which we need the employee records from NetSuite:
  2. Mapper Snap maps the output of the JSON Generator Snap to the input fields of the NetSuite Get List Snap:
  3. NetSuite Get List Snap retrieves employee records based on the internal IDs & object type:

    When the NetSuite Get List Snap is saved, it generates the input schema automatically. The following is the data preview of the NetSuite Get List Snap:



Insert excerpt
NetSuite SOAP Snap Pack
NetSuite SOAP Snap Pack
nopaneltrue