And I’ve set-up the Shop Warnings so to see what happens, but the reality is that we want to make it a hard-stop if the prior Operation is not Complete.
A post-processing BPM on Erp.BO.LaborSvc DefaultOprSeq method will do this.
That method will complete, but it returns a variety of messages depending on your shop warnings. Before the call is committed to the DB, your Post directive can catch if the returned message is “A previous operation has not completed.”
Hey David,
Just wanted to say Thanks - That worked a treat!!
Initially I didn’t seem to be getting the Shop Message, but refreshed Pilot & tried again & it’s now working!!
Cheers,
Kev.
This is exactly what we do, too. With one difference being that we check to see if the message is not blank. This results in if you change the Scheduling Factor to either Start-To-Start or Finish-to-Finish on the operation, then it will let you start that operation in sequence with the previous and stop you from doing so if the previous operation is not started (system message is something like “a previous operation has not been started”).