Maintain outer scope in two for loops?

[mal]

Trying to do something trivial to do with two for loops but surprisingly incredibly hard to do with coda.

Say I have two values, Ps (say p1…p5) and Bs (say b1…b10)
I have one table here I want a selection to allow users to choose among values, in csv form that would ultimately look like:
P1, B1, B5, B10
P2, B2, B3, B10
…

What I need is to then have a view that creates a row for each pair chosen. That is, in csv that would look like:
P1, B1
P1, B5
P1, B10
P2, B2

etc.

Essentially what I need is something like this pseudocode:
for each row r1 in Assignments:
for each b in r1.Bs:
AddRow(Pairs, Pairs.P, r1.p, Pairs.B, b)

I’ve tried many combinations of FormulaMap and Sequnece but the fundamental problem seems like any looping construct losses the scope of the parent loop. That is, if I tried to have a FormulaMap within a FormulaMap “CurrentValue” only has the inner scope. Another thing I tried is to first add all the Ps and then add all the Bs in a different formula but I run into the same issue. Don’t really see how coda can claim to be turing complete. Any ideas?

[Paul_Danyliuk]

Here’s the trick you’re looking for:

What to do when CurrentValue is overloaded

That’s a know thing: There’s a workaround with storing the outer CurrentValue in a cell somewhere (e.g. same row dedicated column, or a helper table). E.g. here’s the way I’m iterating over Value Drivers, then each of their Metric Uplifts, then for each of those I insert six rows with a Sequence().FormulaMap(). Note how I store _Current Value Driver and _Current Metric Uplift into a cell before using it in a nested FormulaMap: [image] [image] (Fun fact: in retrospective, in my case none o…