[MChammaTX]

A NetSuite Partner that implemented one of our subsidiaries a few years ago pushed all the customization objects from our sandbox account (which was being used to develop) into the SuiteBunlde repository and then into Production, so SBOX -> SBREPO -> PROD.

Apparently (I wasn’t here at the time) they then told us we could never refresh our SBOX from PROD or it would wipe out the bundle in the SuiteBundle repository. We’ve been paying for a dormant SBOX that we can’t refresh.

This doesn’t really make sense to me although I’ve never deployed a SuiteBundle based on this scenario.

If we:

a) refresh our SBOX that is linked to the bundle in the repo

or

b) discountinue the SBOX that is linked to the bundle in the repo

what impacts does this have?

Thanks for any help.
This is a cached copy. Click here to see the original post.

[michoel]

Per the documentation:

A sandbox refresh has the following impacts on bundle definitions:

Bundle definitions in sandbox are maintained if you installed the bundle into another sandbox or production account. NetSuite maintains the bundle definition in the sandbox account as well as the link between the bundle source and target accounts.As a result, a bundle installed from sandbox into production can be continually updated with changes made to the source bundle in sandbox.
Bundle definitions are not maintained if the bundle in the sandbox account was not installed in another sandbox or production account.

[Author]

Posts