NetSuite SuiteAnalytics Connector

Sync NetSuite SuiteAnalytics tables into your warehouse with role-based discovery and cursor-aware incremental reads.

SourceBronze

Evaluating against Fivetran? See how Supaflow handles NetSuite SuiteAnalytics pricing, connector quality, and Snowflake deployment side-by-side.

Supaflow vs Fivetran

Why Supaflow

All connectors included

Every connector is available on every plan. Pricing does not increase with connector count.

Pay for compute, not rows

Credit-based pricing. Usage scales with your pipelines, not with row counts.

One platform

Ingestion, dbt Core transformation, reverse ETL, and orchestration in a single workspace.

Capabilities

SuiteAnalytics Connect Source

Connect through NetSuite SuiteAnalytics Connect with Account ID, Server Host, Role ID, username, and password. The connector uses the current SuiteAnalytics Connect data source and reads only the data visible to the configured role.

Role-Based Table Discovery

Schema discovery reflects the SuiteAnalytics tables and fields your selected role can read. The object list is account-specific, so newly granted tables appear after schema refresh instead of being hard-coded in the connector.

Cursor-Aware Incremental Reads

Tables with a numeric source primary key and a supported last-modified cursor (`lastmodifieddate`, `lastmodified`, or `linelastmodifieddate`) can run incrementally. Other readable tables remain available for full refresh.

Large-Table Read Tuning

For high-volume NetSuite tables, you can reduce the Numeric ID Chunk Width so Supaflow issues smaller source queries. This gives large incremental syncs a practical tuning knob when a table is busy or prone to long-running reads.

Transaction Type Allowlist

Optionally restrict the `transaction` table to selected NetSuite transaction type codes such as SalesOrd, CustInvc, or PurchOrd. Leave the allowlist blank to read every transaction type visible to the role.

Supported Objects

Discovered NetSuite Tables

Role-visible tables

Every SuiteAnalytics Connect table visible to the configured role can appear in schema discovery. Common examples include transactions, transaction lines, customers, vendors, items, accounts, and subsidiaries.

Incremental Eligible

Numeric primary key + last-modified cursor

Tables become incremental when Supaflow discovers a numeric source primary key plus `lastmodifieddate`, `lastmodified`, or `linelastmodifieddate`.

Full Refresh

Readable tables without incremental metadata

Tables that do not meet the primary-key and cursor requirements can still be selected for full-refresh pipelines.

How It Works

Enable SuiteAnalytics Connect

In NetSuite, enable SuiteAnalytics Connect and assign a custom role with SuiteAnalytics Connect permission plus read access to the records you want to sync. Avoid Administrator, Full Access, 2FA-required, and Connect IP-restricted roles for this username/password connector.

Collect NetSuite connection values

Open the SuiteAnalytics Connect Driver Download page and copy the Account ID, Service Host, and Role ID shown under Your Configuration. Supaflow connects to the service host on port 1708 and uses NetSuite2.com by default.

Enter credentials in Supaflow

Create a NetSuite source and enter Account ID, Server Host, Role ID, Username, and Password. Passwords are stored encrypted. OAuth 2.0 and token-based authentication are not exposed by this connector.

Tune optional settings

Leave advanced settings at their defaults for most accounts. Use Transaction Type Allowlist to narrow the transaction table, Numeric ID Chunk Width to tune range reads, and Schema Refresh Interval to control metadata refresh cadence.

Test and save

Click Test & Save. Supaflow validates the SuiteAnalytics Connect session, then discovers the NetSuite tables visible to the configured role.

Use Cases

ERP and finance reporting

Land NetSuite transactions, accounts, customers, vendors, items, and related tables in your warehouse so finance and analytics teams can build reporting models outside the NetSuite UI.

Transaction analysis by type

Use the Transaction Type Allowlist when a pipeline only needs orders, invoices, purchase orders, or another focused set of transaction types.

Role-scoped operational exports

Use a dedicated NetSuite role to control exactly which tables and fields Supaflow can discover, then refresh schema as permissions change.

Frequently Asked Questions

Which NetSuite data source does Supaflow use?

The connector defaults to NetSuite2.com. Oracle identifies NetSuite2.com as the current SuiteAnalytics Connect data source, so leave Server Data Source unchanged unless Supaflow support asks you to adjust it during troubleshooting.

Which authentication methods are supported?

This connector supports NetSuite username and password authentication for SuiteAnalytics Connect. OAuth 2.0 and token-based authentication are not currently exposed in the Supaflow connector configuration.

Do I need to install a NetSuite driver?

Most customers use Supaflow-hosted agents and do not need to install NetSuite drivers. Driver installation only applies to private or installed Supaflow agents running in your own tenant; see the docs appendix for that setup.

Can I use the Data Warehouse Integrator role?

The Data Warehouse Integrator role requires token-based authentication in NetSuite. Because this connector currently exposes username and password authentication only, use a custom SuiteAnalytics Connect role unless Supaflow support has confirmed a different setup for your account.

Which NetSuite objects can I sync?

Supaflow discovers tables dynamically from SuiteAnalytics Connect. The available objects depend on your account, enabled NetSuite features, and the permissions on the configured role.

Can I sync saved searches, datasets, workbooks, or reports?

Not as separate source objects. Supaflow syncs tables exposed through SuiteAnalytics Connect; saved searches, SuiteAnalytics datasets, workbooks, and reports are not separate connector objects unless their underlying data is available through a role-visible SuiteAnalytics Connect table.

How does incremental sync work?

A table is incremental only when schema discovery finds a numeric source primary key and a supported last-modified cursor: `lastmodifieddate`, `lastmodified`, or `linelastmodifieddate`. Other readable tables use full refresh.

How are formula or computed fields handled?

Supaflow reads the fields NetSuite exposes through SuiteAnalytics Connect. Incremental sync only detects changes when the table's supported last-modified cursor advances, so use full refresh for a table when computed values can change without updating that cursor.

Does Supaflow capture NetSuite deletes?

No. Incremental sync reads rows whose supported cursor advances. Hard deletes are not emitted as delete events unless NetSuite represents them in a table you sync.

Why is a table or field missing?

SuiteAnalytics Connect follows NetSuite role-based access restrictions. Confirm the configured role can read the missing record type or field, then run schema discovery again.

Can I limit the transaction table to specific transaction types?

Yes. Set Transaction Type Allowlist to comma-separated NetSuite transaction type codes such as SalesOrd,CustInvc,PurchOrd. Leave it blank to read all visible transaction types.

Can I run NetSuite pipelines natively inside Snowflake?

Yes. Supaflow runs as a Snowflake Native App via Snowpark Container Services, so NetSuite data can be extracted and loaded without leaving your Snowflake account.