If you expect zero, one or more items from the filter, the formula is correct. Just make sure to also enable “multiple values” in column settings.
Often errors happen when you:
- don’t use .First() when expecting zero or one value
- copy with a button what you think a single value from another table, but is set up to be “allow multiple values” (hence copying a list)
- mistakenly reference a whole column and not just one cell
2 Likes
I had a similar problem in that I had a multi-value lookup column using a formula that was giving me the dreaded “**** is not a valid row reference.”
I found a solution:
Rather than using
thisRow.Txact.Tags
And observing
I used
thisRow.Txact.first().Tags
And observed
The coda app is a double entry accounting system that contains 3 tables:
tbl_Txfer (each row is a credit or debit financial transfer for an account)
Id, Txact (Single Val Lookup), … Txact_Tags (Mult Val Lookup)…
tbl_Txact (each row represents a set of transfers)
Id,… Txact_Tags (Mult Val Lookup)…
tbl_Tags (each row is a uniqe tag used for filtering tbl_txfer or tbl_txact)
Id, …
I needed to use the First()
method to ensure I didn’t get the dreaded “is nto a valid row reference error.”
Hope that helps someone.
1 Like