Method Directive not honoring new value

[markb_wi (Mark Bernhardt)]

I have a method directive on SalesOrder.Update and am running into a real bugger of an issue which I think should be easy.

Customer service would like a pop-up box if they add a SO line and the parts have certain header analysis codes. They want to be warned that they added a subassembly and not a top level assembly due to customer part number confusion.

I can get this to work on a NEW line but on an updated line the BPM is not working correctly. My BPM checks for two Analysis codes in a query and should return more than one line if either of those codes is assigned.

If I change the part number from any part to a subassembly it sends a popup
If I change the part number from a part NOT a subassembly to one that is NOT a subassembly it does not send a popup.
If I change the part number from a part that is a subassembly to one that is NOT a subassembly it sends a popup and that is wrong.

The Query seems to be looking at what it was and what it becomes at the same time. I tried adding OrderDtl where Company=Company, OrderNum=OrderNum, OrderLine=OrderLine and added criteria on ttOrderDtl whereSysrowID<>OrderDtl.SysrowID and get an infinite wheel of death when saving.

[hkeric.wci (Haso Keric)]

How many Parts do you have?

BPM SPEED Helpful Hint - be careful how you "Join"

Help Hint for you all… I have been doing some refactoring of BPMs for efficiency. Finding mistakes made from prior sins of myself and others. You can probably find some ways to improve your end user’s experience by doing some of these same changes… note that this refactoring takes about 5 minutes, but saves users lots of frustrations. THIS example is applicable to all users (including Cloud). Also, as an encouragement to those NOT attending Insights… I learned about the need for this trick last…

Joining "TT" records to regular DB records in BPMs

I am opening up this topic, because it was raised at #Insights2018. Please join in on the discussion if you have examples that prove this wrong!!! I just want to curb any urban legend that may be building out in the community based on misunderstood ideas. There was a recommendation made during one of the sessions that JOINING a TT record to a regular database record was bad practice. Instead of joining, you should simply add conditions in your query for any of those links between TT and non-TT…

[tsmith (Tyler Smith)]

Try setting a table criteria on the ttOrderDtl table in the Query where RowMod == “U” or RowMod == “A”. I believe method directives are passed an unmodified row and the modified row for the pre and post comparisons, so your query sees both the original row and the updated row and passes.

[hkeric.wci (Haso Keric)]

Also your Part is the first table and ttOrder is 2nd, change the order.

[markb_wi (Mark Bernhardt)]

Thank you the BPM Speed article was the solution. Amazing and I’ll use that from now on. If I had only seen that 3 years ago! It would have simplified things quite a bit.