TLDR Carlos encountered a "Search field not found" error and suggested including the field name in the message. Hengfei agreed and asked Carlos to create an issue.
Forgot that string literals in SQL happen with `''` so changed `"999.0.0.999"` with `'999.0.0.999'` and it is fixed now
This was the screenshot btw:
we will make new release soon
Oh I see. As a suggestion, would it be possible to include the field name in the error? Like instead `Search field not found` -> `Search field "999.0.0.999" not found` That would help to figure out the root cause
Ha, you need use single quote for values.
SQL has some limitations, field name can use without quote or must use double quote, field value must use single quote.
Yes. That's correct. I figured out later as I explained before. I'm suggesting to change the error message to include the field name. That will help to figure out that something is wrong
it reports by backend, but UI not report. Can you create an issue for this? we will improve UI error report.
Here we go:
Carlos
Tue, 27 Jun 2023 09:08:44 UTCGetting this error when adding a second filter `Search field not found`: But it is a field that was on the available columns, and also that was already used for a count and for the X and Y columns