ANS-0805 · CUSTOM FIELDS, RECORDS & FORMS
Navigating NetSuite Bundles: Common Pitfalls When Deploying from Sandbox to Production
Understand the critical risks and irreversible changes that can occur when deploying NetSuite bundles, especially in multi-user environments.
Short answer
Deploying NetSuite bundles from Sandbox to Production requires extreme caution due to potential irreversible changes, especially in shared environments. Uncoordinated modifications, such as converting custom lists to records, can lead to unexpected system behavior and permission issues. Always verify all bundle components and their impacts before installation.
Scenario
In a NetSuite account managed by multiple users, uncoordinated changes in a Sandbox environment can lead to significant issues during bundle deployment. For instance, a custom list might be converted to a custom record for testing purposes without proper communication. If a bundle is then created that includes components referencing this modified list, such as a custom form with a custom field linked to it, installing this bundle in Production can trigger irreversible changes and unintended permission assignments.
Solution
Deploying bundles from a NetSuite Sandbox to Production environment, especially in accounts with multiple administrators, users, or consultants, carries significant risks due to potential uncoordinated changes. Understanding these 'gotchas' is crucial for a smooth deployment.
Irreversible Custom List Conversion
A Custom List can be converted into a Custom Record with a single action. However, this operation is irreversible. If a custom list is converted in Sandbox and a bundle containing components that reference this (now custom record) list is deployed to Production, the list in Production will also be irreversibly converted.
Custom Field Inclusion in Bundles
Custom fields are not automatically included in a bundle, even if they are part of a saved search or custom form that is being moved. If a saved search includes a formula referencing a custom field, or if a custom form utilizes a custom field, these custom fields must be explicitly added to the bundle to ensure proper deployment.
Permission Discrepancies
Converting a custom list to a custom record has collateral impacts on permissions. Custom Record Permissions differ from those used to manage Access to Custom Sublists. Deploying a bundle that triggers such a conversion can inadvertently grant users broader access (e.g., to create, edit, or delete records) than intended, potentially leading to data integrity issues or system disruptions.
Unpredictable Bundle Impacts
The Bundle Components List and Installation Override Preferences in NetSuite can be complex, making it challenging to predict all the impacts of installing a bundle. It is critical to thoroughly review all components and understand their implications before proceeding with installation, as bundles can introduce irreversible consequences.Given these potential problems, manually re-creating components in Production is often recommended for critical or complex changes, despite being time-consuming for numerous components. Always ensure complete control and understanding of all changes before installing a bundle, as the consequences can be severe and irreversible.
Expert NetSuite Support
Need help with this NetSuite issue?
Custom Fields, Records & Forms consulting and configuration support