Method Directive or Data Directive

Hello,

Long time follower first time poster.

I am in the process of exploring BPM and can handle some simple basic ones in designer.
I have reached the point where I want to get a bit more technical and potentially join information from 1 table into another table and not sure whether a Method or Data Directive is the best route to go.

In this case under the Customer Entry Table I have created a UD column that I am using to flag if a customer has a Partnership deal with our company and therefore subject to special rules.

I then created a similar UD Column for Partnership in the Sales Order table and have a custom checkbox there.

What I want to happen is that when a Sales Order is started and the customer is entered the Partnership checkbox gets checked if that Customer is on Partnership and a message pops up for the Sales Entry person to alert them that the Customer is on Partnership and then have a Post-Processing email sent to our Production Manager. Right now I can get it to populate that checkbox using the data tools in customization but I am unable to figure out a Method Directive as it is not in this OrderHed table.

Any help would be greatly appreciated.

BPM’s pull in any UD columns attached to your BO automatically.

If the UD field isn’t part of the service you’re working with, I tend to use a condition widget with the “Number of rows in the designed query” to cross reference whatever I want.

In this case I am using two different tables.

Use the “Number of rows in the designed query” option in the condition widget. It lets you build a simple-BAQ-like lookup.

I’d also strongly recommend putting this on SalesOrder.Update rather than a data directive.

In this case I’d use that design query to search and then set field if true?

Do I need to join that Customer Table to the SalesOrder table to be able to set a field inside SalesOrder?

Yes, join ERP.Customer to ds.OrderHed.