Set up the Oracle NetSuite connection to start the flow of data into Data 360.
note: This feature is a Beta Service. A customer may opt to try a Beta Service in its sole discretion. Any use of the Beta Service is subject to the applicable Beta Services Terms provided at Agreements and Terms. If you have questions or feedback about this Beta Service, contact the Data 360 Connector team at datacloud-connectors-beta@salesforce.com.
| User Permissions Needed | |
|---|---|
| To create a connection: | System Admin profile or Data Cloud Architect permission set |
Before you begin:
- Enable the Beta connector through the feature manager. See Enable Data 360 Features.
- Verify your admin has enabled firewalls on the system you want Data 360 to connect to by including these IP addresses to your allowlists.
- If using Named Credential authentication, create external and named credentials.
-
In Data Cloud, click Setup, and select Data Cloud Setup.
-
Under External Integrations, select Other Connectors.
-
Click New.
-
On the Source tab, select Oracle NetSuite and click Next.
-
Enter a connection name, connection API name, and provide the authentication and connection details.
-
For Authentication Details, select Token Authentication or Named Credential from the Authentication Method dropdown.
-
Role Id: Enter the NetSuite role ID for the specified account. In NetSuite, if you have the Show Internal IDs preference enabled, go to Setup > Users/Roles > User Management > Manage Roles.
-
Include Child Tables: Select whether to display child tables. The default is
false.
-
For Token Authentication, enter the credentials from your NetSuite account.
-
Client ID: Enter the client ID from the integration record in NetSuite.
-
Client Secret: Enter the client secret from the integration record in NetSuite.
-
Access Token: Enter the access token generated for the user role in NetSuite.
-
Access Token Secret: Enter the access token secret generated for the user role in NetSuite.
note: Token Authentication tokens require periodic refresh. If a token expires, the connection fails silently. To avoid data sync interruptions, monitor your connection status and regenerate tokens in NetSuite before they expire.
-
-
For Named Credential authentication, select a Named Credential.
-
-
For Connection Details, populate the following parameters.
-
Account Id: Enter the account ID that can be found at the beginning of the NetSuite URL. If the URL is https://1234567.app.netsuite.com/, your account ID is ‘1234567’.
-
Version: Enter the NetSuite version number. The default is
2025_2. -
Schema: Select the NetSuite API schema to use. SuiteQL is the default. For information about the available objects, see Oracle NetSuite Connector Objects (SuiteQL Schema) and Oracle NetSuite Connector Objects (SuiteTalk Schema).
-
Timeout: Optionally enter a request timeout in seconds. The default is
0, which means that requests don't time out. -
Page Size: Optionally enter the number of rows returned on each page of a NetSuite API response. The default is
1,000. -
Row Scan Depth: Optionally enter the number of rows that the connector scans during schema detection. The default is
0. -
Tables: Optionally enter a comma-separated list of tables to restrict the tables that the connector exposes. By default, the field is empty.
-
Include Custom Field Columns: Select this option to include custom field columns in the tables that the connector exposes. By default, this option isn't selected.
-
Include Custom Record Tables: Select this option to expose custom record tables. By default, this option isn't selected.
-
Auto Detect SuiteAnalytics Connect Enabled: From the dropdown, select whether the connector automatically detects whether SuiteAnalytics Connect is enabled for your NetSuite account. The default is
false. -
Use Chunked Metadata: Select this option to use chunked metadata. By default, this option isn't selected.
note: To learn more about connecting to Oracle NetSuite, review Navigating NetSuite.
-
-
To review your configuration, click Test Connection.
-
Click Save.
After the connector details are accepted, the connection is created and listed under Connectors. You can now create data streams.