Skip to main content

NetSuite connector reference

Preview

The NetSuite connector is in Public Preview.

Find reference material for the NetSuite ingestion connector in Databricks Lakeflow Connect.

Supported data source

The NetSuite connector supports ingestion from the NetSuite2.com data source only. The legacy netsuite.com data source isn't supported.

To verify that your NetSuite account uses the NetSuite2.com data source, check the JDBC URL in your NetSuite account settings. See Step 5: Find the host, port, and account ID.

Supported tables

The NetSuite connector supports all tables in the NetSuite2.com data source except for the DeletedRecord table.

To view the available tables in your NetSuite account, either query NetSuite metadata using the SuiteAnalytics Connect feature or refer to your NetSuite schema documentation.

Automatic data transformations

Databricks transforms NetSuite data types into Delta-compatible data types as follows:

NetSuite Type

Delta Type

BIT

Long

BIGINT

Long

INT

Long

TINYINT

Long

SMALLINT

Long

ROWID

Long

FLOAT

Double

DOUBLE

Double

REAL

Double

NUMERIC

Double

DECIMAL

Double

VARCHAR

String

WVARCHAR

String

CHAR

String

WCHAR

String

NCHAR

String

NVARCHAR

String

LONGNVARCHAR

String

WLONGVARCHAR

String

CLOB

String

BOOLEAN

Boolean

DATE

String

TIME

String

TIME_WITH_TIMEZONE

String

TIMESTAMP

Timestamp

TIMESTAMP_WITH_TIMEZONE

Timestamp

Pipeline configuration

When creating a NetSuite ingestion pipeline, you must specify the following configuration properties:

  • name: A unique name for the ingestion pipeline.
  • catalog: The Unity Catalog catalog where ingested data and event logs will be written.
  • target: The Unity Catalog schema where ingested data will be written.
  • serverless: Must be set to true for NetSuite pipelines. NetSuite ingestion requires serverless Lakeflow Declarative Pipelines.
  • ingestion_definition: An object containing the ingestion configuration.
    • connection_name: The name of the Unity Catalog connection to NetSuite.
    • table_configuration: An object containing table-level configuration.
      • netsuite_jar_path: The path to the NetSuite SuiteAnalytics JDBC JAR file in a Unity Catalog volume (for example, /Volumes/main/default/netsuite_jars/NQjc.jar).
    • objects: An array of table objects to ingest. Each object contains:
      • table: An object describing the source and destination table.
        • source_schema: The source schema in NetSuite. Use netsuite2 for the NetSuite2.com data source.
        • source_table: The name of the NetSuite table to ingest.
        • destination_catalog: The Unity Catalog catalog where the ingested table will be written.
        • destination_schema: The Unity Catalog schema where the ingested table will be written.
        • table_configuration: An object containing table-specific configuration.

Authentication fields

To create a NetSuite connection in Catalog Explorer, you must provide the following authentication details:

  • Consumer Key: The OAuth consumer key from your NetSuite integration.
  • Consumer Secret: The OAuth consumer secret from your NetSuite integration.
  • Token ID: The access token ID for your NetSuite user.
  • Token Secret: The access token secret for your NetSuite user.
  • Role ID: The internal ID of the Data Warehouse Integrator role in NetSuite.
  • Host: The hostname from your NetSuite JDBC URL (for example, mycompany.connect.api.netsuite.com).
  • Port: The port number from your NetSuite JDBC URL (typically 1708).
  • Account ID: The account ID from your NetSuite JDBC URL.

For instructions on obtaining these authentication details, see Configure NetSuite for ingestion into Databricks.