Hello, we had some existing SS2.0 scripts that def...
# sdfn
Nicholas Penree
12/07/2021, 6:13 PMHello, we had some existing SS2.0 scripts that defined @NApiVersion as 2.x. We've since updated the @NApiVersion to 2.1 and re-deployed the script. When we view the script record, it still shows 2.0. If we edit the script file and save it within NetSuite it automatically updates to 2.1, with no modifications to the script file.
Is this a bug or known issue?
b
battk
12/07/2021, 6:30 PMnetsuite has traditionally had caching problems related to its scripts
battk
12/07/2021, 6:30 PMjoin the years worth of support cases
battk
12/07/2021, 6:32 PMyours may be a slightly different problem if the code running in netsuite is the new file, but the script record is not updated
n
Nicholas Penree
12/07/2021, 6:46 PMThe code running in NetSuite is the new code and it uses 2.1 language features so it fails when it runs since the script record still says 2.0. I've replicated this on multiple 2.x scripts deployed via SDF
b
battk
12/07/2021, 6:48 PMstill support case
n
Nicholas Penree
12/07/2021, 6:48 PMOk thanks
b
battk
12/07/2021, 6:49 PMnetsuite has always had problems updating scripts from their webservices
battk
12/07/2021, 6:49 PMit works as expected from the ui
d
dbarnett
12/07/2021, 8:09 PM@Nicholas Penree if you scroll up a bit on this channel ~5days ago I had the same issue/resolution - seems like is still a caching bug going on in NS
Edit: except in my case, the script files were locked via our deployment, so I just made some trivial change in all the entry point files and re-deployed to get them to update to 2.1
n
Nicholas Penree
12/07/2021, 8:10 PMthanks @dbarnett
d
darrenhillconsulting
12/08/2021, 2:18 PMWait. Not sure this is caching. If you previously deployed those scripts a 2.x .. then redeploy them a 2.1 .. the original script records (not files) will remain 2.0. So, you need to deleted the original scripts records (not file) and redeploy to get them to be 2.1
d
dbarnett
12/08/2021, 3:18 PM@darrenhillconsulting I disagree with this assessment (or at least I do not think this is the expected/desired behavior)
nothing about the script record from an SDF XML standpoint specifies the API version right, it is just in the NApiVersion tag in script contents itself
aside from that, other than the "caching" issue, I have observed the script record does update to 2.1 when originally 2.0 via change of NApiVersion and re-deploy
dbarnett
12/08/2021, 3:22 PM(however I am not saying your solution wouldn't work, just that it is not desirable or from my experience needed)
primarily from the standpoint it would delete any existing Script Parameters set by the user which would definitely mess things up at least in my case
n
Nicholas Penree
12/08/2021, 3:24 PMdefinitely not desirable to have to delete the entire script record to change the version. I agree with @dbarnett that the version is controlled in the script file so not sure why it would require deletion. if edited and saved within the UI it correctly updates the 2.1 on the script record.
Seems like a netsuite bug via web services at battk suggests
d
dbarnett
12/09/2021, 1:11 PM@Ali Syed (NS DevTools QA) can you comment on any of the above - what is the expected behavior, and is this something on NetSuite's radar that they are working towards resolving?
a
Ali Syed (NS DevTools QA)
12/09/2021, 2:57 PMHello, I am not sure about this as this is a completely different team who is responsible for this. Please raise your question with NS support and they will verify it for you with relevant team.
👍 1