Features Available for Testing in a Sandbox

A sandbox account is a copy of your production account, as of a specific date and time. As a sandbox is only a copy of the information from your production account, the actions you perform in the sandbox do not affect the information in your production account.

Many NetSuite features are available for testing in sandbox accounts. Some features are only available in a limited form in sandbox accounts, and a few behind-the-scenes tasks that run in your production account do not run in your sandbox. For example, billable components information is not calculated for the sandbox. To view your Total Storage Size (MB) information, go to Setup > Company > View Billing Information in your production account. The billing information page in a sandbox account displays the billing information copied from production. Therefore, the Total Storage Size (MB) information displayed in the sandbox is not changed by tasks completed in the sandbox account, such as deletion of custom records.

During sandbox refreshes, certain objects are not copied from your production account. For more information, see Data That is Not Copied from Production to Sandbox.

See the following for details about features in sandbox accounts:

Features Available for Full Testing in Sandbox Accounts
Features Available for Limited Testing in Sandbox Accounts
Features Not Available for Testing in Sandbox Accounts

Features Available for Full Testing in Sandbox Accounts

Features in the following table can be fully tested in sandbox accounts.

Feature	Testing Notes
Bulk Merge
CTI Integration	Partners are Contivio and Five9
CSV Import
Custom Records	Security-sensitive fields on custom records will display the same values displayed in the production account.
Email Campaigns	Email campaigns must have fewer than 25 recipients. Note: The From header on email you send from your sandbox account will be rewritten to use the SMTP-related email address (netsuite.com). For more information, see FROM Headers in Email Can Be Rewritten.
Email Case Capture
Email Notifications and Outgoing Email	Saved searches are automatically set to inactive in sandbox accounts. For email routing options, see Setting Preferences for Sandbox Email.
Intellesync
OpenID Connect (OIDC)	For instructions, see OpenID Connect (OIDC) Single Sign-on.
Reports Scheduled Reports	Scheduled Reports do not send emails. Alert Me When Ready reports do send emails (assuming a user initiates this action). Note: The company preference for sandbox email is evaluated after the report is executed and prepares to send email. Depending on the preference specified, the email is sent to a specific user or not sent at all. See Setting Preferences for Sandbox Email for more information.
Saved Searches Scheduled Saved Searches	Scheduled Searches and Email Alerts behave as they do in the production account. Note: The company preference for sandbox email is evaluated after the report is executed and prepares to send email. Depending on the preference specified, the email is sent to a specific user or not sent at all. See Setting Preferences for Sandbox Email for more information.
Secure Domains	It is possible to test and verify a custom secure domain from the user’s perspective in a sandbox account. Note: Do not attempt to reuse domains that are already deployed in your production account. You must set up a unique domain for each of your accounts: production, sandbox, and Release Preview. See Manual Certificates and Set Up Domains for Web Stores for more information.
Server SuiteScript
Client SuiteScript
SuiteAnalytics Connect (formerly ODBC)
SuiteFlow (Workflows)	SuiteFlow can be fully tested. Note: Scheduled SuiteFlow (workflows) are not run automatically in sandbox accounts, but can be tested manually.
Telephony Integration (Basic)
Two-Factor Authentication	2FA Settings are shared between a production account and the sandbox accounts that are associated with that production account. Users do not need to recreate their 2FA Settings for sandbox accounts.
SOAP Web Services	The SOAP requests and responses for each job can be viewed in the SOAP Web Services Usage Log. In sandbox accounts, requests and responses are accessible for one day. For more information, see Using the SOAP Web Services Usage Log.

Feature

Testing Notes

Bulk Merge

CTI Integration

Partners are Contivio and Five9

CSV Import

Custom Records

Security-sensitive fields on custom records will display the same values displayed in the production account.

Email Campaigns

Email campaigns must have fewer than 25 recipients.

Note:

The From header on email you send from your sandbox account will be rewritten to use the SMTP-related email address (netsuite.com). For more information, see FROM Headers in Email Can Be Rewritten.

Email Case Capture

Email Notifications and Outgoing Email

Saved searches are automatically set to inactive in sandbox accounts. For email routing options, see Setting Preferences for Sandbox Email.

Intellesync

OpenID Connect (OIDC)

For instructions, see OpenID Connect (OIDC) Single Sign-on.

Reports

Scheduled Reports

Scheduled Reports do not send emails. Alert Me When Ready reports do send emails (assuming a user initiates this action).

Note:

The company preference for sandbox email is evaluated after the report is executed and prepares to send email. Depending on the preference specified, the email is sent to a specific user or not sent at all. See Setting Preferences for Sandbox Email for more information.

Saved Searches

Scheduled Saved Searches

Scheduled Searches and Email Alerts behave as they do in the production account.

Note:

Secure Domains

It is possible to test and verify a custom secure domain from the user’s perspective in a sandbox account.

Note:

Do not attempt to reuse domains that are already deployed in your production account. You must set up a unique domain for each of your accounts: production, sandbox, and Release Preview.

See Manual Certificates and Set Up Domains for Web Stores for more information.

Server SuiteScript

Client SuiteScript

SuiteAnalytics Connect (formerly ODBC)

SuiteFlow (Workflows)

