Error Message Enhancement for Missing Search Fields

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.

Photo of Carlos
Carlos
Tue, 27 Jun 2023 09:08:44 UTC

Getting 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

Photo of Carlos
Carlos
Tue, 27 Jun 2023 09:37:59 UTC

Forgot that string literals in SQL happen with `''` so changed `"999.0.0.999"` with `'999.0.0.999'` and it is fixed now

Photo of Carlos
Carlos
Tue, 27 Jun 2023 09:38:54 UTC

This was the screenshot btw:

Photo of Hengfei
Hengfei
Tue, 27 Jun 2023 10:49:10 UTC

we will make new release soon

Photo of Carlos
Carlos
Tue, 27 Jun 2023 10:50:41 UTC

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

Photo of Hengfei
Hengfei
Tue, 27 Jun 2023 10:52:32 UTC

Ha, you need use single quote for values.

Photo of Hengfei
Hengfei
Tue, 27 Jun 2023 10:54:35 UTC

SQL has some limitations, field name can use without quote or must use double quote, field value must use single quote.

Photo of Carlos
Carlos
Tue, 27 Jun 2023 10:55:46 UTC

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

Photo of Hengfei
Hengfei
Tue, 27 Jun 2023 10:56:41 UTC

it reports by backend, but UI not report. Can you create an issue for this? we will improve UI error report.

Photo of Carlos
Carlos
Tue, 27 Jun 2023 12:55:36 UTC

Here we go: