Lookups, different results, different input methods?

[Paul_Danyliuk]

Just scanned through the thread, and it definitely looks like a one vs list-of-one issue (and maybe even a list-of-list-of-one further down), which started somewhere deep down and propagated like a virus throughout all of your data. That’s why it is important to always check for proper data types and notice and fix issues asap.

Related thread:

Here’s a riddle for the community

I have a table that’s a list of tasks for clients. Grouped by client. How come that I got two groups for the same client? [image] And no, those aren’t two different rows — it’s the same client. Hint: some tasks were entered manually with client being selected from a drop-down list. And the other tasks were created with a button, copying the value from the “Current client” field in a supporting table. (I know the answer. I just wonder if you can figure what went wrong. There’s a lesson in he…

Examine all your Filter() formulas closely. Properly set “allows multiple values” on columns themselves. If you expect one value, use .First() after .Filter(). Live formulas should fix themselves after that. And for copied data make buttons that would automate unwrapping those potential lists, e.g.

thisRow.ModifyRows(
  SuspectedListColumn, thisRow.SuspectedListColumn.ListCombine().First()
)

P.P.S. Also get into habit of programming button actions with formulas and not by selecting dropdowns. In my experience it’s much easier to spot errors in formula code.