This topic contains 2 replies, has 0 voices, and was last updated by darrenhillconsulting 8 years ago.
-
AuthorPosts
-
November 7, 2016 at 2:57 pm #1572
MChammaTXIn the documentation I noticed that in the JS doc entry tags you can put either 2.0 or 2.x for the API version. Does anyone know how future version upgrades are planned and what impacts this will have?
For example if I put 2.x will my code be compatible with 2.1, 2.2, 2.3 but would break if I had put in 2.0 instead? Can someone from NetSuite comment on what is planned for future SuiteScript versions?
Should we expect SuiteScript 3.0 to come much sooner than it took to go from 1.0 to 2.0?
This is a cached copy. Click here to see the original post. -
November 7, 2016 at 10:00 pm #1573
erictgrubaughAlso throwing in my request for more information here.
I do not know how the roadmap or future versions will be handled. My assumption is that “2.0” and “2.x” are essentially equivalent. I use “2.x” in all my templates.
The only detail that comes from the Help docs is:
For SuiteScript 2.0 custom modules that are not entry point scripts, this tag is an optional declaration. It can serve as a defense against future incompatible versions of SuiteScript (versions 3.x and higher) attempting to load it.
-
November 8, 2016 at 8:17 am #1574
darrenhillconsultingMy guess is the Netsuite plans to deliver support for legacy SS2.0 versions. Meaning, if you ‘tag’ your script with 2.0, Netsuite will execute that code against its 2.0 engine, even if it has already launched 2.3, 2.4, 3.0, etc. In the past (SS1), it was difficult to update (or fix) functions/features as it would require anyone that ever used those functions/features to update their code … if not impossible. Now, they can release new versions and protect customers from having their old 2.0 code from breaking.
I’m only assuming this, as its not been mentioned/documented anywhere.
Makes sense?
For the record, I always use 2.x (I always want to be using the latest and greatest .. so I’m assuming that when 2.1 is released, all my scripts will take advantage of that. If something breaks, I’ll fix it [and gain knowledge of the fix/improvement])
Hey @MChammaTX! Hope you are well my friend!
MChammaTX replied on 11/08/2016, 10:19 AM: You too Darren. Thanks for the help.
-
AuthorPosts
You must be logged in to reply to this topic.