Loading Profile...
Lookup query returns lookup message as hit instead of empty set
Lately I have noticed that "lookup" queries sent via email (or twitter) returns the query message (e.g. "l nomatches" returns "#1 <right> l nomatches" as its only result). This appears to only happen for searches which return no results -- those which return results seem to work fine.</right>
I’m frustrated
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
-
Inappropriate?Hi JRK,
Thanks for the heads-up on that. We'll take a gander and see what's what.
From what I'm reading, though, you're not missing any thing in lookups, but are rather wondering about the odd result when there are no matches — am I correct?
—Rael
EMPLOYEE
