I am working on emailing AR Invoices directly to the customer. It is working fine when there is a valid email address in the field, but when we have an invalid email in the field Customer.EmailAddress then the process does error out, which is fine, but we would like to be notified about this. I do not even get a bounce back email address. Instead, we have to go into System Monitor and verify those that errored out.
Any thoughts?
We have the exact same setup. We have a condition in the Breaking and Routing that checks to see if the Customer Email address is valid (contains an ‘@’ and ‘.’) and if it is, it proceeds to send the invoice. If not, it sends an email to the user saying the invoice could not be sent. You could alternatively have the report print-preview if you don’t have a valid email, and train your users to know if the report comes up then it couldn’t send.
1 Like
ditto
So with that said, I get what you are saying, but we also have it set up where the To: is our ARTeam and the CC is the Customer.EMailAddress
so it should still be going out to the ARTeam regardless, but we should get a bounce back with the typo in the Customer.EMailAddress (i.e. Joe@dizney) where the email address is missing the .com
We have had the same issue and have a Problem Number through EpicCare (they have accepted that it’s a bug).
I’ve found that the address parser must be very picky. Sometimes a double or trailing ; (which separates email addresses) caused problems.
Address fields setup like:
me@co.com; <CustEmail>; you@co.com;
Could cause problems if <CustEmail> evaluates to a null
We have set ours up to email the invoices to accounts if the email address is missing or invalid, that way they can forward those ones on manually or at least go in and check the customer.