This notice is intended for customers that have a SuiteScript file(s) that was previously identified as non-compliant with the upcoming change to the stack property of Error instances and the .toString() method on functions in hidden files.
What is Changing?
The stack property of Error instances and the .toString() method associated with hidden files will be changing, starting June 2025. The stack property of an Error instance will no longer show the trace of a function if it is a part of a hidden file. Usage of functionName.toString() where functionName is part of a hidden file will result in an error. Files are considered hidden if any of the following is true:
- The file record in the File Cabinet has the Hide in SuiteBundle preference enabled.
- Your SuiteApp has a hiding.xml file in the InstallationPreferences folder with the “HIDING” defaultAction set to “HIDE.”
- Your SuiteApp has attribute files under FileCabinet > SuiteApps > com.netsuite.project > .attributes where the hideinbundle field is set to ‘T’.
Required Actions
As a reminder, you must remove any business logic that relies on functionName being returned in the stack of Error instances, and remove usages of functionName.toString() if functionName is in a hidden file, to prevent script functionality from breaking in target accounts. Once you have made changes to affected files and confirmed that your projects are operating as expected, push upgrades to your managed bundles and SuiteApps. If you have un-managed bundles or SuiteApps, please instruct your customers to upgrade to the latest version as soon as possible. The change will take place June 2025.
If you have questions, please contact NetSuite Customer Support.