Migration Status Updates for SuiteScript 2.0 Modules

The Migration Status reports changes and updates on SuiteScript 2.0. Check for migrated modules and their enhancements.

·2 min read·View Oracle Docs

TL;DR

The Migration Status section provides updates regarding the migration to SuiteScript 2.0, detailing which modules have been transitioned and enhancements made in each release.

Overview of Migration Status

The transition to SuiteScript 2.0 is an important part of enhancing the developer experience within NetSuite. This section outlines the current state of this migration, the modules that have migrated, and updates on related changes.

Migration Updates (by Release)

Below is a summary of migration changes organized by release version:

ReleaseDescription of ChangesModules Migrated to SS 2.0New Modules
2020.1- Continued Module Migration to Unified Developer Experience
  • Continued implementation of My Account backend components (Service Controllers)
  • Updated some modules for SuiteScript 2.0 migration to TypeScript | StoreItem, Transaction, TransactionHistory | None | | 2019.2 | - Partial Module Migration to Unified Developer Experience
  • Initial implementation of My Account backend components (Service Controllers)
  • Updated some modules for SuiteScript 2.0 migration to TypeScript
  • Expanded SSP Application support for SuiteScript 2.0 affecting all Commerce web store SuiteApp installation and setup procedures. | Case, Subscriptions (Limited Release) | None | | 2019.1 | Added SSP Application support for SuiteScript 2.0 for implementations utilizing the SuiteTax feature. | None | None |

Note: Modules that have been migrated to SuiteScript 2.0 can be found in the Backend directory of the SCA source code: <SC_xxx/Backend/SC/ (where xxx represents the release). If your implementation contains customizations to these modules, you will need to review changes to maintain functionality. Keep in mind that importing or including migrated modules in your customizations may lead to runtime errors.

Relevant Next Steps

For those installing or managing SuiteCommerce applications:

  1. Go to Customization > SuiteBundler > Search & Install Bundles.
  2. Search using the Bundle ID of the appropriate SuiteApp, ensuring you're up to date with the latest versions required for a successful implementation.

Source: This article is based on Oracle's official NetSuite documentation.

Key Takeaways

  • The document lists modules transitioned to SuiteScript 2.0 by version.
  • Updates include improvements for developers using SuiteCommerce applications.
  • Understanding the migration impacts can help avoid runtime errors in custom implementations.

Frequently Asked Questions (4)

What modules were migrated to SuiteScript 2.0 in the 2020.1 release?
In the 2020.1 release, the StoreItem, Transaction, and TransactionHistory modules were migrated to SuiteScript 2.0.
Are there any new modules introduced in the 2019.2 or 2020.1 releases?
No new modules were introduced in either the 2019.2 or 2020.1 releases according to the migration status updates.
Do migrations to SuiteScript 2.0 affect customizations in SuiteCommerce applications?
Yes, if your implementation includes customizations to migrated modules, you will need to review changes to maintain functionality and avoid potential runtime errors.
What should developers consider when using modules migrated to SuiteScript 2.0 in their customizations?
Developers should be cautious of importing or including migrated modules as it may lead to runtime errors in custom implementations and should ensure they review changes in the Backend directory of the SCA source code.
Source: Migration Status Oracle NetSuite Help Center. This article was generated from official Oracle documentation and enriched with additional context and best practices.

Was this article helpful?

More in SuiteScript

View all SuiteScript articles →