SuiteFlow can be fully tested.

Note:

Scheduled SuiteFlow (workflows) are not run automatically in sandbox accounts, but can be tested manually.

Telephony Integration (Basic)

Two-Factor Authentication

2FA Settings are shared between a production account and the sandbox accounts that are associated with that production account. Users do not need to recreate their 2FA Settings for sandbox accounts.

SOAP Web Services

The SOAP requests and responses for each job can be viewed in the SOAP Web Services Usage Log. In sandbox accounts, requests and responses are accessible for one day. For more information, see Using the SOAP Web Services Usage Log.

Features Available for Limited Testing in Sandbox Accounts

The following features are only available in a limited form in sandbox accounts:

Feature	Testing Notes
Alternative Payment Methods	No actions taken (no payment sent). Test mode is on for all payment processing profiles.
Credit Card Processing	No actions taken. To test your billing processes or credit card processing, use only test credit card numbers and a valid expiration date. Important: See Credit Card Processing in Your Sandbox After a Refresh for more information.
Direct Deposit	No actions taken.
NetSuite Connector	You cannot connect multiple NetSuite accounts (production, sandbox, Release Preview) to the same NetSuite Connector account. You can only connect one NetSuite account to a NetSuite Connector account at a time. The NetSuite sandbox account requires you to create a NetSuite Connector sandbox account. For more information, see General NetSuite Connector FAQ and Checking Accounts for NetSuite Connector Deployment.
PayPal Integration	No actions taken.
Perquest	No actions taken.
SAML Single Sign-on	SAML configuration is not copied from the production account to the sandbox account. You must configure SAML in your sandbox account after each refresh.
Scheduled SuiteScripts	Scripts scheduled in production are disabled by default in sandbox accounts, but you can set them up and test them. For details, see Scheduled Script Execution.
SSN or TIN (Social Security Number or Tax Identification Number)	Real numbers not copied. Use only test numbers.
Token-based Authentication	Tokens created using the Token-based Authentication feature in your NetSuite production account are not copied to your sandbox account. To test this feature, you must create tokens in that sandbox account. Each time your sandbox is refreshed, you must create new tokens in that sandbox account.
UPS/FedEx Integration for Shipping Labels	No actions taken.
Website and Web Store	Websites that exist in your production account are copied to your sandbox, but you must set up domains after a refresh. Domains are not copied from your production account to your sandbox account. After a sandbox refresh, you must set up domains in the sandbox account. See Automatic and Manual Certificates and Set Up Domains for Web Stores for more information. Note: If you have multiple sandbox accounts, ensure that the domains are unique across all of your accounts. An error message is generated if there are duplicate domains. Websites created only in your sandbox account are lost after a sandbox refresh, and need to be recreated. For more information, see Getting Started.

Feature

Testing Notes

Alternative Payment Methods

No actions taken (no payment sent).

Test mode is on for all payment processing profiles.

Credit Card Processing

No actions taken.

To test your billing processes or credit card processing, use only test credit card numbers and a valid expiration date.

Important:

See Credit Card Processing in Your Sandbox After a Refresh for more information.

Direct Deposit

No actions taken.

NetSuite Connector

You cannot connect multiple NetSuite accounts (production, sandbox, Release Preview) to the same NetSuite Connector account. You can only connect one NetSuite account to a NetSuite Connector account at a time. The NetSuite sandbox account requires you to create a NetSuite Connector sandbox account.

For more information, see General NetSuite Connector FAQ and Checking Accounts for NetSuite Connector Deployment.

PayPal Integration

No actions taken.

Perquest

No actions taken.

SAML Single Sign-on

SAML configuration is not copied from the production account to the sandbox account. You must configure SAML in your sandbox account after each refresh.

Scheduled SuiteScripts

Scripts scheduled in production are disabled by default in sandbox accounts, but you can set them up and test them.

For details, see Scheduled Script Execution.

SSN or TIN (Social Security Number or Tax Identification Number)

Real numbers not copied. Use only test numbers.

Token-based Authentication

Tokens created using the Token-based Authentication feature in your NetSuite production account are not copied to your sandbox account. To test this feature, you must create tokens in that sandbox account. Each time your sandbox is refreshed, you must create new tokens in that sandbox account.

UPS/FedEx Integration for Shipping Labels

No actions taken.

Website and Web Store

Websites that exist in your production account are copied to your sandbox, but you must set up domains after a refresh.

Domains are not copied from your production account to your sandbox account. After a sandbox refresh, you must set up domains in the sandbox account.

See Automatic and Manual Certificates and Set Up Domains for Web Stores for more information.

Note:

If you have multiple sandbox accounts, ensure that the domains are unique across all of your accounts. An error message is generated if there are duplicate domains.

Websites created only in your sandbox account are lost after a sandbox refresh, and need to be recreated. For more information, see Getting Started.

Features Not Available for Testing in Sandbox Accounts

The following features are not available for testing in sandbox accounts:

Fax
Memorized Transactions
NetSuite for Outlook
Outlook Integration
Payroll

Features Available for Full Testing in Sandbox Accounts

Features Available for Limited Testing in Sandbox Accounts

Features Not Available for Testing in Sandbox Accounts

Related Topics