@Keith Fetterman I will hopefully be able to give a detailed answer about this shortly but for now I will say, "yes, we're aware of this issue"

Excellent. Awareness is the first step to solving it. 😄 I shared my note to you with Flo since she has also helped me with the SCEM. Once the version management handling past versions and local development of this is worked. Out, the theme&extensions framework will be killer and stable like the Kilimanjaro version.

Awareness is the first step to solving it

What I'm trying to say is that we are making changes in the next release (🚨SAFE HARBOR STATEMENT🚨) to address this issue and once the release notes are published I can discuss it more

Thanks for letting me know.

@Keith Fetterman Take a look at the 'target versions' section and let me know if you think this solves your use case https://developers.suitecommerce.com/announcement-suitecommerce-and-suitecommerce-advanced-20192

@Steve Goldberg, thanks for sending this and posting the article. I reviewed the section you mentioned (I’ll review the rest later.) I am not sure if it will solve the problem we experienced or not from the write up. Assume you developed an SCS site on 2019.2 using an extension (version 1) from a bundle (version 1). When SCS 2020.2 is deployed, the current version of the bundle is now 2 and the extension is version 2. The bundle is updated replacing version 1 of the extension with version 2. I switch from SCS to SCA 2020.2 and re-run the activation. Will the activation show version 1 of the extension even though it no longer exists in the bundle?

So, 'old' versions of extensions are saved on your account. 1) Develop on an SCA 19.2 site and write your extension with the target version ~19.2.0. Deploy and activate, every is cool. 2) Develop on an SC 19.2 site; activate same extension, all good. 3) Later: SC 19.2 site is updated to 20.1 but SCA is still 19.2. 4) Extension does not show to SC 20.1 site but does to SCA 19.2 site. 5) Extension updated locally to version 2, and targets ~20.1.0. Deploy. 6) Activation screen for SCA 19.2 site still shows version 1 of extension; SC 20.1 site does not see version, and only sees version 2.

Yes that makes sense. Where are the old versions saved in the file cabinet? In the specific SSP application’s extensions folder. If so, my problem will not be solved. In the scenario we had, the SC to SCA switch didn’t occur until 20.1, but the SC site even though it was upgraded to 20.1, the extension is still 1.0. When the SCA 20.1 is installed, it’s put in a different SSP application folder in the file cabinet, and it’s extensions folder doesn’t have the old extension version. If the old versions of the extensions are stored somewhere other than the bundle folder and the SSP applications folder in the file cabinet, the SCA 20.1 version could access this location to pull the old versions of the extensions.

Extensions are versioned in SuiteScripts > Deploy_Extensions

Okay. Great. Are the extensions that are in published bundles, like SuiteSuccess - Customization CB2B, placed in the SuiteScripts > Deploy_Extensions folder? If they are, then that solves the previous extensions version problem. But, I think there is still an issue with what is mentioned in the article. Here is what I am not sure about. If the SC website running version 1 of the extension is upgraded to 20.1, the bundle that contains the extension is updated and the extension is now v2, then the SCA 20.1 bundle is installed, the website’s touch points are changed to SCA 20.1, will the activation show version 1 or version 2 or both when re-activating the activation? If it’s only version 2 of the extension, the problem we encountered will not be resolved.