I have two workflow rules which says:

First Workflow rule : Copy A's value to B .

Second Workflow rule: Coyp B's value to C.

I am finding issue with order of execution of above workflow rules, sometime Second is firing before First and copying old values. So i ended up have different value from B and C at end. Users Enter sometimes values in A and SomeTimes value in B.

Since both are field updates putting them both in one workflow rule will not make sense as field updates would also be in random order. Client don't want to go with trigger approach.

  • Why not just put into one wfr and with two field updates copy A to b and a to c? Seems a needs to go both into b an c buy your question. If entry is a problem use two wfr one with a condition a is blank and the other where a is not blank
    – Eric
    Apr 2, 2018 at 4:27
  • Are A and B the same SObjectType? and if not, in what way are they related?
    – cropredy
    Apr 2, 2018 at 4:38
  • 1
    Why don't you add a condition in or ISCHANGED(A) in second WF. Apr 2, 2018 at 5:46

1 Answer 1


Since it's difficult to put order of execution of workflows. I have encountered similar use case in my project.

So, First Copy A's value to B - perform by workflow.

and then Copy B's value to C - perform by process builder.

Since, workflow rule fires first, followed by process builder. Refer Triggers and Order of Execution

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .