Week 2 of 8

What a release can break

Oracle tests NetSuite. It does not test your scripts, your workflows, the saved searches your integrations read, or the SuiteApps you installed. Those are yours, and in most accounts nobody has a complete list.

Oracle’s own Release Preview guidance suggests the start: export your script deployments to a spreadsheet and use it as a checklist. Then add everything else a business process relies on.

This week: build the inventory and rank it

Export Customization > Scripting > Script Deployments and your workflow list. Add saved searches and SuiteQL datasets used by integrations and reports, Advanced PDF/HTML templates and installed SuiteApps.
For each object, record the business workflows that rely on it, its owner, and whether it lives in an SDF project under version control.
Rate business risk and change frequency. High and high means it is tested every release and is first in line for automation.
Read the release notes for your modules and mark what is impacted. In 2026.2, for example, SuiteQL queries and datasets with no sort order now sort by transaction date.

Number of the week

test areas in Oracle’s suggested Release Preview test plan, from business workflows to SuiteAnalytics Connect.

Source: Oracle NetSuite Help Center, Suggested Test Plan

Use this week

NetSuite Customization Regression Inventory →
Object types, a calculated test priority, release impact and a result column per release.
Change Impact Analysis Log →
Turns release-note items and your own changes into test scope.

Next week: which NetSuite account to test in, and what each one is and is not good for.

Get the playbook in your inbox, one week at a time

Subscribe free and every template in the library is yours.