Hi all, Did anyone else notice this in the 2026.2 release preview (on the home page)? All SuiteScript versions lower than 2.1 are going to stop working "in an upcoming NetSuite release". I wonder how much time they'll give us. I manage a lot of SS1.0 scripts and script libraries I never got the chance to rewrite in SS2.x... 🫠 Update: NS Support say they have no deprecation date for SS 1.0, so clearly nothing about this is officially documented at the moment.

Where did you see this?

@eminero On the dashboard when logging into the 2026.2 RP.

Thanks!

Holy cow, that's.....wild.

I mean the heat death of the universe will also happen ... "in the future" I'm not worrying about it though

Hopefully the heat death of the universe comes before ss1.x is dropped. They still don't support email captures in 2.x 😞

They cannot completely turn off SS 1.0 scripts as even some of NetSuite scripts using SS 2.1 code calls the SS 1.0 libraries/API. Edit: referring to client script NS code.

We just had our sandbox upgrade last night and this is the message we have also.

its gotta be a bogus message. There's so much 1.0 and stuff out there

@Brad Hosking Basically, SuiteScript server-side scripts can be annotated with

@NApiVersion 2.x

which gives you the flexibility of running it as SuiteScript 2.0 or 2.1, based on account preference.

the x in 2.x means run at the latest suitescript available so if you have 2.x, you are just going to run whatever the latest and greatest is. You could most likely just change any 2.0 to 2.x and be fine for your scripts. Its the 1.0 that is going to be a huge pain in the ass. Good for consultants who are going to get paid to update the code (or your own internal team) but bad for pretty much any client that has working features in 1.0.

On the last SDN partner call, the presenters were inundated with questions about this. It turns out, they rolled this message out in 2026.1, then quickly decided against it before anyone saw it and disabled it -- but ONLY for 2026.1. They forgot to disable it for this release, which sparked a panic. Clearly, they have shown their hand, but they've also admitted that the world is not ready for this kind of chaos, so... look for this to return closer to the heat death of the universe.

All the developers out there must be over joyed! Job security for life!

If I'm honest, I was hoping this message rolled out with 2026.2, but alas, I'll have to find some other way to hit my utilization goals.

If that was true i'd just quit my job and start a business updating 1.0 scripts and retire in a few years

With how much NS is shoving AI into all the things I could see them trying to mass rewrite all SS1 logic in SS2.1+ automatically as a "convenience".

My price doubles if you did that

Probably should be higher. I can't imagine how wonderful that would be to pickup.

Have you seen the migration skills for SS1/SS2.0 -> 2.1 they already created? @Christopher Quackenbush' idea is not far from reality

Array indices starting at 1 is probably gonna blow AIs mind

I doubt it would @creece

Glad I searched here for answers. ..TBH I have hundreds of affected scripts 🫠🫠

If this is happening and they are going to depreciate 1, 2 and 2x, AI is going to get very busy in converting it all. Which if you think about means we spend more tokens which in theory could be a revenue stream…

they might actually mean that 2.1 part of the message. Suitescript 2.0 and 1.0 both run using the old rhino javascript engine. That warning message probably means they only plan on supporting the graaljs engine used by suitescript 2.1

Maybe.. just maybe they should call it 3.0 and we all know where we start at that point. No confusion that way.

Which is all great unless in your account you have locked scripts that you cannot see the contents of and the bundle it came from is not one you have access to and on top of that the partner that installed it is not around anymore. 🤨

Because of the above reasons, it is nearly impossible for NetSuite to completely disable/remove scripts written in any version than 2.1

i really feel like everyone in this thread seems to have missed this message... you can all chill out

On the last SDN partner call, the presenters were inundated with questions about this. It turns out, they rolled this message out in 2026.1, then quickly decided against it before anyone saw it and disabled it -- but ONLY for 2026.1. They forgot to disable it for this release, which sparked a panic.

Clearly, they have shown their hand, but they've also admitted that the world is not ready for this kind of chaos, so... look for this to return closer to the heat death of the universe.

Linkedin has been on fire with people coming out of the woodwork to help with this transition lol They really hopped on the fear bandwagon even though it was obviously a goof message.

Let's comment under each post to counter it 😄

A little fear may not be a bad thing 😄

I didn't miss it but whenever it happens what I said still stands 🤣