#C2C2JM29M #C298P0BCK So I feel I owe a few people an apology on here but I can’t remember who. I’ve maintained in the past that using a workflow action to dynamically calculate a field value is not possible. However I have found that it is now quite possible. For example if you have Field A, Field B and Field C on a record and you want to use a set field value action to set Field C = Field A + Field B but AFTER someone enters a value in Field A (without having to save the record), I have always found this impossible However in recent tests I was able to do this using the after field edit trigger. Not sure if this was something in a new release or I just wasn’t doing it correctly in the past but I’m sorry to whomever I’ve led astray!

Well, that was me recently... I thought I was trying that, however, I wonder if it's because I have too many dependencies... what I mean by that is Field A is a dropdown of words which sets Field B which is an integer... Field C another dropdown of words which sets Field D another integer... then I want Field E to be Field B + Field D... I also then need Field E to set the value of another "risk level" field which kicks off another workflow... I was able to work around it by making the employee save the record first before they can click the button that kicks off the next workflow... It wasn't ideal, but it works... I might retry your suggestion in sandbox to see if I can get it to work, though.

If you use sourcing to set fields B and D you might be able to use the after field sourcing trigger to calculate B+D then upon save trigger your other workflow