NetSuite actions

NetSuite component actions.

---

Delete Object By Id

Deletes an object by the ID provided.

Delete Object By Id. Config fields

• Object Category - a category of an object in NetSuite:

  • Standard
  • Custom

• Object Type - an object in NetSuite (Contact, Customer etc.). Fetches dynamically.

Delete Object By Id. Input Metadata

Is being fetched dynamically. The sample:

Input metadata for Transaction objects:

{
  "internalId": "string",
  "externalId": "string",
  "deletionReasonCode": "deleteionReasonCodeString",
  "deletionReasonMemo": "deletionReasonMemoString"
}

Deletion Reason Usage Notes

Input metadata for other objects:

{
  "internalId": "string",
  "externalId": "string"
}

Delete Object By Id. Output Metadata

{
  "internalId": "string"
}

Lookup Object By Id

Lookup an object by the ID provided.

Lookup Object By Id. Config fields

• Object Category - a category of an object in NetSuite
  • Standard
  • Custom
• Object Type - an object in NetSuite (Contact, Customer etc.). Fetches dynamically.
• Allow ID to be omitted
• Allow Zero Results

Lookup Objects

Looks for objects available in NetSuite which meet given criteria.

Use this action to execute the following types of searches:

• Basic search — Execute a search on a record type based on search filter fields that are specific to that type. See Basic Searches in SOAP Web Services.

• Joined search — Execute a search on a record type based on search filter fields on an associated record type. See Joined Searches in SOAP Web Services

• Advanced search — Execute a search on a record type in which you specify search filter fields and/or search return columns or joined search columns. Using advanced search, you can also return an existing saved search. See Advanced Searches in SOAP Web Services.

Lookup Objects. Config fields

• Object Type - an object in NetSuite (Contact, Customer etc.). Fetches dynamically.

• Search Type - a type of search. See below.
  • Basic
  • Joined
  • Advanced
• Behavior - a behavior for the component on how to handle the response which has more than 1 object to response with:
  • Emit individually
  • Fetch all
  • Fetch Page

Basic search

A basic search lets you search records of a specific type using the fields on that record as search filters. In a basic search, field criteria are the only values you set. You cannot specify search return columns. The full list of available objects to search can be found in the Help Center (may vary for each installation). You can find the entire metadata of each object there as well.

Log in to your NetSuite account > Suite Cloud (Customization, Scripting, and Web Services) > SuiteCloud Platform Introduction > SuiteCloud Records Reference Tools > The SuiteScript Records Browser > Click ‘Go to the SuiteScript Records Browser.’

Then choose Schema Browser > ‘common’ from the dropdown list and open the Search tab at the left.

What you should do next is to build a correct search request using object fields and operators.

Search operators

It is just the recommended list. You should always use an actual one based on the Help center of your account.

• GetSelectValueFilterOperator:

• SearchDateFieldOperator:

• SearchDoubleFieldOperator:

• SearchEnumMultiSelectFieldOperator:

• SearchLongFieldOperator:

• SearchMultiSelectFieldOperator:

• SearchStringFieldOperator:

• SearchTextNumberFieldOperator:

Basic Search Samples

Search contacts by a provided email

Object Type: Contact

Search Type: ContactSearchBasic

XML request:

The same request for the component (JSON):

{
  "email": {
    "searchValue": "tomsmith@tomsmith.com",
    "operator": {
      "value": "is"
    }
  }
}

Response:

Joined search

Execute a search on a record type based on search filter fields on an associated record type. A joined search allows you search against a specific record type using the fields on an associated record as search filters. In the NetSuite UI, you can identify which associated records provide joined filter criteria by first navigating to a record’s search interface.

Once again, you can find the list of available objects in the Help Center. The component will dynamically fetch all the list with an available metadata. But you should always look at the documentation to build a correct search request.

Joined Search Samples

Search contacts associated with customers

Object Type: Contact

Search Type: Contact Search Join

The following sample shows how to return an associated joined list of records. In this case, all contacts associated with customers of internalId 1, 2 and 3 are returned.

