Discussions
Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Explore new breakthroughs, sharpen your skills, and connect with experts who are shaping what’s next. Experience bold keynotes, interactive learning, and connections that span the global NetSuite community. Discover what's next at SuiteConnect Tour 2026.
We’re excited to announce that the 2025 Community Recap is now available! This special recap highlights the amazing contributions and achievements of our members over the year and celebrates the collective success of our community.
Check your personalized recap to see the impact you made in 2025 and how your efforts helped shape our community’s growth and success.
View Your 2025 Community Recap
Thank you to everyone for your passion, collaboration, and support. Here’s to building an even stronger community together in the year ahead!
Season’s greetings to you and yours! As we head into the holidays (December 24 – January 4), we want to take a moment to celebrate the incredible strength and collaboration within our community. Even during the break, you can continue to benefit from connecting with peers, searching related threads, posting your questions, and marking helpful replies as “Accepted” in the Support Community.
Please note our dedicated team will be on reduced coverage during this time, and regular responsiveness will resume on January 5. Wishing you a joyful and restful holiday season!
-The NetSuite Support Community Team
Scheduled server-side script failing
I set up a scheduled script to run at midnight every day to find all cases that have a status still identified as 'New' and a custom field 'custevent_respondbyhrs' greater than 0 (respondbyhrs contains the number of raw hours to first response (taking into consideration business hours response versus 24x7 response, holidays, etc)
The function csiWriteToErrorLog simply writes out the error to the execution log using the 'ERROR' classifier which includes the line number of the error for debug purposes. Interestingly this ends up writing out to the execution log as 'DEBUG' which not sure why (could be my function, but I don't see a problem with it). The function _FunctionResults simply writes out to the execution log using the 'AUDIT' classifier that the function finished and shows an error count if errors occurred.