This site was built to compliment the existing NetSuite Professionals Slack Community by adding a means for members to easily find answers to common questions and to create a searchable database of those questions and answers.

NetSuite Professionals

Hey I have a bunch of scripts that used to have
```/**
 * @NApiVersion 2.x
 * @NScriptType Suitelet
 */```
that I updated to say
```/**
 * @NApiVersion 2.1
 * @NScriptType Suitelet
 */```
but somehow some of the script records inside Netsuite still say 2.0 after the new files got deployed. Any ideas what else I need todo to ensure that all script records also update to 2.1?

I had gotten this before also
seemed something was cached when deploying via SDF
I think I had to change/update the script file contents within NetSuite's inline file editor was what resolved it

Yeah I just found that out too. When re-saving the file inside netsuite I got the error about that. But sdf didn't complain. Kinda annoying

<@UFUCXSXCJ> or someone else from the QA team any idea what can be done here? Changing 20+ scripts is not really a good solution for all of our developers to have todo

Its the deployments.  Currently you need to re-create the deployments to see the SuiteScript version change

I update files to SS2.1 quite a lot when wanting to use new functionality and I update and just upload the file to account through webstorm and never have have issue the script suitescript version just changes to 2.1 instantly. 

Wait what <@U5TNEF7FW>.  All you do is update the JSDoc in the .js file from 2.x to 2.1 , and the script records in NetSuite update themselves?

When using upload file to account or deploy. Have to make sure connected custom modules are 2.1 as well but as long as the file already exists in the file cab and the script is already created don't have any issues at all.

you can however call a 2.0 custom module from a 2.1 script but you cannot call a 2.1 custom module from a 2.0 script

yes, I do agree all of this "should" happen automatically; I have just had some intermittent issues with it in the past.
I didn't notice any certain pattern though, just seems some issue on NS side caching some aspect