Connect Foundry to Oracle NetSuite using the SuiteQL framework and start syncing data from your NetSuite ERP to Foundry.
Capability | Status |
---|---|
Exploration | 🟢 Generally available |
Batch syncs | 🟢 Generally available |
Incremental | 🟢 Generally available |
Learn more about setting up a connector in Foundry.
The NetSuite SuiteQL source uses token-based authentication (TBA) ↗.
The token-based authentication feature must be enabled on your account. To enable TBA, see NetSuite documentation ↗.
Access control in NetSuite is configured via the assignment of roles to a user; each role is a collection of permissions that define what tasks the user can perform and what data they can access. We recommend the following configuration for the user that will connect to Foundry:
Create a dedicated role with appropriate permissions.
foundry-role
.
Assign the new role to a user.
foundry-role
) from the dropdown list, select Add then Save.To verify that you added the correct permissions, log in as the user you have assigned the new role to, and check that you can view all the data that you expect.
Integration records are used in NetSuite to manage connections to external systems. We recommend the following configuration to connect to Foundry:
foundry-integration
.CLIENT ID
and CLIENT SECRET
. You will need them to configure Foundry.CLIENT ID
and CLIENT SECRET
will be displayed only the first time you save the integration record. You must reset them to get new ones, which invalidates the previous values.
foundry-integration
in our example), the user to which you've assigned the newly created role (foundry-role
), and the newly created role.
foundry-role
) assigned to it.TOKEN ID
and TOKEN SECRET
. You will need them to configure Foundry.TOKEN ID
and TOKEN SECRET
will only be displayed the first time you save the token. You will need to create a new token to get a new TOKEN ID
and TOKEN SECRET
.
Learn more about token management in NetSuite. ↗
The NetSuite SuiteQL connector requires network access to the NetSuite instance to which you want to connect.
If you are connecting via a direct connection, you will need to add the following egress policy to the source:
If this egress policy does not exist, you can request the egress policy; otherwise, you can add the egress policy.
If you are connecting with an agent runtime, you must ensure that the agent host has firewalls open to the host names, IP addresses, and ports required to connect to your NetSuite Connect instance.
Option | Required? | Description |
---|---|---|
Account ID | Yes | NetSuite Account ID, found as a prefix in your NetSuite's instance URL |
Client ID | Yes | CLIENT ID copied when creating the foundry-integration |
Client secret | Yes | CLIENT SECRET copied when creating the foundry-integration |
Access token | Yes | TOKEN ID copied when creating the TBA token |
Access token secret | Yes | CLIENT ID copied when creating the TBA token |
The NetSuite SuiteQL source can be explored to discover tables and create new syncs. You can also manually create new syncs from the overview page of the source.