Process Activities / NetSuite tab
Parent topic: NetSuite tab

Upsert Entity (NetSuite) activity

An activity that creates an entity, or changes entities if they exist. NetSuite recommends using Upsert Entity as an alternative to Create Entity so you do not create duplicate entities.



Configure the Upsert Entity activity

To configure the Upsert Entity activity, do the procedure in this topic.

Good to Know

How to Start

  1. On the Organizer, do one of these:
  2. Do one of these:
    • Add an activity:
      1. In the Process Builder, in the Activity Library, open the NetSuite tab.
      2. On the NetSuite tab, drag the Upsert Entity activity onto your process.
    • Change an activity:
      1. In your process, double-click your activity.

Procedure

  1. Complete the fields on the General Configuration screen.

    For more information, refer to Configure General Options for a CRM Activity.

  2. Click Upsert Entity .
  3. Complete the fields on the Upsert Entity Configuration screen.

    For more information, refer to Create or Change a NetSuite Entity.

  4. (Optional) Click Advanced > E-mail Notification .

    For more information, refer to Configure E-mail Notifications for Any Activity

General Configuration

Specifies the basic information for a CRM activity.



Fields

Field Name Definition

Display Name
Function:
Specifies the activity name that shows in your process.
Accepted Values:
One line of text that can have spaces.
Default Value:
None
Accepts Process Data Variables:
No

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

Connection Timeout (Seconds)
Function:
Specifies the number of seconds permitted to complete an action before the connection stops.
Accepted Values:
An integer that represents a number of seconds.
Default Value:
600
Accepts Process Data Variables:
No

Upsert Entity Configuration

Specifies the information to create an entity, or changes entities if they exist.



Fields

Field Name Definition

NetSuite
Function:
Specifies the access token that connects to your NetSuite application.
Accepted Values:
A list of access tokens configured for your environment.
Default Value:
None

Add Token

Opens this Screen:
New NetSuite Access Token
Function of this Screen:
Configures a new access token for NetSuite.

Entity Name
Function:
Specifies the name for your entity.
Accepted Values:
One line of text that can have spaces.
Default Value:
None.

When you select the NetSuite access token, the name of the entity shows in the Entity Name field.

Accepts Process Data Variables:
No

Request Mapping
Function:
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 Entity Configuration screen, click the Request tab.
Accepted Values:
Click the Ellipses button to open the Schema Mapper screen.

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

Map Response to AgilePoint Schema
Function:
Specifies the connection from the NetSuite API response parameter to your process schema.
To Open this Field:
  1. On the NetSuite Upsert Entity Configuration screen, click the Response tab.
Accepted Values:
Click the Ellipses button to open the Schema Mapper screen.

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

Store the Response in Custom Attribute
Function:
Specifies the variable that contains the response to a method call. The method must call a web service.
To Open this Field:
  1. On the NetSuite Upsert Entity Configuration screen, click the Response tab.
Accepted Values:
A process data variable.
Default Value:
None
Accepts Process Data Variables:
Yes
Parent topic: NetSuite tab

Quick Links:

Send Feedback

Quick Start

Process Activities

eForm Controls

AgilePoint NX Online Help

AgilePoint NX Technical Documentation

Support Portal

AgilePoint

AgilePoint NX

Documentation Updated: December 3, 2015

© 2015 AgilePoint, Inc. All rights reserved.