Upsert Record (NetSuite) activity

An activity that creates an entity record, or changes the record, if it exists, in NetSuite. NetSuite recommends to use Upsert Record as an alternative to Create Record so you do not create duplicate records.


Upsert Record activity

Configure the Upsert Record activity

To configure the Upsert Record 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 Upsert Record activity onto your process.

    Drag Upsert Record activity

General Configuration

Specifies the basic settings for the Upsert Record 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 Upsert Record Configuration

Specifies the configuration to create an record or change a record, if it exists, in NetSuite.

Figure: NetSuite Upsert Record Configuration > Request tab

NetSuite Upsert Record 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 an entity for which to create or change 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 parameter 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. On the NetSuite Upsert Record Configuration screen, 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.

Example:
Refer to:

Map Response to AgilePoint Schema

Description:
Specifies the connection from the NetSuite API response parameter to your process schema.
To Open this Field:
  1. On the NetSuite Upsert Record Configuration screen, 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.

Example:
Refer to:

Store the Response in Custom Attribute

Description:
Specifies the process data variable that contains the record internal ID from NetSuite.
To Open this Field:
  1. On the NetSuite Upsert Record Configuration screen, click the Response tab.
Allowed Values:
A variable.

Format:

  • String

Accepted:

  • Numbers
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?