Skip to end of metadata
Go to start of metadata

Introduction

A NetSuite Delete activity deletes records in NetSuite and is intended to be used as a target in an operation. After configuring a NetSuite connection, you can configure as many NetSuite activities as you like for each NetSuite connection.

The Delete activity requires the use of either an internal or external ID field to delete existing records.

Creating a NetSuite Activity

From the design canvas, open the Connectivity tab of the design component palette:

Use the Show dropdown to filter on Endpoints, and then click the NetSuite connection block to display activities that are available to be used with a NetSuite connection:

To create an activity that can be configured, drag the activity block from the palette to the operation.

For more information about the parts of an operation and adding activities to operations, see Operation Creation and Configuration.

Configuring a NetSuite Delete Activity

Follow these steps to configure a NetSuite Delete activity:

Step 1: Enter a Name

  • Name: Enter a name to use to identify the NetSuite Delete activity. The name must be unique for each NetSuite Delete activity and must not contain forward slashes (/) or colons (:).
  • Save & Exit: If enabled, click to save the configuration for this step and close the activity configuration.
  • Next: Click to continue to the next step and temporarily store the configuration. The configuration is not saved until you click the Finished button on the last step.
  • Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Step 2: Review the Data Schemas

  • Data Schema: The request and response data schemas for NetSuite are displayed. If the operation uses a transformation, the data schemas are displayed again later during the transformation mapping process, where you can map to target fields using source objects, scripts, variables, custom values, and more.

    The NetSuite connector uses the SOAP web services API used in the version of NetSuite WSDL you have configured. Refer to documentation provided in the NetSuite Help Center (login to NetSuite required) for information on the schema fields.

    TIP: During the transformation mapping process, you can map to either the internalId or externalId fields in NetSuite to associate the records to be deleted.
    NOTE: To refresh a data schema in an existing activity, you must advance through each activity configuration step again, making at least one change (such as adding and removing a character from the end of the name of the activity) to force a refresh of the schema.
  • Back: Click to return to the previous step and temporarily store the configuration.
  • Finished: Click to save the configuration for all steps and close the activity configuration.
  • Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Next Steps

After configuring a NetSuite Delete activity, complete the configuration of the operation by adding and configuring other activities, transformations, or scripts as operation steps. You can also configure an operation's operation settings, which include the ability to chain operations together that are in the same or different workflows.

After a NetSuite Delete activity has been created, menu actions for that activity are accessible from the project pane in either the Workflows or the Components tabs, and from the design canvas. See Activity Actions Menu for details.

NetSuite Delete activities can be used as a target with these operation patterns:

Operations that contain a NetSuite activity can have only one NetSuite activity and cannot also contain any Salesforce, SAP, ServiceMax, or SOAP activities.

Other patterns are not valid using NetSuite Delete activities. See the validation patterns on the Operation Validity page.

A typical use case is to use a NetSuite Delete activity in the Two-Transformation Pattern. In this example, the first transformation (NetSuite Delete Request) creates a request structure that is passed to the NetSuite Delete activity. The second transformation (NetSuite Delete Response) receives the response structure, which is then written to a variable by a Variable Write activity (Write NetSuite Delete Response) and a message is then logged by the Write to Operation Log script:

To use the activity with scripting functions, write the data to a temporary location and then use that temporary location in the scripting function.

When ready, deploy and run the operation and validate behavior by checking the operation logs.

On This Page

Last updated:  Jul 27, 2020

  • No labels