My colleague can deploy and activate extensions wi...
# suitecommerce
d
My colleague can deploy and activate extensions without issue. If I deploy, the files appear in the file cabinet, the extension shows in SC ExtMech Extension List, but the extension doesn't appear in the list for a new activation. Can anyone give any pointers where to start looking?
s
Are the values you set for the target version and applications supported by the site you want to activate it on?
Copy code
"target": "SCA,SCS",
"target_version": {
    "SCA": ">=20.2.0",
    "SCS": ">=20.2.0"
}
d
Definitely all correct.
I've tried with a newly created/bare extension and still the same
s
And just to confirm that these values actually represent you site, ie your site is running 20.2.0+? Furthermore, these values are the ones present in the manifest file as it is stored in NetSuite?
d
The site's 20.2.0 and the manifest is correct on the server
I think it's a permissions issue to do with the SC ExtMech Extension records. My colleague can create one manually and it appears in activations but it doesn't when I do the same.
s
Perhaps. Does your user have the SCDeployer role?
d
Yes
s
OK, I don't really know what to say. I think you may need to raise a case with support
d
Found the issue now. It was to do with versioning
I think it probably arose in the initial deploy. The fact we can't do _gulp extension:deploy --advanced (_as mentioned by @Viraj Shinde last week) doesn't help in that respect. Is this something which Netsuite are aware of?
s
I'm not sure what you're referring to. What exactly was the issue and how did you fix it?
d
I suspect when I first deployed, I did version 20.2.0, rather than >=20.2.0
Presumably the custom record gets created from this and doesn't update if you then redeploy with the same extension version
s
I don't think it gets updated unless you increment the version number of the extension
d
gulp extension:deploy --advanced is supposed to force re-entry of the deployment info, but doesn't seem to work with the latest tools
e
probably --advanced flag existed in the src developer tools but I have not seen that flag for extension dev tools 👀
s
I can look into it. As Emerson says, I'm not familiar with that flag existing on the developer tools
d
Thanks Steve. It's documented in help if you search "Gulp Command Reference for Themes and Extensions"
s
OK I have tested it and I'm able to replicate it. I've created issue 618055 for it. If you want to help get it prioritised, please raise a case describing your issue and ask for it to be associated with that issue.
👍 2