SuiteScript developers
Migrate your own SuiteScript 1.0 scripts to 2.1.
Assess ownership, review code changes in Git, validate with sandbox transactions, and confirm an SDF release. Vendor-managed upgrades stay with the publisher.
Real product views. Example account data.
What you need
Code and Git are in beta. Enable Developer mode with an authorized NetSuite role. You need a sandbox for testing; SDF deployment requires configured SuiteCloud credentials, write permissions, and confirmation.
What to review
- Confirmed custom-script scope and vendor exclusions
- SuiteScript 2.1 changes with a reviewable Git diff
- Sandbox validation records and remaining issues
- SDF release review and target confirmation
How the workflow unfolds
Agree the migration scope
Ask netQuery.ai to review versions, ownership, bundle membership, and dependencies. Confirm which custom scripts belong in the migration.
Upgrade and review
Convert the selected scripts to 2.1 and inspect the Git diff. Review API changes and dependencies before testing.
Test, fix, and retest
Create sandbox test transactions, inspect behavior and execution logs, and iterate until the agreed checks pass. Retain the validation results for review.
Confirm the release
Review the validation results and exact production account, then confirm the SDF deployment with the required write permissions enabled.
Example workflow — adapt the scope and checks to your account.
Follow a SuiteScript migration.
Explore the decisions and review points from ownership assessment to an SDF deployment confirmation.
These are illustrative outputs, not a completed migration or verified test results. The scope and checks depend on your account.
Review script versions, bundle membership, and dependencies. Confirm your custom scripts before selecting the migration scope.
Real product views. Example account data.
Illustrative workflow
Example scope review
- Custom SuiteScript 1.0 script — candidate; ownership to confirm
- Vendor-managed bundle script — excluded; publisher-led update
- Linked workflows and dependencies — review required
Upgrade selected scripts to SuiteScript 2.1, then inspect the code and Git diff before moving on to sandbox validation.
Real product views. Example account data.
Illustrative workflow
Example review queue
- Selected custom script — proposed 2.1 changes
- Git diff — ready for developer review
- API changes and dependencies — checks pending
Create test transactions, inspect execution logs, and revise the code against agreed checks. Review the evidence before release.
Real product views. Example account data.
Illustrative workflow
Example validation checklist
- Sandbox test transactions — to prepare
- Expected behavior and execution logs — to review
- Agreed validation checks — results pending
Review validation results and the exact target account. SDF deployment requires configured credentials, the required write permissions, and confirmation.
Real product views. Example account data.
Illustrative workflow
Example release review
- Validation evidence — approval pending
- Production target account — confirmation required
- SDF deployment — awaiting confirmation
Step 1 of 4