Skip to main content

NetSuite SuiteAnalytics Connect

This connector captures data from Oracle NetSuite into Flow collections. It relies on the SuiteAnalytics Connect feature in order to both load large amounts of data quickly, as well as introspect the available tables, their schemas, keys, and cursor fields.

If you don't have SuiteAnalytics Connect, check out our SuiteTalk REST connector.

Supported data resources

Flow discovers all of the tables to which you grant access during setup, including Transactions, Reports, Lists, and Setup.

Prerequisites

  • Oracle NetSuite account
  • Allowed access to all Account permissions options
  • A new integration with token-based authentication
  • A custom role with access to objects you want to capture. See setup.
  • A new user assigned to the custom role
  • Access token generated for the custom role

Setup

Create a NetSuite account

  1. Create an account on the Oracle NetSuite portal.

  2. Confirm your email address.

Set up your NetSuite account

  1. Find your Realm, or Account ID. You'll use this to connect with Flow.

    1. In your NetSuite portal, go to Setup > Company > Company Information.

    2. Copy your Account ID.

      If you have a production account, it will look like 2345678. If you're using a sandbox, it'll look like 2345678_SB2.

  2. Create a NetSuite integration to obtain a Consumer Key and Consumer Secret.

    1. Navigate to Setup > Integration > Manage Integrations > New.

    2. Give the integration a name, for example, estuary-rest-integration.

    3. Make sure the State option is enabled.

    4. In the Authentication section, check the Token-Based Authentication checkbox.

    5. Save your changes.

    Your Consumer Key and Consumer Secret will be shown once. Copy them to a safe place.

  3. Set up a role for use with Flow.

    1. Go to Setup > Users/Roles > Manage Roles > New.

    2. Give the role a name, for example, estuary-integration-role.

    3. Scroll to the Permissions section.

    4. (IMPORTANT) Click Transactions and add all the dropdown entities with either full or view access level.

    5. (IMPORTANT) Click Reports and add all the dropdown entities with either full or view access level.

    6. (IMPORTANT) Click Lists and add all the dropdown entities with either full or view access level.

    7. (IMPORTANT) Click Setup an add all the dropdown entities with either full or view access level.

    To allow your custom role to reflect future changes, be sure to edit these parameters again when you rename or customize any NetSuite object.

  4. Set up user for use with Flow.

    1. Go to Setup > Users/Roles > Manage Users.

    2. Find the user you want to give access to use with Flow. In the Name column, click the user's name. Then, click the Edit button.

    3. Find the Access tab.

    4. From the dropdown list, select role you created previously; for example, estuary-integration-role.

    5. Save your changes.

  5. Generate an access token.

    1. Go to Setup > Users/Roles > Access Tokens > New.

    2. Select an Application Name.

    3. Under User, select the user you assigned the role previously.

    4. Under Role, select the role you assigned to the user previously.

    5. Under Token Name, give a descriptive name to the token you are creating, for example estuary-rest-integration-token.

    6. Save your changes.

    Your Token ID and Token Secret will be shown once. Copy them to a safe place.

You now have a properly configured account with the correct permissions and all the information you need to connect with Flow:

  • Realm (Account ID)
  • Consumer Key
  • Consumer Secret
  • Token ID
  • Token Secret
info

You can also authenticate with a username and password, but a consumer/token is recommended for security.

Configuration

You configure connectors either in the Flow web app, or by directly editing the catalog specification file. See connectors to learn more about using connectors. The values and specification sample below provide configuration details specific to the NetSuite source connector.

Properties

Endpoint

