Hey all, this is a very random question, but... do...
# suitescript
m
Hey all, this is a very random question, but... do you think Netsuite has any plans of completely deprecating SuiteScript 1? I know 'no new features will be published for it', but I'm more concerned about it being removed altogether. I still write most of my scripts in it, so I thought I'd ask. I do see they have deprecated some other features, but there is usually still compatibility for old stuff (thinking old templates versus Advanced Templates). But I'm not sure if that will be the case for SuiteScript 1 or not.
r
As far as I am aware no, as a lot of modules are built on it on organizations worldwide. But on a bigger note, why do you not upskill yourself and start coding in 2.1? ES6 functionality will unlock for you, you can do so much more with it? Plus eventually if you decide to move from 1.0 to 2.0 you will have a bigger tech debt to move from.
a
I imagine they'd be a huge outcry if they killed it off, so I can't see that happening, unless they're working on some tool to auto-migrate SS1 code to SS2 code ๐Ÿค” ... yeah they won't do that. but I agree with raghav, its time to move on SS 2.x offers so much more. lots of new modules that simply don't exist in SS 1.0, map reduce scripts, and ES6 syntax sugar
m
@raghav Cool, thanks! And yeah, I've been doing so, and it's pretty nice (at least, nicer than I first thought looking into it - I originally thought it looked a lot messier). Main thing is... if I need to eventually migrate things... I'd rather start now rather than have to do things within a 6 month period... (I have a ton of scripts)
@Anthony OConnor Yeah, I hope you are right there ๐Ÿ™‚. I'm going to need to explore more ES6... still writing the modules in ES5 pretty much since I'm so used to it ๐Ÿ˜›.
a
first step would be stop making NEW script in 1.0... all new dev has to be in 2.x once you're more familiar with it the migration path won't seem so painful
m
@Anthony OConnor True that ๐Ÿ™‚
m
From @erictgrubaugh (https://stoic.software/wp-content/uploads/2020/08/client-map-application-assessment.pdf)
I have been informed by one member of the SuiteScript team that: โ€œWithin the next few releases, although not within one year, we will be disallowing creation of new 1.0 scriptsโ€.
If the above information is accurate, you can expect that before NetSuite version 2019.1, you will need to be writing all of your new scripts in SuiteScript 2.0. Because 1.0 and 2.0 cannot be intermingled in the same script, you may be limited on what you can accomplish or add to your existing 1.0 script. You will not be able to take advantage of the latest features of SuiteScript, and you will be missing out on any continued performance or security improvements that NetSuite makes with SuiteScript 2.0.
I consider delaying a transition to 2.0 extremely risky for any SuiteScript application. Your maintenance efforts will grow exponentially as 1.0 fades into obscurity. You will effectively need to maintain two distinct code bases, and very soon developers who come in to the NetSuite market won't even learn 1.0; thus, there will be even less available talent to help you maintain and improve your applications
a
ok... but that was 4 years ago, and they haven't done it yet?
ablobshrug 1
m
@michoel Wow, that is quite a notice... I guess I might just need to ask them on their forums what their roadmap is on this. If they are going to prevent you from editing previously created scripts... I might just need to start migrating things on the sooner side... we oftentimes have to go back and change scripts we've already written. @Anthony OConnor It does look like it was 4 years ago... perhaps they've changed their mind? I'll ask them about it.
e
^^ Yeah, even as the author of that post, given they haven't moved on it in 4 years, I don't anticipate they'll ever actually turn it off.
And I agree with everyone else, migrate asap ๐Ÿ™‚
m
Thanks @erictgrubaugh, yeah, I'm going to try and do that ๐Ÿ™‚. I think I can do pretty much everything I need to in it, as long as I have dayjs included (I use nlapiAddDays() way too much).
Hey @erictgrubaugh @michoel @Anthony OConnor Just a heads up, I asked them, and they said they had no plans nor timeline to remove 1.0, so I think you are all correct that they don't ever plan to turn things off (at least in the short term). Link here: https://community.oracle.com/netsuite/english/discussion/4483121/does-netsuite-have-any-plans-for-deprecating-suitescript-1-0
๐Ÿ‘ 2
a
dont let this make you NOT migrate dude ๐Ÿ™‚
this 1
m
@Anthony OConnor Definitely. It just gives me a bit more leeway with my timetable for (maybe) slowly moving some already written scripts over. But there's about 200 of them... so it might take a while.
๐Ÿ‘ 1
@Anthony OConnor So I think I might have found something that will definitely keep me on Suitescript 2.1... it seems that multiline template literals work... which is a huge convenience and timesaver! ๐Ÿ˜„
a
oh you mean with backticks?
yeah that's pretty neat, you can also use ${var} in the middle of them without having to use "text" + var + "moretext"
m
@Anthony OConnor Yep, that's precisely what I meant. Way better than stringing out multiple lines with + between variables. ๐Ÿ™‚ Anyways, hope you are having a good day.
z
My question is little bit different : when NetSuite will provide ALL feature available for Suitescript 2.x. CustomGL plugin only SS1. 0 Email capture plugin only SS1.0
r
Everything has it pros and cons. Email.send 10 recipient limit. nlApiSendEmail no limit that I am aware of.
z
My mistake, I forgot to add Email capture plugin
Bank statement parser (ok deprecated) only SS1.0
a
pretty sure nlapiSendEmail has 10 recipient limit too
not to mention about 12 freaking params
r
We are using nlapiSendEmail for sending emails to people over 10 recipients. Will confirm after checking once. But I am pretty sure with one more parameter added you could.
a
this if from memory and it was long time ago , but i think you're allowed 10 recipients, 10 CC and 10 BCC... and you can subvert that if you can use contact groups... there's also a way to send campaign emails or something, which absolutely DOES NOT have that limitation, not sure if that's available with nalpiSendEmail though