is suitescript 2.1 now supported for services?
# suitecommerce
t
is suitescript 2.1 now supported for services?
s
No
g
Hi Steve, is there any plan to support SuiteScript 2.1 in SCA services soon?
s
OK, I asked a developer and he said that actually 2.1 should be supported in SCA / extensions
I am now confused because I was always told it wasn't 😅
Does someone want to try it out and see
c
I tried a week ago and it wasn't.
s
What happened? And did you change your SS 2.x execution to 2.1?
c
I specifically put 2.1 in the script file header and couldn't save. When I changed back to 2.x it worked.
g
I just tried and got
Failed to validate script file: Invalid SuiteScript Runtime Version.
s
🙃
Then I think the dev I talked to was misinformed
Because this stuff matches my expectations
FTR calling a 2.1 Suitelet in a Backbone model should work fine 🙂
👌 1
g
Yeah, I’ve been doing that. But going back to the first question, can we expect support for SuiteScript 2.1 in SCA services anytime soon?
s
It's not on the roadmap, no
👌 1
r
Aren't SCA services for some modules like Case already in 2.x?
Copy code
/**
* @NApiVersion 2.x
* @NModuleScope Public
*/
define(["require", "exports", "../_suitescript/SC/Case/Case.Fields.ServiceController"], function (require, exports, ServiceController) {
    "use strict";
    return { service: function (ctx) { return ServiceController.service(ctx); } };
});
s
2.x !== 2.1
2.x tells NetSuite to execute the script per the global preference setting, which, by default, should be 2.0
r
I see...
s
In your scripts, you explicitly define the version or leave it ambiguous
r
cause usually when I write explicitly 2.0, some of latest ECMA methods does not work but when I switch to 2.x it does, that's why I assume the engine somehow updates the ss version other than 2.0