Create Multiple Records (NetSuite) activity

An activity that creates more than one entity record in NetSuite.


Create Multiple Records activity

Configure the Create Multiple Records activity

To configure the Create Multiple Records activity, do the procedure in this topic.

Examples

Good to Know

How to Start

  1. Open Process Builder.

    For information about how to open this screen, refer to Process Builder.


    Open Process Builder
  2. In Process Builder, in the Activity Library, open the NetSuite tab.

    Open NetSuite tab
  3. On the NetSuite tab, drag the Create Multiple Records activity onto your process.

    Drag Create Multiple Records activity

General Configuration

Specifies the basic settings for the Create Multiple Records activity.

Figure: General Configuration screen

General Configuration screen

Fields

Field NameDefinition

Display Name

Description:
Specifies the activity name that shows in your process.
Allowed Values:
One line of text (a string).

Accepted:

  • Letters
  • Numbers
  • Spaces
Default Value:
None
Accepts Variables:
No
Example:
This is a common configuration field that is used in many examples. Refer to:
  • Examples - Step-by-step use case examples, information about what types of examples are provided in the AgilePoint NX Product Documentation, and other resources where you can find more examples.

Description

Description:
Specifies an optional text description for your activity.
Allowed Values:
More than one line of text.
Default Value:
None
Accepts Variables:
No

Connection Timeout (Seconds)

Description:
Specifies the number of seconds permitted to complete an action before the connection stops.
Allowed Values:
An integer.

Represents

  • A number of seconds
Default Value:
600
Accepts Variables:
No

NetSuite Create Multiple Records Configuration

Maps request data from NetSuite to your process when you create entity records.

Figure: NetSuite Create Multiple Records Configuration > Request tab

NetSuite Create Multiple Records Configuration Request tab

Fields

Field NameDefinition

NetSuite

Description:
Specifies the access token that connects to your NetSuite application.
Allowed Values:
A list of access tokens configured for your environment.
Default Value:
None
Example:
Refer to:

Create Add Token icon

Opens this Screen:
Access Tokens for NetSuite
Function of this Screen:
Configure an access token to connect to NetSuite.
Example:
Refer to:

Entity Name

Description:
Specifies the name of the entity for which you want to create a record.
Allowed Values:
An entity name from the list.
Default Value:
None.

When you select the NetSuite access token, the name of entities show in the Entity Name field.

Request Mapping

Description:
Connects the NetSuite API request parameters to your process schema. This is mandatory only if the request passes data from the process schema to parameters in the NetSuite API.
To Open this Field:
  1. Click the Request tab.
Allowed Values:
Click the Schema Mapping Schema Mapping icon button to open the Schema Mapper screen.

Use this screen to connect the request to the data model for your process.

Default Value:
None
Example:
Refer to:

Map Response to AgilePoint Schema

Description:
Specifies the connection from the NetSuite API response parameters to your process schema.
To Open this Field:
  1. Click the Response tab.
Allowed Values:
Click the Schema Mapping Schema Mapping icon button to open the Schema Mapper screen.

Use this screen to connect the response to the data model for your process.

Default Value:
None
Example:
Refer to:

Store the Response in Custom Attribute

Description:
Specifies the variables that store more than one record internal ID from NetSuite
To Open this Field:
  1. Click the Response tab.
Allowed Values:
A process data variable that represents more than one record internal ID, separated by semicolons (;).
Default Value:
None
Accepts Variables:
Yes
Limitations:

Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?