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 🤣

Hmm now when deploying I'm getting this in my log. Will they support ss2.1 in email capture before or after they officially drop support? This still shows 1.x as only being supported: docs.oracle.com/en/cloud/…/chapter_4235218166.html

1. ~/Objects/customscript_plugin_order_capture.xml (0 error(s), 1 warning(s))
  - WARNING: The project contains SuiteScript 1.0 script files. These scripts will stop working in an upcoming NetSuite release. To ensure compatibility, convert these scripts to SuiteScript 2.1 as soon as possible.

its just a warning? warning = it doesn't stop me deploying I don't care 😛

I asked the question in an all hands meeting thing a few weeks ago and I got a bunch of wide eyes and a suggestion to start migrating everything

I'm aware it's a warning currently. While it doesn't stop me today.. six months from now it could be a different result, and cause real problems.

if they ever truly start down this path i expect it to be over MULTIPLE release - they'll release a tool that shows you all your deployed scripts that are 1.0 and have notes all over the release notes then they'll say in the next release we're targeting DATE, and nothing else then as we approach that DATE, they'll see actually we're thinking it will be DATE2 now then as we approach DATE2 they'll say we've heard youre feedback and are putting this on old till everyone is comfortable, watch this space, we'll be providing tools to help the migration path then another release will hit and they'll have some AI tool to rewrite your 1.0 scripts to 2.1 ...and THEN you'll say - hey but what about email capture? and then everything will go on pause again

You have a better chance getting struck by lightning then them actually doing this IMO

Well.. the upgrade message was cryptic.. Suiteworld 2026 session catalogue has this doozy and another session on CI/CD

Someone just reported that they saw a message today in an account referencing the deprecation of SuiteScript 1.0 and 2.0 and 2.X which will no longer work in 2028.2

I'm seeing it in SB too, here's the link it includes now: suiteanswers.custhelp.com/app/answers/…/1047412

@Michelle Beutler Thanks. So it seems to be official then. We'll have our work cut out for us...

There has been an ongoing discussion elsewhere about this. The general consensus was that It's not happening anytime soon. The message has been seen in other forms (message bar), and it was stated it was never supposed to have been shown, I suspect the same applies to this.

We shall learn more at Suiteworld I am guessing

I've started seeing this in production accounts. Based on a quick audit I did in one client's account, it appears as if NetSuite might have a lot of work to do in this regard. Hopefully, they will soon be accelerating their own migrations:

I have a feeling that will sort of happen along the lines of "You now have AI for all your SuiteScript migrations!" and "It will cost you thiiiiiiiisssss much" GitHub Copilot models actually works not too bad with the migration FYI if you have that and VSCode. I need to sit down and work out 1. Whats in use 2. What needs to be disabled If only there was a native CI/CD solution that would make this whole process sooooo much easier

what about email capture plugins? they don't supports SS2.1...do we just loose our email capture plugins?

I only had about 10 scripts that were not already at 2.1 and had them converted with Claude in about half hour without touching anything

@NElliott Oracle is sending out emails about it now. Seems like this has gone beyond a banner that they forgot to remove. 🙂

Why are they removing the 2.x annotation? I thought that was going to be an account level setting to control the version. Why not just bump it to a 2.1 minimum for 2.x?

cos it reads as ambiguous and it'd actually be enforced 2.1 elsewhere anyway so its wrong - also just kicking the can cos in the future when they want to enforce everything is 2.2 then 2.x won't be ok

It's really easy to create an NS-centric agent in Copilot. When you define it you direct it to this url: github.com/oracle/netsuite-suitecloud-sdk/…/agent-skills And it's awareness is pretty good for everyday tasks

What about custom plug-ins. At the moment they only support 1.0 or 2.0 🤔