NetSuite SuiteScript 2.1 Requirement

Short answer: if you have seen a notice in your NetSuite account asking you to update scripts to SuiteScript 2.1, your Netgain products are already accounted for. Nothing is required from you to keep them running.

This article covers what the banner is, what Oracle is actually changing, and what is worth reviewing in your own account before the deadline.

What is the banner I am seeing in NetSuite?

NetSuite is displaying an account-level notice reading “Update Needed: Update Scripts to SuiteScript 2.1.” Oracle is retiring older versions of its scripting language and moving every account onto a single current version.

The notice appears across NetSuite accounts generally. It is not triggered by anything specific to your environment, and it is not a sign that something in your account is broken or at risk today.

View full size

Do I need to do anything about my Netgain products?

No. Netgain is tracking this requirement across our full product line and updating our scripts ahead of Oracle's deadline. No Netgain SuiteApp will stop working because of this change, and you will not be asked to do script work on anything we built.

Our products are built natively on the NetSuite platform, so we move with the platform as it changes. Keeping our SuiteApps current with Oracle's standards is part of what your subscription covers.

What exactly is Oracle changing, and when?

Oracle is phasing out SuiteScript 1.0, 2.0 and 2.x in favor of SuiteScript 2.1. The published timeline:

The deadline that matters is 2028.2. That will happen around September 2028.  No action is required in the current release to keep your account running.

Why am I seeing the banner if nothing on the Netgain side needs attention?

The notice is account-wide, and it does not identify which scripts it is flagging or who owns them. Most NetSuite accounts accumulate scripts from several sources over the years: customizations built in house, SuiteApps from more than one vendor, and integrations configured during past implementations. The banner treats all of them the same way.

What should I review in my own account?

This is worth doing at some point before 2028.2, at a pace that suits your team. Oracle documents three ways to build the inventory:

• Filter the scripts list. Go to Customization > Scripting > Scripts and use the API Version filter to show scripts running on versions other than 2.1.
• Build a saved search. Set the criteria to API Version is not 2.1, and include Name, ID, Script Type, API Version, Owner and Description as columns.
• Build a SuiteAnalytics workbook. Go to Analytics > Workbooks > New Workbook, select a dataset that includes script information, and filter out scripts using API version 2.1.

Any of the three gives your administrator a working list.

How do I tell which scripts came from Netgain and which came from somewhere else?

Start with the Owner field in the saved search above, which shows where each script originated. To confirm vendor ownership, cross-reference the Installed Bundles list at Customization > SuiteBundler > Search & Install Bundles > List. Clicking a bundle name opens the Bundle Details page, where the Components subtab shows the objects that bundle installed.

From there, the list sorts itself into three groups:

• Scripts from a Netgain bundle. Ours to update, and we are handling them.
• Scripts from another vendor's bundle. Reach out to that vendor, since their code is not something you can update yourself.
• Everything else. Your own customizations, which is where your team's effort is best spent.

Who do I contact with questions?

For anything Netgain related, start with our knowledge base at support.netgain.tech or open a support case. Your Netgain Account Manager can also help you confirm whether a particular script in your account belongs to one of our products.