Discussions
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?