Report Start Expression: Filter condition

Hi,

I am working on a start expression used to filter a report.
Note the report worked perfectly when its filter was just to grab the data from the table and order it.
Now I am trying to remove some potential rows from this report.

Here is the Expression:

ORDERBY(
FILTER(
Faults,
AND(LEN([Equipment])<=3),
[Equipment]<>“W14”,
[Equipment]<>“W22”,
[Equipment]<>“W23”,
[Equipment]<>“W35”,
[Equipment]<>“W38”,
[Equipment]<>“W46”)),
[Equipment],False)

As you can see I am creating requirements for the rows.
One is tha the length of the name in Equipment is equal to or less than 3.
This works correctly as tested by itself.

My next step was to remove specific results, I attempted this by creating and AND( in the select row portion of the filter expression. For some reason this fails and I cannot work it out.

Appsheet is telling me this expression does not produce a list of ref values?

Your parentheses are wrong:

image

Note too that a <<Start>> tag must be a single line; it cannot contain line breaks (though line wrapping done by Docs/Excel/Word is okay).

Try this:

<<Start: ORDERBY(FILTER("Faults", AND((LEN([Equipment]) <= 3), NOT(IN([Equipment],{“W14”, “W22”, “W23”, “W35”, “W38”, “W46”})))), [Equipment], FALSE)>>
3 Likes

Worked a charm thanks @Steve!

Yeah I had been trying every other way I could think of hense the incorrect parentheses.
Thank you for the tip on the Start tag, although mine was correct I just tried to make it more legible.

So the issue I had was not making each section of the and statement a seperate item so to speak with brackets?

The NOT(IN( system is a lot better in every way (I tried this way earlier but couldnt get it working) but effectively works the same no?

1 Like

The expression you posted had extra “stuff” after the closing parenthesis of the ORDERBY() function. I suspect that extra confused the editor, leading to errors.

It is functionally the same, but more efficient.

3 Likes

I had a similar problem with a workflow template. After trying tons of different troubleshooting efforts, it finally worked when I took out all the returns in the very long expression. It’s interesting that in the expression editor you can space it out pretty much anyway you want for readability but can’t do that at all with a Start expression.

2 Likes