I have a simple BPM that triggers based on a row being added or updated in a sales order for a few particular customers. (OrderDtl table)
I’m using ‘Changed Row’ as the target for the BPM.
The problem comes in with shipping - when they ship to one of these customers then the BPM triggers and they see the same message.
So, I guess this is a two-part question…
What exactly is the difference between Updated and Changed rows - when would I use on over the other?
Is there a way to tell the BPM to only trigger from SO Entry and not from Customer Shipment Entry or any other program that may change something iin the OrderDtl table?
It sounds like this is a data directive on OrderDtl table? If so, suggest migrating it to a method directive perhaps the Update method or do a trace and get a more specific one you’d like to trigger it on.
@spkeller Not sure on update vs change, but if you want to reign in the directive you can follow @timshuwy’s guide here BPM Trick - Call Context - only trigger sometimes... How to figure out what to do, but as @Randy suggests doing this on a data directive will still fire a lot. I would possibly use a post processing bpm on SalesOrder.ChangeCustomer or ChangeShipToID to put up a message for a sales person. A trace would be best to see what fires in your system.
@Randy, @gpayne, thanks for the input.
I’m currently going thru a trace, trying to find a better process for the trigger.
I just grabbed @timshuwy’s post and I’ll read through that to see if I can get any additional info to help with this.
Thanks again.
Re-reading your post, you’d be better served calling your BPM on the SalesOrder.Update Method Directive and have a condition that checks for Add or Update.
