Please check out the document below. Near the bottom, I show two Formulas, that act differently but shouldn’t. And pose questions near the bottom of the doc too. Any insight?
Example Case w/Questions
(Not sure how to embed this is a visible Coda Doc inside this post.)
Summary: A formula displays zero results when I prefix with CurrentValue, but displays correct count of results when I leave out CurrentValue. I seem to understand that Coda believes this is expected behavior? Unless they just meant to explain how to get around the unexpected behavior. I was told Nesting Filter/FormulaMap was causing a conflict to CurrentValue, and that WithName was not sufficient to correct that conflict, and that using CurrentValue was slowing down my formula anyway so I shouldn’t use it in the first place.
My comments regarding replys I’ve received about this formula:
“This doesn’t work because the Filter() argument is inside a FormulaMap() formula that also uses CurrentValue that corrupts that result.” *
… but thats what withName is for? And doesn’t it always grab the most recently established CurrentValue as a rule?*
“Also, CurrentValue is implied inside of the filter formula so it’s best to just remove that add’l CurrentValue and continue without it since it’s also probably slowing down that Filter() formula on top of getting mixed up with the FormulaMap() formula’s CurrentValue” *
… same thing here… I thought withname solved this problem and that it would always grab the most recently declared CurrentValue. Also as an aside, note the mention of CurrentValue slowing down the formula.*