Using Integration Records in Sandbox Accounts

You can install a sandbox integration record in your production account by bundling or auto-installation. You can also install records in your sandbox from other sources, like your production account or another NetSuite account.

For details, see Auto-Installation of Integration Records and Bundle Installation of Integration Records.

Important:

Creating an integration record in a sandbox and installing it in production means you won't own it in production. Therefore, you won't be able to update all fields in the production account. For full control, create the integration record directly in the production account.

After creating an integration record in your sandbox and then installing it in you production account and after a sandbox refresh, integration record settings are copied. For details, see Sandbox Refresh Impact on Integration Records.

Development Process for Integration Records

Create and test an integration record in your sandbox account.
After testing, create a new integration record in your production account using the tested settings.

Updating an integration record in one account can affect behavior in other accounts differently. For more details, see the following sections:

Common Fields Between Production and Sandbox Accounts
Sharing Integration Records Between Sandbox and Production Accounts
Sandbox Refresh Impact on Integration Records

Note:

For details on using token-based authentication with integration records with production and sandbox accounts, see Token-based Authentication Credentials and Accounts.

Common Fields Between Production and Sandbox Accounts

Integration records have account-specific fields and fields that are common between all accounts. The following fields are common:

Application ID
Name
Description
Authentication
Consumer Key
Consumer Secret

The Consumer Key and Consumer Secret are not directly editable. You cannot change them directly, but you can regenerate them. You can only regenerate Consumer Key and Consumer Secret in the original account.

Important:

The Application ID isn't editable.

Note:

For details on distributing an integration record, see Distributing Integration Records.

Sharing Integration Records Between Sandbox and Production Accounts

You can create an integration record in sandbox or production and install or auto-install it in the other account, or the other way around. In this case, you cannot fully manage the integration record in the account where you installed or auto-installed it, and you can only edit the State and the Note fields.

Sandbox Refresh Impact on Integration Records

During a sandbox refresh, production data overwrites sandbox content. A sandbox refresh is one way to uninstall an integration record. If a record was only in sandbox, it's removed during the refresh. After the refresh, you can auto-install the record back into sandbox if you have the application ID. However, you won't have full control over the record in sandbox.

After a sandbox refresh, review and block unused integration records, as production records are copied to sandbox with their settings.

When auto-installing, note that initial installation data isn't kept. Data contained in the SOAP Web Services Execution Log, the State field, and the Note field is deleted. For details, see Auto-Installation of Integration Records.