SydneyH

Thank you for explaining this so thoroughly. I believe we can run the trigger on Insert only, vs. both insert and update. We are tracking each deposit as its own line item upon entry/insert. The starting balance for every new participant is always 0, which is likely where my problem was considering the 'case' logic was not implemented. This fixed our issues. Thank you so much! -Sydney

I have a triggered action setup with the goal of replacing the "Account Balance" in one table, based on entry into the other table. The triggered action is currently setup to add the newly deposited amount to the existing balance. The task validates but won't populate the data as intended unless I remove the "addition problem". If the task is set to update 'Account Balance = #inserted.DepositAmount' it will run successfully. Has anyone else experienced this issue? I have nearly identical tasks within other tables of my application that function as intended with subtraction of similar variables.