RunActions and Recalculations

I have a button that is behaving inconsistently and am wondering if I misunderstand how RunActions works. I have a formula on button click that moves a value from one column to another, then clears the initial value:

RunActions(
  ModifyRows(thisRow, thisRow.[Source ID (Complete)], thisRow.[Source ID]),
  ModifyRows(thisRow, thisRow.[Source ID], List().First())
)

Most of the time, this works fine, but sometimes, I wind up with two blank columns. My understanding is that with RunActions, the second parameter will only run after the first completes and the doc recalculates, but instead this feels like a race condition.

Can any one shed some light on this? I can see in the row’s activity that there previously was a value that was cleared out.

Hi @Dan_Mesa,

You that has been my understanding and experience with RunActions.

I just created a test of this and couldn’t get it to work.

I don’t understand your use of List().First() in your code.

List requires either an entry into the List between the brackets or to be the end of an object to form the List. If working with tables as a list it needs a column otherwise you’ll get the whole row referenced. E.g. TableName.List().First().ColumnName or List(TableName.ColumnName).First().

Hopefully this points you in the right direction.

If not please provide some clarification the specifics of what you are trying to accomplish so I can understand better.

All the best

Dale

Hi Dale, thanks for the reply. The formula is moving a value from one column to another, then clearing out the original value. List().First() is just being used to provide a blank value and appears to be unrelated to the issue.