SuiteScript developers
Migrate your own SuiteScript 1.0 scripts to 2.1.
Check ownership, propose an upgrade, review it in Code and Git, then work through sandbox tests before you confirm an SDF release. Vendor-managed updates stay with the publisher.
What you need
Code and Git are in beta and require Developer mode with an authorized NetSuite role. Runner execution requires the optional NetSuite bundle, a sandbox or Release Preview account, and confirmation. SDF deployment needs configured SuiteCloud credentials. The upgrade prompt alone does not deploy code.
What you get
- Confirmed script scope, vendor exclusions, and ownership questions
- Proposed SuiteScript 2.1 changes and a reviewable Git diff
- Sandbox checks, recorded results, and unresolved issues
- An SDF release with explicit target confirmation
How it works
Confirm which scripts are yours
Review versions, bundle membership, and dependencies. Exclude vendor-managed scripts and flag uncertain ownership for a person to confirm.
Propose and inspect the upgrade
Use the SuiteScript upgrade workflow for a selected script. Review the proposed 2.1 code in Code, then inspect the Git diff and API changes before testing.
Test against agreed behavior
Plan sandbox test transactions and expected outcomes. With the optional Runner and write controls configured, validate behavior, review logs, and iterate. Test records may persist; keep the results for review.
Approve the exact release
Use Git and SDF to review and validate the release. Confirm the destination account and approve deployment with the required credentials and write permissions.
Example workflow — adapt the scope and checks to your account.
Here’s how a migration can work.
Start by finding the scripts you own. Follow the changes through testing to the deployment you approve.
These sample results illustrate the steps. They aren’t a completed migration or verified tests; your account needs its own checks.
Check versions, bundle ownership, and dependencies. Choose the custom scripts to upgrade and leave vendor-managed updates with the publisher.
Real product views. Example account data.
Illustrative workflow
Example: choosing what to upgrade
- Custom SuiteScript 1.0 script — check who maintains it
- Vendor-managed bundle script — leave its update with the publisher
- Related workflows and dependencies — check before upgrading
Let netQuery.ai update the selected scripts to 2.1. Review the code and Git diff before you test.
Real product views. Example account data.
Illustrative workflow
Example: reviewing the changes
- Selected custom script — proposed 2.1 changes
- Git diff — ready for you to review
- API changes and dependencies — still to check
Have netQuery.ai create sandbox test transactions, check logs, and refine the code until your agreed checks pass. Keep the results for the release review.
Real product views. Example account data.
Illustrative workflow
Example: checking the results
- Sandbox test transactions — to prepare
- Expected behavior and logs — to check
- Agreed tests — results pending
Review the test results and exact destination account. SDF deployment needs configured credentials, the required write permissions, and your confirmation.
Real product views. Example account data.
Illustrative workflow
Example: getting ready to deploy
- Test results — awaiting your review
- Production account — confirm the destination
- SDF deployment — waiting for your approval
Step 1 of 4