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.
SuiteWorld | October 25–28, 2026 | Las Vegas Where our community gets ready for what’s next!
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Join us
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Join us
Benchmarking: Search Operations
I ran some benchmark tests with the search operations using the NetSuite webservice and I found that performing several small requests is actually FASTER than one large request.
For instance, I was performing a SEARCH for any inventory item inside NetSuite. This results in a total of 653 records (for our particular company). If I performed the initial SEARCH for 100 records, and then used the SEARCHNEXT function for the additional records, it was actually FASTER than simply performing a SEARCH for all 653 records.
If anyone else has done any time-tests for these functions, feel free to contribute feedback.
0