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.
Make Your Voice Heard: What Tech & ERP Topics Should We Explore in our Next Webinar?? We’re all ears! Vote now, and the poll runs until January. Poll for ERP | Poll for Tech.
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!
To help you get the most out of your 2025.1 Release Preview account, review the topics outlined in the Release Preview Guide.
NetSuite Release 2025.1 Release Notes are available for download here!
How do I call a scheduled script again in 2.0 where it was left out previously?
I'm encountering challenges with NetSuite Governance Unit limits in my scheduled script. To address this, my current strategy involves processing 50 records during each script execution. After processing a set of 50 records, I trigger the scheduled script again with an incremented range, such as 51 to 100, for the subsequent execution. This iterative process continues until all records are processed. I'm seeking suggestions on how to enhance this approach for better efficiency and to overcome NetSuite's governance limits. How can I optimize this solution, and are there any best practices I should consider scheduled script 2.0?
Tagged:
0