tNetSuiteOutput (v2019/2021) Standard properties

Click the Apply button to validate your selection.

Property Type

Select the way the connection details will be set.

• Built-In: The connection details will be set locally for this component. You need to specify the values for all related connection properties manually.

• Repository: The connection details stored centrally in Repository > Metadata will be reused by this component.

  You need to click the [...] button next to it and in the pop-up Repository Content dialog box, select the connection details to be reused, and all related connection properties will be automatically filled in.

A schema is a row description. It defines the number of fields (columns) to be processed and passed on to the next component. When you create a Spark Job, avoid the reserved word line when naming the fields.

Built-In: You create and store the schema locally for this component only.

Repository: You have already created the schema and stored it in the Repository. You can reuse it in various projects and Job designs.

When the schema to be reused has default values that are integers or functions, ensure that these default values are not enclosed within quotation marks. If they are, you must remove the quotation marks manually.

For more information, see Retrieving table schemas.

Click Edit schema to make changes to the schema. If the current schema is of the Repository type, three options are available:

• View schema: choose this option to view the schema only.

• Change to built-in property: choose this option to change the schema to Built-in for local changes.

• Update repository connection: choose this option to change the schema stored in the repository and decide whether to propagate the changes to all the Jobs upon completion.

  If you just want to propagate the changes to the current Job, you can select No upon completion and choose this schema metadata again in the Repository Content window.

Click Sync columns to retrieve the schema from the previous component connected in the Job.

API version

Select the version of the NetSuite API you are connecting to.

Account

Enter your NetSuite web services account number (also called account ID).

Login type

Select the login type: Basic or Token-based.

E-mail and Password

Enter your user credentials to access the NetSuite SOAP service.

These two fields are available when Basic is selected from the Login type drop-down list.

Role ID

Enter your NetSuite role ID.

This field is available when Basic is selected from the Login type drop-down list.

Enter the NetSuite application ID generated for your account.

An application ID is required starting from NetSuite version 2015 and above. You can find your application ID or create a new one on NetSuite's Manage Integration page.

This field is available when Basic is selected from the Login type drop-down list.

Enter the consumer key and consumer secret generated in your NetSuite account.

These two fields are available when Token-based is selected from the Login type drop-down list.

Enter the token ID and token secret generated in your NetSuite account.

These two fields are available when Token-based is selected from the Login type drop-down list.

Record Type

Click the [...] button next to the field to open a dialog box, and then select a record type you want to retrieve or select the Use custom object check box and specify a custom record type in the Object Name field.

• Add: Adds a new record to your data. If a duplicate is found and the Die on error check box is selected, the Job stops; if the Die on error check box is cleared, the duplicate is ignored and the Job continues.

• Update: Makes changes to an existing record.

  If the record corresponding to the specified Internal ID does not exist, and the Die on error check box is selected, the Job stops.

  To use this option, the InternalId column must exist in the schema and set as Key.

• Upsert: Updates the record corresponding to the specified ID, or inserts a new record if it does not exist.

  To use this option, a column for record ID must exist in the schema and set as Key.

• Delete: Removes an existing record.

  If the record corresponding to the specified Internal ID does not exist and the Die on error check box is selected, the Job stops.

  To use this option, the InternalId column must exist in the schema and set as Key.

tStatCatcher Statistics

Select this check box to gather the Job processing metadata at the Job level as well as at each component level.

Specify the maximum number of records that can be processed in a batch.

Enable customizations

To use NetSuite's Upsert operation, the ExternalId column must exist in the schema and set as Key.

This option is available when Upsert is selected from the Action list in Basic settings.

By default, for compatibility reasons, this option is enabled and the component performs the Add or Update action for an upsert depending on whether the record ID is specified.

Global Variables

NB_LINE: the number of rows read by an input component or transferred to an output component. This is an After variable and it returns an integer.

CURRENT_INTERNALID: The internal ID of the record currently inserted or processed. This is a Flow variable and it returns an integer.

ERROR_MESSAGE: the error message generated by the component when an error occurs. This is an After variable and it returns a string. This variable functions only if the Die on error check box is cleared, if the component has this check box.

A Flow variable functions during the execution of a component while an After variable functions after the execution of the component.

To fill up a field or expression with a variable, press Ctrl+Space to access the variable list and choose the variable to use from it.

For more information about variables, see Using contexts and variables.