So long as you have columns in that query (I don’t see them in the snippet above) it should work. In SS2.x, you need to define at least one column. In SS1, a search could be run with no columns defined, though I can’t remember what you get back. Maybe just the internal ids of each record.

Was gonna say something similar to this, I believe its probably the issue. Although, query is usually really good about telling you exactly what is wrong.

Okay, thanks. I'll try including one column.

I haven't encountered a problem in SS2+ running a Search with no columns. Unsure about Queries though

Apparently queries need to have at least one column.

Yeah it would seem so

I'm starting to evolve to the opinion that I'll use Query only with SuiteQL, and Search for the rest

Well I needed it to look up properties of custom fields. Search doesn't support that.

Just for confirmation, this

Column

-less Search seems to work fine

Interesting. I have definitely had trouble with a column-less search before in a 2.0 script. It’s possible the behavior has changed since then, though, or maybe it is specific to the record type.

maybe eric's example was 2.1 and behavior improved from 2.0?

I don't recall a problem in 2.0 either

I know that in traditional searches I commonly provide an empty column list if all I needed is record internal ids as output.

Yeah, I am thinking it had more to do with the Map/Reduce not being able to serialize the result set with no columns present. I’ll have to test it again.