PropertyTitleDescriptionTypeRequired/Default
`/accountNetsuite Account IDNetsuite realm/Account ID e.g. 2344535, as for production or 2344535_SB1, as for the sandboxstringRequired
/role_idRole IDThe ID of the role you created. Defaults to 3, which is the ID of the administrator role.int3
/suiteanalytics_data_sourceData SourceWhich NetSuite data source to use. Options are NetSuite.com, or NetSuite2.comstringRequired
/authenticationAuthentication DetailsCredentials to access your NetSuite accountobjectRequired

Token/Consumer Authentication

PropertyTitleDescriptionTypeRequired/Default
/authentication/consumer_keyConsumer KeyConsumer key associated with your integration.stringRequired
/authentication/consumer_secretConsumer SecretConsumer secret associated with your integration.stringRequired
/authentication/token_keyToken KeyAccess token keystringRequired
/authentication/token_secretToken SecretAccess token secretstringRequired

Username/Password Authentication

PropertyTitleDescriptionTypeRequired/Default
/authentication/usernameUsernameYour NetSuite account's email/usernamestringRequired
/authentication/passwordPasswordYour NetSuite account's password.stringRequired

Advanced Config options

PropertyTitleDescriptionTypeRequired/Default
/advanced/connection_limitConnection LimitThe maximum number of concurrent data streams to attempt at once.int10 Connections
/advanced/task_limitTask LimitThe maximum number of concurrent tasks to run at once. A task is either a backfill or incremental load. Backfills can load multiple chunks in parallel, so this must be strictly <= /advanced/connection_limitint5 Tasks
/advanced/start_dateStart DateThe date that we should attempt to start backfilling from. If not provided, backfill from the beginning.dateNot Required

Bindings

PropertyTitleDescriptionTypeRequired/Default
/nameNameThe name of the table this binding refers tostringRequired
/intervalIntervalHow frequently to check for incremental changesISO8601 DurationPT1H (1 Hour)
/log_cursorLog CursorA date-time column to use for incremental capture of modifications.StringRequired (Automatically Discovered)
/page_cursorPage CursorAn indexed, non-NULL integer column to use for ordered table backfills. Does not need to be unique, but should have high cardinality.StringRequired (Automatically Discovered)
/concurrencyConcurrencyMaximum number of concurrent connections to use for backfilling.int1 Connection
/query_limitQuery LimitMaximum number of rows to fetch in a query. Will be divided between all connections if /concurrency > 1int100,000 Rows
/query_timeoutQuery TimeoutTimeout for queries. Typically left as the default as some tables just take a very long time to respond.ISO8601 DurationPT10M (10 Minutes)
/associationsAssociationsList of associated tables for which related data should be loaded.Array[TableAssociation][]
/associations/[n]/child_table_nameForeign Table NameThe name of the "foreign" table that should be associated with the "parent" binding containing this associationStringRequired
/associations/[n]/parent_join_column_nameParent Join ColumnThe name of the column on the "parent" table to be used as the join keyStringRequired
/associations/[n]/child_join_column_nameForeign Join ColumnThe name of the column on the "foreign" table to be used as the join keyStringRequired
/associations/[n]/load_during_backfillLoad During BackfillWhether or not to load associated documents during backfillBooleanFalse
/associations/[n]/load_during_incrementalLoad During IncrementalWhether or not to load associated documents during incremental loadsBooleanTrue

Sample


captures:
${PREFIX}/${CAPTURE_NAME}:
endpoint:
connector:
image: ghcr.io/estuary/source-netsuite-v2:v3
config:
account: "12345678"
authentication:
auth_type: token
consumer_key: xxx
consumer_secret_sops: xxx
token_id: xxx
token_secret_sops: xxx
connection_type: suiteanalytics
role_id: 3
suiteanalytics_data_source: NetSuite2.com
advanced:
connection_limit: 20
cursor_fields: []
enable_auto_cursor: false
resource_tracing: false
start_date: null
task_limit: 10
bindings:
- resource:
associations:
- child_join_column_name: transaction
child_table_name: TransactionAccountingLine
parent_join_column_name: id
load_during_backfill: false
load_during_incremental: true
interval: PT5M
name: transaction
page_cursor: id
query_limit: 100000
concurrency: 1
query_timeout: PT10M
log_cursor: lastmodifieddate
target: ${PREFIX}/${CAPTURE_NAME}/transaction
{...}