Simple Trick: Keep using row data in same action *after* you already deleted the row

[Paul_Danyliuk]

I need to play around with this idea more. E.g. here’s one way to push multiple variables in nested formula maps:

Now I need some useful application of this.

Maybe it’s also possible to achieve the nested CurrentValue calculation using this trick. Previously the only viable way I found (with live formulas, not actions) is this:

Dedupe an array of arrays based on a common key/object with formulamap()

Alright, here’s an explanation (also noticed a problem with my solution while writing this post, lol, so fixed and also simplified). Normally the solution would look like this: Get the list of unique emails as [List of lists].FormulaMap( CurrentValue.Last() ) given that emails are last in each list. Run a simple formula map: [Unique emails].FormulaMap( [List of lists].Filter(CurrentValue.Last() = uhm… CurrentValue).First() ) i.e. for each email (CurrentValue) filter the list of li…

And with actions I almost exclusively use this trick: Tutorial: Iterator tables (CurrentValue workaround). It’s universal enough to be considered as a to-go solution, a reusable design pattern (if you’re a software engineer, I mean something like GoF patterns)