Let’s be a bit more computer-scientific about this:

AND and OR are commutative (i.e. their order does not matter), and, Traditionally and for fairly deep underlying mathematical reasons, AND has precedence over OR, ie. it binds more tightly: " `Cond.1 AND Cond.2 OR Cond.3`

" does indeed mean " `(Cond.1 AND Cond.2) OR Cond.3`

".

But also, " `Cond.3 OR Cond.2 AND Cond.1`

" should mean exactly the same: it’s the same as “`Cond.3 OR (Cond.2 AND Cond.1)`

” because of the precedence of the AND operator and the order of the pieces can be turned around because of commutativity. Think of AND as * and OR as +: `1*2+3 = 3+2*1`

. (In some programming languages there are variations on this theme in that the entire thing might stop evaluating as soon as the final truth value of the expression is known - this breaks commutativity and introduces the need to define associativity.)

Without doing too much, Airtable could at least implement the precedence rule, then allow mixing of AND and OR, and leave it at that. If there are no parenthesis operators implemented, one may simply have to repeat some of the AND-tests inside each of the OR’s: just as `a*(b+c) = a*b+a*c`

, one can work around needed parentheses for logical tests: for “`Cond.1 AND (Cond.2 OR Cond.3)`

” one could write “`Cond.1 AND Cond.2 OR Cond.1 AND Cond.3`

”.