Discussions
Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
Update your Profile with your Support type to get your Support Type badge.
Expand your NetSuite knowledge by joining our Ask A Guru Live sessions. RSVP on this event now.
Don't miss out on our Question of the Week! You only have until tomorrow, September 11, 2025, 2PM ET to comment your answers and earn rewards! Click here for more details.
Uncover the power of data with the Analytics Hub —your ultimate guide to mastering NetSuite Saved Searches and Reports. Simplify the complex and unlock your organization's true potential. Dive into the Analytics Hub now and soar to new heights!
NetSuite 2025.2 Release Notes - This document summarizes the changes to NetSuite between 2025.2 and the previous release.
To help you get the most out of your 2025.2 Release Preview account, review the topics outlined in the 2025.2 Release Preview Guide.
SuiteWorld October 6 - 9, 2025: Agenda Builder is live!
Read on for the latest updates including:
• Agenda Builder launch
• SuiteWorld On Air registration
• New NetSuite Prompt Studio Contest
• And more!
Check out this thread to learn more!
Read on for the latest updates including:
• Agenda Builder launch
• SuiteWorld On Air registration
• New NetSuite Prompt Studio Contest
• And more!
Check out this thread to learn more!
Scriptable cart, global client scripts, and the 'N/ui module
I am attempting to enable scriptable cart in an account that has a global suitescript 2.0 client script and running into an issue. The N/ui module is not defined when the script runs in the context of the webstore.
I have come up with the following work-arounds:
1. Switch to form level client script and use a different custom form for orders originating from the web store - bad for maintenance effort
2. Reference all modules with define(['N'], function(nModule) { /* code goes here */ }); - bad for performance
3. Undeploy the script from certain roles - potentially the best option
Any other ideas?
0