Deprecating a Bundle

You can deprecate a bundle to indicate that it is no longer the most up to date version available. When you deprecate a bundle, you specify another bundle as a replacement, newer version. You specify this replacement bundle by its name and NetSuite account ID. For instructions, see Steps to Deprecate a Bundle.

You can deprecate a bundle only after you have copied this bundle from one account to another. The copy of the bundle serves as the basis for development of a new bundle version. For details, see Copying a Bundle to Other Accounts.

A bundle may have multiple copies, and each copy may in turn have multiple copies of its own. When you deprecate a bundle, the replacement bundle must be a direct descendant of the deprecated bundle. To understand the chaining of bundle copies, see Ancestry of Copied Bundles.

The effects of deprecation are different for managed bundles and other bundles. For details, see Results of Deprecating Non-Managed Bundles and Results of Deprecating Managed Bundles.

On the Saved Bundles page, a deprecated bundle includes a Deprecated By column with the bundle ID and account ID of the replacement bundle, in the format <Bundle ID> Account:<Account ID>. For other details about deprecated bundles, see Notes about Deprecated Bundles.

Important:

Deprecation is available only for customization bundles. You cannot copy or deprecate configuration bundles. Also, you cannot deprecate a bundle that has been created in a sandbox account.

Steps to Deprecate a Bundle

Complete the following procedure to deprecate a bundle.

To deprecate a bundle:

  1. Go to Customization > SuiteBundler > Create Bundle > List.

  2. In the Action list for the bundle you want to deprecate, click Set Availability.

  3. On the Bundle Availability page, in the Deprecate Bundle section, select a replacement bundle for the bundle to be deprecated.

    • Deprecate With Bundle lists bundles that are descendants of the deprecated bundle, in accounts where you have a role with SuiteApp Marketplace permission.

    • The format of list options is <Bundle ID> Account:<Account ID>.

  4. Review other settings on the page. You may want to change the level of availability for the deprecated bundle or Visible By All setting.

  5. Save the changes to the Bundle Availability page.

Ancestry of Copied Bundles

Each copied bundle can have multiple ancestors, depending upon the versioning strategy used for the bundled solution. An ancestor can be the bundle from which a bundle was directly copied, or a bundle from which a chained set of copies was made. The following illustration shows a chained set of copies. In this illustration, Bundle A is the common ancestor of all of the other bundles.

Note that bundles must be deprecated by their descendants. For example, in the scenario illustrated here, you could deprecate Bundle B and replace it with Bundle D, but you could not replace it with Bundle C.

Deprecating a Bundle section of the Saved Bundles page

Results of Deprecating Non-Managed Bundles

Results of Deprecating Managed Bundles

Deprecation of managed bundles is handled differently than deprecation of non-managed bundles. Managed bundle deprecation allows continuing support of an existing bundle version that has been installed in target accounts, including the ability to release bug fixes and minor changes, at the same time that development of a new version is occurring. See Phased Upgrade of Managed Bundles.

Notes about Deprecated Bundles

Related Topics

SuiteApp Creation and Distribution
Saved Bundles
Bundle Availability
Sharing a Bundle
Implementing Phased Updates by Setting Bundle Availability
Copying a Bundle to Other Accounts
Managed Bundles Overview
SuiteApp Development Process with SuiteBundler
Phased Upgrade of Managed Bundles

General Notices