So I have a Saved Search that runs fine directly in NetSuite, but fails when loaded and run from SuiteScript 2.0...
{ "error": { "type": "error.SuiteScriptError", "name": "SSS_INVALID_SRCH_OPERATOR", "message": "An nlobjSearchFilter contains an invalid operator, or is not in proper syntax: custentity1.", "stack": [ "each(N/searchUtil)", "post(SuiteScripts/jarod_ss2/test-search.js:116)", "<anonymous>(SuiteScripts/jarod_ss2/test-search.js:149)" ], "cause": { "type": "internal error", "code": "SSS_INVALID_SRCH_OPERATOR", "details": "An nlobjSearchFilter contains an invalid operator, or is not in proper syntax: custentity1.", "userEvent": null, "stackTrace": [ "each(N/searchUtil)", "post(SuiteScripts/jarod_ss2/test-search.js:116)", "<anonymous>(SuiteScripts/jarod_ss2/test-search.js:149)" ] }, "id": "" } } The cause appears to be related to a search criteria on a custom field set to "starts with" blank, which of course has an associated filter. If I remove that criteria, the search will run from the script with no error.Am I wrong to expect a saved search that works in the UI to also "just work" from script?