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.
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Keep an eye out for upcoming NetSuite events, including meetups, workshops, and webinars. These sessions are a great way to connect with peers, learn from experts, and stay current on the latest NetSuite updates and best practices. Registration links are provided in each event.
Client script debugging tip (2.0)
In 1.0 client scripts we were able to open the developer console, find client scripts and insert debugging points. In 2.0 we can't find the scripts that way which can make production debugging hard.
I've found two ways to address this so far...
1. Netsuite suggested adding a "debugger;" line to the script. If the console is open it will start the debugger when it hits this line.
2. If you add a console.log message in your script, the message in the console will include a link to the source code that can be used to add breakpoints. I've just been adding a console.log("{name of file}"); to the pageInit event. Then I've got access to the entire script if I need it.
0