RDD Table Criteria on null value

Epicor ERP 10
, ,
1

Is there a way to create a RDD Table Criteria on a field with a null or blank value?

The reason why I’m asking is because I have created a Print Routing to email customer invoices and in order to accomplish this I needed to add the CustCnt table to the ARForm RDD to get the Primary Billing Contact email address… then created a relationship between Customer.PrimBCon and CustCnt.ConNum to limit the contacts to the Primary Billing Contact. The problem is that the Main Customer contacts and Ship To contacts can have the same ConNum per customer… so I need to limit the results in the RDD to only the contact with a blank ShipToNum.

2

I just went through this a week or so ago, did a lot of research and was unable to add table criteria in the RDD even on an aliased table (one of the suggestions).

What I ended up doing is putting the criteria in the print routing. Put the break in first, then your criteria between breaking and emailing.

Jenn

3

My favorite trick these days is to NOT use the Primary Billing Contact.

When setting up the customer contact - create a RoleCode called EmailCustomer. Assign the customer contact to the role “EmailCustomer”.

then in the RDD simply join by Company, and CustNum (i.e. All of the customers contacts).

Then in APR when you are configuring the Email Template - in the “To” field. Filter by Role Code.

This method allows you to control who and more importantly - how many people will get the Invoice.

DaveO

1 Like
4

This works for us as well. Allows us to be much more flexible with controlling who gets what documentation in the order to invoicing process…(Also works well in the supplier side).

5

I did something similar but used UD fields instead. I created check boxes for the documents (SO Ack, RMA, Invoice, etc.) so that multiple contacts can be selected to email them to. They are on the contact and I just add the contact table for the customer and filter by the check box.

Back to your specific issue though, can you not get there through a linked table? I find those the best as they are usually already filtered to your specific record.

6

I ended up doing the same thing just adding an UD field that does not contain a value and created a relationship to that field.