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.
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!
RESTlet issue
Hi,
We have created a RESTlet in suitescript 2.0 where we are pulling the values from existing saved searches by proving ID in RESTlet URL and then getting and sending the result in response. While doing so we are facing some blockers:
1. When the result set is huge: Since the RESTlet can only run for 5 mins we are facing Time out issues for large data set saved seraches. We have tried slicing the result set by applying "rownum" as filter but the problem comes when we are trying to sort the result by internal ID. Is there any other way we can break the result into small batches(For ex. 10000) and then in the result we can pass a parameter to identify till what point the search ran and start over from there in the request?
0