This article is relevant if you need to uninstall a NetSuite Bundle but want to preserve data that would be removed or deleted.
Background
When working with the NetSuite platform, there are times when we need to update or modify database objects, which could result in potential data loss. This situation might arise, for instance, when a SuiteApp supplier offers an upgrade to their technologies that negatively affects certain customizations made to their records.
In any scenario where data loss is anticipated, a NetSuite Administrator becomes rightfully concerned about the appropriate course of action. Common sense dictates exporting the data for preservation, allowing for its re-introduction into NetSuite after the necessary technology upgrade is completed. This re-introduction typically occurs post-upgrade.
While effective, this approach can be problematic if the data resides in locked objects. For example, consider a custom field in a financial transaction when the accounting books are closed and locked. Updating this field would require re-opening the books, a prospect that understandably makes accountants nervous.
We encountered this exact scenario with a client. During my planning with one of our Senior Technical Analysts, it occurred to me that an alternative, simpler approach might be possible.
Utilize NetSuite’s SuiteBundler Technology to Preserve Data
When uninstalling a NetSuite SuiteBundle, NetSuite will remove the custom objects in that account, leading to data loss. Similarly, when upgrading a bundle, the installer will alert you to any changes that might result in data loss.
When faced with a situation where data preservation is crucial, here is an innovative approach:
The NetSuite Product Team has been advocating for the use of the SuiteCloud Development Framework (SDF) tools for advanced software customization and database object distribution. However, the original SuiteBundler technology remains widespread within the platform. The fundamental idea of SuiteBundler is to create objects in a NetSuite account that can be bundled and then distributed to a target account. Importantly, the target account incorporates the new object while maintaining a reference to the original source object.
This introduces an opportunity for data preservation. A target database object can be referenced by multiple bundles. If a target database object is referenced by more than one bundle, removing one bundle won’t result in the loss of the object. In other words, as long as a target object is referenced by at least one bundle, NetSuite will not remove the object.
How can we leverage this to our advantage?”
Leverage Sandbox Account to Create a Temporary Bundle
This solution is effective only for organizations that have invested in a NetSuite Sandbox. It assumes that our Sandbox contains the worrisome database object, initially sourced from an original SuiteBundle. We craft a new temporary SuiteBundle in the sandbox to address this, referencing the worrisome database object. We then install this new temporary SuiteBundle in our Production Account. Since there are no changes to the targeted database object’s structure, the risk of harm is nullified. Consequently, the worrisome database object becomes double-referenced.
Before initiating this operation, please refer to the following section on data safekeeping.
Once the worrisome object is double-referenced, modifying the original SuiteBundle is safe. Even if it warns of removing the worrisome object, NetSuite will preserve it due to the double reference. This allows the Administrator to perform the upgrade safely, ensuring data preservation. After completing the upgrade, the Administrator can decide whether to remove the temporary bundle.
Click on the related image to gain a better understanding.
Backup Data for Safekeeping
We thoroughly tested the process before implementing this operation in a client account. As a standard practice, we backed up the data by exporting it for safekeeping. You should do the same. This step is crucial to establish a fail-safe strategy, especially if the assumptions outlined earlier do not hold true.
Deepening Your NetSuite Administrative Knowledge
In the cloud-based NetSuite system, it’s crucial to be cautious when performing operations that could result in data loss. Although NetSuite offers a backup database restoration, this process can be slow to initiate and cumbersome to work with. It involves creating a new restored Sandbox from the production backup, requiring additional effort from the Administrator to relocate the data back into production; let’s avoid that.
Exploring options like the double-referenced database object can save time. However, these should always be tested before implementation. In every scenario, it’s best practice to export data before undertaking any risky operation. This new option discussed here has the potential to reduce risk and shorten data restoration times.
Our clients appreciate our deep technical expertise in the NetSuite platform, a skill set we’ve been honing since our commitment began in 2008. With a team of high-caliber professionals, we excel at collaborating in complex scenarios. This teamwork not only leads to superior client service but also cultivates ‘Ninja-level’ expertise.
If you find this article useful, consider signing up for notifications of new posts. And if you’re an independent thinker, highly creative, and interested in aligning with recognized NetSuite experts, let’s start a conversation.
Marty Zigman
Holding all three official certifications, Marty is regarded as the top NetSuite expert and leads a team of senior professionals at Prolecto Resources, Inc. He is a former Deloitte & Touche CPA and has held CTO roles. For over 30 years, Marty has produced leadership in ERP, CRM and eCommerce business systems. Contact Marty to set up a conversation.
More Posts - Website - Twitter - Facebook - LinkedIn - YouTube
