Efficiency when iterating

[Paul_Danyliuk]

Hey Robert,

Regarding having to enumerate all columns when copying a row with AddRow() — I totally feel your pain. I logged a request a while ago:

Add CopyRows() capability

Sometimes there’s a need to copy a row or multiple rows, e.g. to make a snapshot of some data. Think of a pricing calculator table with lots inputs for different percentages etc — and the salesperson wants to make multiple variants with small changes to be able to quickly switch between. Copying a row with AddRow() and enumerating all the columns is not a problem… unless there’s a few dozen of those. CopyRows() could be a handy formula. It would accept a row or a filtered table, and for variad…

I have the same need at the moment (make snapshots of a table with dozens of columns), and the only way I see to make it easier is to grab the table, copy it into a text editor, and with some find/replace/regex magic compose a formula out of it.

Re your button formula, what you can do is combine the ModifyRows+AddRow in a single action:

thisRow.ModifyRows(thisRow.LogAddress, TheLog.AddRow(
  Log.Datapoint1, thisRow.[Datapoint 1],
  Log.Datapoint2, thisRow.Datapoint2,
  Log.Datapoint3, thisRow.Datapoint3
))