Hi @cnr and @Federico_Stefanato, i often end up using “table.filter(conditions)” directly in the formula of the column, or in select list column, depending on the needs, i think that i haven’t used a lookup column in a long! Why this approach couldn’t work?
Also, could it be that filters in lookup column use “currentvalue” and not thisrow approach?
It seems that maybe I’m wrong, it is no longer showing me thisRow, but it is still failing (and it could just be that the thisRow is implicit, sometimes it does get hidden) I can confirm that prepending thisRow at least replicates the error.
Yes sure!
Wait just a sec that i check if it behave in the same way “lookupping” the same table!
UPDATE: no ok totally unpredicted behaviour, let me explore deeper
Definitive update: You are right @cnr, when you create a lookup column that refers to the same table, the default formula created using “is equal to” lead to a strange behaviour that in my test created a complete list of the rows of the table where the “Source doc” (or whatever) is equal to Ops, or other text, and a blank list in every other
Obv there are workaround to solve the problem, but your idea of this being more a bug is supportable! @coda-team
Also, it happens with any type of “coda generated filter”, also using interactive one, and that happen because the formula, if is referring to his own table, turn currentvalue.columnname into thisrow.columnname, that part is wrong the rest works!
Obv, changing the formula to currentvalue make things works fine again
