Default Value Creating New Value

[Paul_Danyliuk]

A common gotcha You’re using the result of Filter() as is — but this formula always returns a list of elements, even if it’s just one element in the list. What you see is one group for @[New Application], and another for List(@[New Application]). They look the same, yet they are two different things.

You need to use Filter(...).First() whenever you expect just one value.

See:

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…

You should pay extra care to this throughout this doc. Otherwise the issues may pile up until nothing works as expected.

P.S. Instead of the filter, you can simply reference the row itself using @-syntax. Start typing @New Application to select a specific row as a static row reference.

---

CC @Laurent_Auneau that’s for you too