NetSuite Changelog
SuiteScriptRelease NotesNew FeatureSuiteScriptScriptingBest Practices

Removal of Ext JS Library in NetSuite 2024.2 Release Notes

Removal of the Ext JS Library in NetSuite 2024.2 impacts custom scripts. Prepare for future changes ahead of 2025.1.

·2 min read·4 views·NetSuite 2024.2·From NetSuite Release Notes PDF

Starting in NetSuite 2024.2, NetSuite has initiated a phased removal of the unsupported Ext JS library, which will be fully removed in version 2025.1. This change affects any customizations that rely on the Ext JS API, potentially breaking existing implementations if adjustments are not made ahead of time. To aid developers in managing this transition, a banner message will appear on pages loading the unsupported library.

Key Changes

  • Announcement of Removal: Users should be aware that the Ext JS library will be entirely eliminated effective NetSuite 2025.1.
  • Implications for Custom Scripts: Any custom scripts depending on this library must be assessed. Developers need to either replace the usage of Ext JS with their own instance or remove this reliance altogether.
  • Notification Mechanism: The implementation of a banner notification serves to alert developers when pages load scripts that include the Ext JS library, thereby helping to identify necessary changes early.

Best Practices

  • Conduct an Audit: Review your current custom scripts for any instances where the Ext JS library is utilized. This will be vital for ensuring compliance with future versions.
  • Plan for Migration: If your customizations are impacted, develop a migration plan to switch to alternative libraries or frameworks that are supported.
  • Test Extensively: Once changes are made, thoroughly test all customized scripts to ensure everything functions correctly without the Ext JS library.

Who This Affects

  • Developers: Any developers creating or maintaining scripts that depend on the Ext JS library will need to prepare for significant changes.
  • Administrators: It is important for administrators to inform the development team about this removal and assist in any required code modifications.

Key Takeaways

  • Ext JS library will be removed in NetSuite 2025.1.
  • A notification banner will highlight any usage of Ext JS in accounts using version 2024.2.
  • Developers must replace or remove reliance on Ext JS to avoid disruptions.
  • Early planning and testing are advised to mitigate potential issues caused by this removal.

Frequently Asked Questions (4)

Does the removal of the Ext JS library apply to both SuiteScript and standard NetSuite environments?
Yes, the removal of the Ext JS library affects any customizations made in NetSuite, particularly those that rely on SuiteScript, regardless of the environment.
What permissions are required to assess custom scripts for reliance on the Ext JS library?
Developers will need permissions to access and modify custom scripts within NetSuite, typically requiring Administrator or Script Developer roles to conduct the necessary audits.
How will the notification banner function if I have scripts that load the Ext JS library?
The banner message will appear on pages that load scripts using the Ext JS library, serving as an alert for developers to identify and address any reliance on this library quickly.
Will existing workflows be affected if my custom scripts currently depend on Ext JS?
Yes, existing workflows may be disrupted if the reliance on Ext JS is not addressed before the full removal in version 2025.1, necessitating adjustments to custom scripts.
Source: Completely BilledmarkprojectascompletelybilledBilled completely — NetSuite Release Notes PDF. 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 →

Also from NetSuite 2024.2

View all NetSuite 2024.2 changes →