XML request:

The same request for the component (JSON):

{
  "customerJoin": {
    "internalId": {
      "searchValue": [
        {
          "internalId": "449",
          "name": "customer"
        },
        {
          "internalId": "500",
          "name": "customer"
        },
        {
          "name": "customer",
          "internalId": "594"
        }
      ],
      "operator": {
        "value": "anyOf"
      }
    }
  }
}

Response

Search items with a price equal to 10

Object Type: Item

Search Type: Item Search Join

The following sample shows how to search for all items that have a price level of 10.00.

XML request:

The same request for the component (JSON):

{
  "pricingJoin": {
    "rate": {
      "operator": {
        "value": "equalTo"
      },
      "searchValue": 10
    }
  },
  "basic": {
    "type": {
      "operator": {
        "value": "anyOf"
      },
      "searchValue": [
        "_inventoryItem"
      ]
    }
  }
}

Response

Advanced search

Execute a search on a record type in which you specify search filter fields and/or search return columns or joined search columns. Using advanced search, you can also return an existing saved search.

Advanced searching provides users with the ability to:

• Perform a search that references an existing saved search
• Perform a search that references an existing saved search, and then overrides existing search return columns with new search return columns
• Perform a search that references an existing saved search, and then provides additional search filter criteria (on top of the criteria already specified in the saved search)
• Perform a search that specifies search criteria and search result columns

The SOAP web services API includes advanced search objects for all records that have an existing search interface.

Please check your ‘Advanced Search’ Help center section in order to build a correct request. You can find it in the following way:

Log in to your NetSuite account > Suite Cloud (Customization, Scripting, and Web Services) > SuiteTalk Web Services > SuiteTalk SOAP Web Services Platform Guide > SOAP Web Services operations > search > Advanced Searches in SOAP Web Services.

The component will always fetch all the existing metadata for the advanced search for you. All you should do is to delete what you don’t need and to build a correct request based on the documentation.

Known Limitations

• Enum values for condition operators accessible only in the Basic search type.
• Input metadata for property columns absent for object type: Transaction and Advance Search search type.
• The following transaction searches are not supported:

Advanced Search Samples

Execute saved search

Object Type: Customer

Search Type: Customer Search Advanced

The following sample shows how to find customers, using saved search (by a keyword in an email).

XML request:

The same request for the component (JSON):

{
  "savedSearchId": "740"
}

Response

Upsert Object By Id

Either update an object in NetSuite by an ID provided or inserts as a new object if it does not exist.

Upsert Object By Id. Config Fields

• Object Category - a category of an object in NetSuite
  • Standard
  • Custom
• Object Type - an object in NetSuite (Contact, Customer etc.). Fetches dynamically.

Lookup Customer(deprecated)

Deprecated. Use Lookup Object By Id action instead.

This action enables to find the customer by provided ID. It is possible to provide internal, external id or all of them in input message.

If entity doesn’t have externalId You must specify only internalId in input message. If You specify incorrect internal or external id, You will get error That record does not exist.

For example when the externalId exists the answer would be:

{
  "internalId":"1234",
  "externalId":"4567"
}

When the externalId does not exist:

{
  "internalId":"1234"
}

Lookup Invoice(deprecated)

Deprecated. Use Lookup Object By Id action instead.

This action can be used to find invoices by provided ID.

You can provide internal, external id or all of them in input message. If entity doesn’t have externalId You must specify only internalId in input message.

If You specify incorrect internal or external id, You will get error “That record does not exist.”

For example if the externalId exists:

{
  "internalId":"1234",
  "externalId":"4567"
}

If the externalId does not exist:

{
  "internalId":"1234"
}

Upsert Custom Fields

Currently, You can upsert custom fields only from developer mode. You should to use property type, which can accept next values:

• BooleanCustomFieldRef
• DateCustomFieldRef
• DoubleCustomFieldRef
• LongCustomFieldRef
• MultiSelectCustomFieldRef
• SelectCustomFieldRef
• StringCustomFieldRef

You can find example of custom field structures here.