@Steve Goldberg I have been thinking that we need expanded version management of extensions and bundles where we can install and activate old versions. Currently, when you create a new activation it appears that we’re forced to use the latest version of an extension. This is fine for new websites or installing new extensions, but it creates problems for older websites under certain scenarios. For example, we moved an existing website from SuiteCommerce to SCA. The SC website had older versions of the SuiteSuccess extensions activated. The SC website was built using 2018.1 theme and extensions. When the SCA bundle was installed and the website switched to the SCA SSP application, the old extension versions didn’t exist in the SCA folders. When the existing website activation was re-ran, only the latest versions of the extensions were available because the SuiteSuccess bundle had been updated. What would have been ideal is to maintain multiple versions of the SuiteSuccess extensions and the choice to activate any version that was installed or previously installed in the account. I can think of other scenarios where you might want to activate older extensions that was installed in an account but has been removed due to bundle updates. Writing this up in a NetSuite Support case enhancement request isn’t easy because it involves enhancing bundle version management as well as extension management. Is there discussion internally about this? If not, what’s the best forum to get the discussion going?