Ok, I have the same UD fields on the Customer table and they work.
I have the same UD fields on the QuoteDtl table and they do not work.
Story time!! I have the same fields on the Customer, QuoteDtl, and OrderDtl. The intent of them is to identify what documentation is needed on shipment (RoHS, Material Certification, etc). The fields on the Customer are intended to be the default for the customer and there are DDs on the QuoteDtl and OrderDtl to set the default flags from the Customer to the added lines. Then, if a particular quote/order line has additional requirements, the user can select them at time of entry.
I just confirmed that those DDs are working as customers that have defaults are being added to the Quote and Order. So it is clearly the DD that is causing this, but I’m confused as to why?
This is the exact that really gets my with Kinetic.
THE EXACT SAME DD WORKS IN MY OLD ENVIRONMENT 10.2!!!
I’m going to change the logic to check to see if the row is added or updated and then branch off of that. But I am also going to open ANOTHER ticket. I should get a free trip to insights for all of the PRBs I have uncovered.
So I’ve calmed down some now. I did confirm that the DD was the problem. I turned it off and everything worked fine. I did go back to our old environment and made sure the DD was the same and that it worked. I have opened a ticket with Epicor and I will post the PRB when I get it.
Thanks for all of your help @hmwillett , would not have found it without you.
So, to come full circle, I finally got a response from support. They said that development fixed the logic and that it was working incorrectly in the older versions. For anyone else who might have used the shortcut, you will have to update your BPMs. Here is the hole they plugged:
In the older versions, if you used the condition “The field of the added row…” and there were no added rows, the condition would be ignored. Or in other words, there was a third option of “Do Nothing” along with the True and False paths.
This has now been fixed and when the condition is evaluated and there are no added rows, it follows the False path every time.