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.
NetSuite has launched SuiteSuccess Wholesale Distribution Edition, in Japan. Please join us the webinar on February 12 that introduces NetSuite solution with demos and case studies for Wholesale Industry.
Register Now
Have questions or experiences to share? Post your Release 2026.1 questions and join discussions in the Release 2026.1 category.
Intelligent Payment Automation, powered by BILL (formerly Bill.com), lets you automate payments, manage vendor details, and bank account information within NetSuite.
The SuiteApp is available to organizations based in the U.S. with a valid U.S. address, or to global customers (except Canada, China, and Japan) with U.S. business subsidiaries. It only supports payments to vendors operating in the United States.
For more information, visit this thread.
Incorrect results when using nlapiLoadSearch
I've observed something very strange when using nlapiLoadSearch, and then subsequently runSearch() and getResults(). The number of results returned via script do not match the number of results returned by the saved search in the UI. I'm running this in a sandbox environment, on a custom record. I have not tried this in any production environments, yet.
I have 90 records, and all 90 are correctly returned by the saved search in a standard list view.
Using nlapiSearchRecord() with no filters, also returns a result set of length 90.
However, using nlapiLoadSearch with runSearch() and getResults() gives me only 89 results.
This has been driving me nuts the whole weekend! Am I doing something wrong, or is this a bug? Has anyone else experienced this? Any ideas?