Hi there my friends. I am not going to deeply discuss the scenario where this applies, its complex.
So I am just placing here this solution in case anyone else needs it:
Say you need to execute several actions for a row, where one of them is delete that row, and after deletion, you need to trigger and update action in a related row on another table.
There is a way, using FormulaMap to store the data
RunActions( ... "Several actions ... FormulaMap( thisRow.relatedRow, "Here you store your value: the related row you will use later DeleteRows(thisRow), "Then, you delete your row CurrentValue.UpdateData "Now, you update data in your related row, where you needed current row gone for correct calculation ) )
Why would I manually want propagate changes through my model instead of directly relate changing fields to each other with formulas?
Because those related fields will severely impact in performance if your document is complex. By manually changing only data you want, when an user executes those changes, you significantly improve performance.
Disclaimer: Those are my assumptions, I can’t be sure of this statements.
Be wary keeping good UX in this manner will require to create lots of forms by using more auxiliary tables.