I upgraded from SCA 2019.1 to SCA 2022.1 and deplo...
# suitecommerce
c
I upgraded from SCA 2019.1 to SCA 2022.1 and deployed touchpoints. However, I cannot deploy the core SCA as I encountered the following error “Please make sure the selected account/molecule has the “SuiteCommerce Advanced” bundle installed.” If I inspect the source code, I can verify that the website loads SCA 2022.1. So why is NS not seeing the bundle?
s
Have you actually installed the SCA 22.1 bundle on the account?
Or just deployed new code
c
Yes, SCA 22.1 bundle has been installed and touch points connected. The source code even shows that the website is using 22.1.
s
Can you open Advanced > distro.json and tell me what values you have for scriptId and deployId
c
_“scriptId”_: “customdeploy_ns_sca_deployer_2022_1_0", _“deployId”_: “customdeploy_ns_sca_deployer_2022_1_0",
I had to update the deploy script ID as it has by default - customdeploy_ns_sca_deployer_2020_1_0
Copy code
Error: Deployment scriptlet not found, aborting. 
Please make sure the selected account/molecule have the "SuiteCommerce Advanced" bundle installed.
[12:32:23] The following tasks did not complete: deploy, upload
[12:32:23] Did you forget to signal async completion?
What is weird is that I can deploy to their sandbox account.
s
I see. Did you get the deploy error before you modified those script IDs?
c
yes
s
🤔
c
Both the website record and domain have the touch points applied. Then the v2 ssp app touch points are applied.
s
Have you checked whether the script it is referencing has actually been deployed?
And you've done Link to Domain / Link to Site (I forget which)?
c
Looking at the script deployment now… I know we set the permissions for our deployer role. Yes, to the 2nd question.
message has been deleted
s
I am baffled.
c
message has been deleted
s
One thing you can try is that remove the LocalDistributionAdvanced, DeployDistributionAdvanced and DeployDistributionAdvancedSS2 folders from your SC_22.1_Live folder and then try to deploy again. If that does not work try running the "npm install" command again in the terminal.
👍🏻 1