Skip to main content Skip to complementary content

NetSuite properties

Properties to configure to connect to a NetSuite account.

NetSuite connection



Selection Select or enter NetSuite.
Engine Select your engine in the list.
Connection 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 your NetSuite authentication method.
Information noteNote:

NetSuite as a source connector is compatible with parallel executions if you select the token-based authentication.

This means that the pipeline will run faster as the data will be split in several threads as if you had several NetSuite source connectors in your pipeline.

The number of threads depend on the configuration of your run profile.

  • Basic
Email and Password: Enter your user credentials to access the NetSuite SOAP service.
Role ID and Application ID: Enter your NetSuite role ID and application ID.
  • Token-based
Consumer key and Consumer secret: Enter the consumer key and consumer secret values generated in your NetSuite account.
Token ID and Token secret: Enter the token ID and token secret values generated in your NetSuite account.
Description Enter a display name (mandatory) and a description (optional) for the connection.

NetSuite dataset

Property Configuration
Dataset name Enter a display name for the dataset. This name will be used as a unique identifier of the dataset in all Talend Cloud apps.
Connection Select your connection in the list. If you are creating a dataset based on an existing connection, this field is read-only.
Main Record type Enter or select the record type you want to retrieve.
Advanced Enable customization

This option is enabled by default to retrieve customizations - custom record types and custom fields. With this option enabled, custom record types will be retrieved and can be selected in the Record Type field, and custom fields will be retrieved and included into the schema.

You can disable it if you do not need custom record types or custom fields.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!