This issue is reopened, because it seems it still exists.
There is a customer with several emails defined: billing, billing cc, email. Checkt the attachment.
When I tried to send an offer by email, the email address sections were empty, all of them. When I clicked to continue, it dropped an error: no email addresses provided.
So, I am confused, how it is working.
Hi, Istvan,
I've seen trouble in this area too. We use the email functionality for 3 different workflows:
Sales Invoices
AR Aging reports
Sales Orders
Sales Invoices do work consistently. IIRC, AR Aging and Sales orders leave the email "to" boxes blank. At least one of these ignores whatever you enter and sends to the email address(s) listed on the customer -- we've sent out a number of test emails that have gone to a customer unintentionally.
What are you trying to send? I think each item you're trying to send needs individual attention...
Hi,
It's the aging one that ignores the entered values. I too sent out test
mails to customers. The aging one is fixed in a recent patch release in 1.3.
Regards,
Erik
sent from my phone
On Feb 15, 2014 6:39 PM, "John Locke" freelock@users.sf.net wrote:
Related
Bugs:
#1073I use email sending function for the following workflows:
Independently of my workflows, it should work in all cases.
In real life scenario, I can imagine, different emails belong to different functions, like offer and invoice should be sent to different addresses.
Instead of get a random email address from contacts, maybe a multiselect list would be better, which includes all existing emails of the contact, in description - email pairs.
Sales Order also did no pull the email addresses.
I check it.
It seems the offer/order forms did not pull email addresses, while the invoice form did. That is why offer and order form cannot insert email addresses into the right fields.
Anyway, these fields are hidden.
Screenshot example to clarify the issue.
So the problem is that the email information is set in Form->create_links where it should probably be elsewhere. This will take some significant refactoring.
I have fixed thsi for orders. Unfortunately this is not trivial to add for aging reports. Maybe this patch is helpful for that? At any rate the ar aging email addresses can be a different ticket.