Versions Compared

Old Version 32

changes.mady.by.user Mohammed Iqbal

Saved on

compared with

New Version 33

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:

Write


Description:

This Snap provides the ability to create records in NetSuite by defining an object. 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.

  • Expected upstream Snaps: Any Snap that provides a document output view, such as Mapper or Structure or a JSON Generator Snap. 
  • Expected downstream Snaps: [None] or any Snap that has a document input view, such as Filter or Mapper or JSON Formatter.
  • Expected input: This Snap provides 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 create 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.


Prerequisites:

[None]


Support and limitations:
Account: 

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

Insert excerpt
Configuring NetSuite Accounts
Configuring NetSuite 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.

Object


Required. The NetSuite object type to create the records on. This is a suggestible field.

Example: Account

Default value: Account


Custom record


Conditional. This is applicable and required only if CustomRecord is selected for an Object from the suggestible list.

Request timeout 


Required. The timeout for the web service call (in seconds). 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


Multiexcerpt include macro
nameSnap Execution
pageSOAP Execute

Multiexcerpt include macro
nameExecution_Detail_Write
pageSOAP Execute

Troubleshooting

Multiexcerpt include macro
nameNetsuite_Troubleshooting
pageNetSuite Async Get

Examples

Creating an Employee Record Using the NetSuite Create Snap

The following example illustrates the usage of the Create Snap. In this example, we create an employee record. The sample pipeline looks as shown below:  

 


Expand
titleUnderstanding the pipeline

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

NetSuite Create Snap creates an employee record using the Employee object:

After the pipeline executes, it creates a new employee record. The following is the data preview of the NetSuite Create Snap that shows the newly added employee record details:

 



Excerpt

Creating and Updating Customer Records in NetSuite Using Custom Objects

NetSuite enables you to create custom objects, and you can use the NetSuite Create Snap to update these records. This example demonstrates how you can do so.

Download this pipeline.

Expand
titleUnderstanding the pipeline

We design the pipeline as shown above.

Mapper

The Mapper Snap retrieves the NetSuite object's schema from the NetSuite Create Snap and maps the data to be uploaded to the appropriate custom fields in the target schema.

The Mapper offers the following output:

As you can see, the Mapper has mapped custom fields in the NetSuite object schema to values that we listed in the Expression field in the Mapper Snap Settings screen, above. We now need to update a NetSuite record using these custom values.

NetSuite Create

We configure the NetSuite Create Snap as shown below. We select Job as the object that we want to update. This is the schema from which the Mapper Snap picks the custom fields that must be updated.

The NetSuite Create Snap now updates the concerned record based on the object that we selected in the NetSuite Create Settings screen above, and lists out the internal ID of the updated record.

Mapper 1

We can now check whether the record was updated. To do so, we extract the internal ID of the record that was updated from the output of the NetSuite Create Snap using a Mapper Snap:

The Mapper Snap captures the internal ID of the concerned record and makes it available to the NetSuite Get Snap.

NetSuite Get

We now use the internal ID received from the Mapper Snap to check whether the record concerned is actually updated.

We review the output of the NetSuite Get Snap and check whether the new data reflects the latest updates, and find that it does.

Download this pipeline.



Attachments
uploadfalse
oldfalse
patterns*.slp,*.zip

Insert excerpt
NetSuite Snap Pack
NetSuite Snap Pack
nopaneltrue