Week 4 of 8
The Release Preview window
Release Preview is a temporary account on the new version, built from a copy of your production (or sandbox) data. Oracle is clear about its purpose: test your existing business workflows. You are not expected to test the new features.
Two rules catch small teams out. It ends on your production upgrade date. And with no login for 14 consecutive days, Oracle purges it.
This week: request it, set it up and protect it
- Have an Administrator request it from Setup > Company > Release Preview. Request it from a sandbox if you want that sandbox’s data and customizations.
- On day one, redo what is not copied: integration tokens, SAML, web store domains and payment processing credentials. Activate the saved searches you need; they arrive inactive.
- Grant testers access with their own roles. At first only Administrators can get in.
- Put a login rota in the calendar so nobody lets the account lapse past 14 days.
- Install managed SuiteApp upgrades by hand where the vendor has one ready. They are not pushed to Release Preview.
Number of the week
14 days
without a login, and Oracle purges your Release Preview account.
Source: Oracle NetSuite Help Center, Overview of Release PreviewUse this week
- NetSuite Release Preview Test Plan →
A 15-item setup checklist, business workflow tests and a purge-date countdown.
- Guide: testing NetSuite upgrades in the Release Preview window →
What behaves differently in Release Preview, and what to do about it.
Next week: testing as Administrator hides every permission defect. We test with real roles.
Get the playbook in your inbox, one week at a time
Subscribe free and every template in the library is yours.