Bundle Support during NetSuite Release Phasing

Upgrades of NetSuite accounts to each new release occur as a phased process. During phasing of a new release, some accounts are still using the lagging version of NetSuite during the time that other accounts have been upgraded to the leading version. During this time period, you are likely to be using a different NetSuite version than some of the accounts where your bundles are installed, so you need to be aware of the following:

Bundles developed with the lagging version can be installed into accounts that are already using the leading version.
Bundles developed with the leading version can be installed into accounts that are still using the lagging version, but note the following limitations:
- When a user in a lagging version account installs a bundle from a leading version account, any object types in the bundle that are not supported in the lagging version are not installed, resulting in potentially serious impact to bundle function.
- A bundle with a SuiteScript that uses a new API available only in the leading version can be installed into a lagging version account, but the script may not function correctly because the lagging version does not support the API.

You should avoid distributing bundles containing any new leading version API to accounts still using the lagging version. To accomplish this purpose, you can create a bundle installation script that uses the getVersion() method to check the target account version, and prevents installation of the associated bundle if the lagging version is in use. See Using Bundle Installation Scripts and the SuiteScript help topic Setting Up a Bundle Installation Script.

Related Topics