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.
Don't miss out on our Question of the Week! You only have until tomorrow, September 11, 2025, 2PM ET to comment your answers and earn rewards! Click here for more details.
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!

Incorrect results when using nlapiLoadSearch

edited Dec 2, 2019 5:45PM in SuiteCloud / Customization 3 comments

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?

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!

Leaderboard

Community Whiz

Quarter 3 (Jul-Sep 2025)

This Week's Leaders

This Month's Leaders

All Time Leaders