Deploying to a NetSuite Sandbox for Testing and Development
Deploy your applications to a NetSuite sandbox for safe testing and development, enhancing workflow without affecting production data.
Deploying to a NetSuite sandbox is a crucial step in testing applications and customizations before making changes to your production account. This allows developers to ensure the quality and stability of their deployments without risking any disruption to live operations.
Why Use a Sandbox for Deployment?
Sandbox accounts are mirrors of your production environment, making them ideal for:
- Testing new features and customizations
- Troubleshooting existing implementations
- Training personnel on new processes
- Safely experimenting with third-party integrations
Actions taken in a sandbox do not affect the production environment, ensuring a safe space for development. However, it is essential to follow specific deployment procedures to avoid issues.
Steps to Deploy to a Sandbox Account
Follow these steps to successfully deploy your application to a sandbox account:
-
Prepare Your Environment
Open your command line or terminal window. -
Execute Deployment Command
From the top-level directory of your source files, use one of the following commands based on your development environment:- For theme development:
bashgulp theme:deploy
- For extension development:
bashgulp extension:deploy
- For Core SuiteCommerce Advanced development:
bashgulp deploy
On first deployment, this will create a
DeployDistributionfolder that will house the compiled source files.Important Note:
If you have previously deployed to a different account, delete the.nsdeployfile first to enter the sandbox login credentials. - For theme development:
-
Enter Authentication ID
When prompted, input the authentication ID associated with your sandbox account. -
Select Sandbox and Role
In NetSuite, choose the appropriate sandbox account and required role. Click Allow to generate your authentication token and secret.Permissions Warning:
Ensure the role you select has the necessary permissions to deploy. In most cases, the Administrator and SCDeployer roles will suffice. For details on creating custom roles, refer to the guide on Developer Tool Roles and Permissions. -
Upload Files
Navigate to your Web Site Hosting Files, selecting the appropriate path:- For SuiteCommerce:
Web Site Hosting Files > Live Hosting Files > SSP Applications > NetSuite Inc. - SCS - For SuiteCommerce Advanced:
Web Site Hosting Files > Live Hosting Files > SSP Applications > NetSuite Inc. - SCA <version> Development
- For SuiteCommerce:
After setting up the connection, the contents from your DeployDistribution directory will upload to the NetSuite File Cabinet of your sandbox account. Monitor the process completion, as it may take a while depending on file sizes.
Conclusion
Deploying to a sandbox effectively protects your production environment while allowing extensive testing and development. This structured approach ensures you can innovate freely in a controlled setting, thus maintaining operational integrity.
Source: This article is based on Oracle's official NetSuite documentation.
Frequently Asked Questions (4)
What steps should I follow to deploy an application to a NetSuite sandbox?
What happens if I accidentally deploy to the wrong sandbox account?
Do I need specific permissions to deploy to a NetSuite sandbox?
Is there a command difference when deploying themes versus extensions in NetSuite sandbox?
Was this article helpful?
More in Sandbox
- Exception Management Now Supported in Sandbox Accounts
Exception Management is now available in Sandbox accounts, using production-trained models to evaluate workflows safely.
Advertising
Reach Sandbox Professionals
Put your product in front of NetSuite experts who work with Sandbox every day.
Sponsor This Category