Articles in this section

Troubleshoot NetSuite error: SSS_INVALID_SRCH_OPERATOR

Error code: SSS_INVALID_SRCH_OPERATOR

Platform: NetSuite (via Celigo integrator.io)

Affected steps: Export, lookup

What you see in integrator.io

When this issue occurs, the error record displays the following details:

  • Message: An nlobjSearchFilter contains an invalid operator, or is not in proper syntax: <field>
  • Source: application
  • Code: sss_invalid_srch_operator
  • Classification: Value

The SSS_INVALID_SRCH_OPERATOR error occurs when NetSuite can't evaluate one of the filters in a search that an export or lookup step runs. The field named at the end of the error message is the field of the filter NetSuite refused.

A filter fails for one of three reasons, listed here from most to least common:

  • A lookup step's Additional search criteria row takes its value from the record, and that value is empty on the record.
  • An Additional search criteria row uses an operator the field type doesn't accept, or has no value.
  • The saved search itself holds a filter with no value.

Note: The same message can also appear on NetSuite imports, for example when the import runs its own lookups or when a script runs as the record is saved. That case is different and isn't covered here. This article covers exports and lookups only.

Find the filter that failed

Before you fix anything, find out whether the failing filter came from the saved search or from integrator.io. The filter list in the request shows both, in order:

  1. Open the error and view its request. The same request also appears in the NetSuite connection's debug logs.
  2. Find the line titled filters. The list starts with the saved search's own filters and ends with the filters integrator.io added from the step's Additional search criteria.
  3. Find the filter whose field matches the field named in the error message. If the step didn't add that filter, it belongs to the saved search.

NetSuite also writes the same filters line to its script execution log (Customization > Scripting > Script Execution Logs), right after the entry that records the request the RESTlet received. That entry is titled Data In Received, or POST Request Recieved on the SuiteBundle version. When the entries are there, a NetSuite administrator can see which filters ran without turning on debug logging or re-running the flow. NetSuite keeps these entries only while the RESTlet script deployment's Log Level is set to Debug, and only for 30 days. The connection's debug log always shows the filters line.

Troubleshoot exports and lookups

Cause 1: A lookup criteria value is empty on the record

Cause: A lookup step has an Additional search criteria row whose value comes from the record, for example Internal ID any of {{customerId}}. When that value is empty or null on a record, NetSuite refuses the search and names that row's field in the error.

If the field is missing from the record altogether, the step fails earlier with a Handlebars error instead of this one.

Fix: Use either of these approaches:

  • Add an input filter to the lookup step so that records without a value in the source field skip the lookup.
  • Make sure the source field has a value before the record reaches the lookup step.

Cause 2: A criteria row uses the wrong operator or has no value

Cause: A row in the step's Additional search criteria uses an operator that the field's type doesn't accept, or the row has no value.

Fix: Edit the row. Give it a value, and use an operator the field type accepts:

Field type Operator that fails Use instead
List/Record contains any of
Internal ID equal to is, or any of

Cause 3: The saved search holds a filter with no value

Cause: The export has no additional search criteria, but the saved search itself holds a filter with no value, for example starts with with nothing after it. NetSuite runs the search on its own pages, so it appears to work in NetSuite, but refuses it when integrator.io runs it.

Fix: In NetSuite, edit the saved search and either remove that filter or give it a value. You don't need to change anything on the export.

Contact Celigo Support

If the error persists after you complete the troubleshooting steps, contact Celigo Support and provide:

  • The error ID and timestamp
  • The integration, flow, and step names
  • The error request and response, including the filters line
  • Relevant NetSuite script execution logs

Quick reference

Step type Common cause Primary fix
Lookup Additional search criteria value is empty on the record Add an input filter so records without the value skip the lookup, or fill the source field first
Export or lookup Additional search criteria row uses the wrong operator or has no value Use an operator the field type accepts (for example, any of) and give the row a value
Export Saved search holds a filter with no value In NetSuite, remove the filter or give it a value