ANS-0803 · OTHER
How to Manage NetSuite Bundle Deployments and Third-Party Integrations?
This guide outlines best practices for deploying NetSuite bundles, managing third-party SuiteApps, and handling NetSuite Fixed Assets during migration from sandbox to production.
Short answer
When migrating NetSuite bundles from sandbox to production, selectively choose components for deployment to avoid conflicts. For third-party SuiteApps, leverage managed bundle updates. NetSuite Fixed Assets can be deployed independently. Avoid attempting to embed third-party bundles within a source bundle, as this is not a supported practice and can lead to deployment issues.
Scenario
Organizations often need to migrate NetSuite configurations, including custom bundles and integrated third-party applications, from a sandbox environment to production. The challenge lies in ensuring a smooth deployment process, managing dependencies, and avoiding conflicts, particularly with external SuiteApps and NetSuite's own Fixed Assets module.
Solution
To manage dependencies and avoid conflicts, selectively choose the specific components required for deployment when creating a bundle.
For third-party SuiteApps, it is important to understand that many are now managed bundles, where the bundle provider handles updates, reducing the need for active, individual deployment coordination by the customer.
NetSuite Fixed Assets can be deployed either before or after the main Suite Bundle, or it may have been previously deployed.
It is important to note that attempting to include third-party bundles directly within a source bundle for dependency management is not a standard or supported feature in NetSuite's current bundling process and can lead to deployment conflicts.
Expert NetSuite Support
Need help with this NetSuite issue?
Other consulting and configuration support