Audience: Administrator

Overview

eXtendTech uses NetSuite bundles and SuiteApps to distribute pre-built solutions, customizations, and configurations across different NetSuite accounts. These packages contain various components such as custom fields, forms, records, scripts, workflows, roles, and preferences. While bundles enable deployment and updates to your eXtendApps, you might notice that certain customized fields or preferences revert to their previous state after a bundle update.

This article explains the key reasons behind these resets and offers guidance on effectively managing your customizations following a bundle update.

What is a NetSuite Bundle Update?

A NetSuite bundle update occurs when the provider of an installed bundle releases a new version of their solution. This update typically includes enhancements, bug fixes, or new functionalities. When you install an update, NetSuite's SuiteBundler tool compares the new bundle definition with the existing components in your account. The primary goal of the update process is to bring your installed bundle components up to the latest version defined by the bundle provider.

Why Do Resets Occur?

The core reason why your customizations may appear to be reset after a bundle update is due to the ownership and management of the bundle's components by the bundle itself.

The most crucial information to understand is this: If you have customized components that are specific to the bundle (i.e., components originally provided by and primarily managed by the bundle), those customizations may be reset during a bundle update and will often need to be re-applied or reconfigured afterward.

Bundle Overriding its Own Components: When a bundle is updated, it pushes the latest version of its own defined components. If you have directly modified a component that originated from and is "owned" by the bundle (e.g., a custom record's base preferences, a custom field's label or display type, a script's configuration parameters, or a custom form's layout), the bundle update will often overwrite your local changes with the bundle's latest definition. This ensures the bundle's intended functionality and consistency across all installations.

Impacted Components

Components most susceptible to resets during a bundle update typically include:

  • Custom Fields: Defaults, sourcing, validation rules, display types, labels (if the label is redefined by the bundle).
  • Custom Forms: Layouts, subtab arrangements, field placement (if the form is managed by the bundle).
  • Custom Records: Definitions, fields, and potentially data (if the bundle specifies data replacement).
  • Preferences: Specific application preferences or configurations managed by the bundle.
  • Roles: Permissions and restrictions (if the role is part of the bundle).
  • Center Tabs: Layout, included links, and associated permissions (if the center tab is part of the bundle).
  • Workflows and Scripts: If you modify a bundle-provided workflow or script, its definition may be overwritten by the bundle update.

Best Practices to Minimize Impact

While some resets are inherent to the bundle update process, you can adopt several best practices to minimize disruption:

  • Identify Bundle-Specific Customizations: Be aware of which custom fields, forms, roles, and preferences were originally introduced by an installed bundle. Customizations made on components owned by a bundle are most susceptible to being reset.
  • Document Your Customizations: Document any custom changes you have made to bundle-specific components. This detailed record will be valuable for quickly re-applying them if they are reset.
  • Re-apply Customizations: Be prepared to re-apply any customizations that are reset after a bundle update. This might involve re-setting field defaults, re-adding fields to forms, or reconfiguring preferences according to your specific business needs.

By understanding how bundle updates work and adopting these proactive measures, you can manage your NetSuite environment more effectively and ensure that your critical customizations are preserved or easily re-established after an update.