Prevent Method Directive from Running when Attached to a Directive that is Invoked by Another Method Directive

Is there a way to prevent a method directive from running when the method to which it is attached is invoked by another method directive? For example, I have some functionality in a post-processing directive on ERP.BO.Customer.GetByCustID that I want to run mainly when I’m loading a customer into the customer form. I also have pre-processing on ERP.BO.Customer.Update that invokes the ERP.BO.Customer.GetByCustID method (to get the dataset on another customer), but I don’t want the post-processing directive to run. I was thinking that using a BPM data field as a marker might work, but I was hoping there was a simpler way.

Not sure I understand your sequence but…maybe callContextClient.ProcessId?
I often add it as a condition in BPM’s
image

Bruce,

Thanks for suggestion but unfortunately the process IDs are the same.