How to use Custom Email field in Workflow recipient list?

[Systems Navigator]

Hi guys,

I am currently working on a workflow in which I would like to select the email of a recipient by a custom email field. I did this by creating a dropdown with different email addresses as labels. However when I activate the workflow and make it to send an email, it doesn't send it.

When I select a recipient by a specified user, it works fine. So apparently sugar does not read the email address correctly from my custom dropdown field. Is there maybe only one way to do this? I couldn't find anything about this. What type of field should I create with an email address to make this work?

Thanks for help in advance!

OS: Windows 2003 Server R2
Sugar: Version 6.6.0 Pro
Webserver: apache 2.0.59
PHP: Version 5.2.5
Mysql: version 5.0.45

[Systems Navigator]

Anybody knows how to do this?

Thanks

[eitrix]

just a sugesstion, maybe it reads the value of dropdown not a LABEL, thats why you are not getting the email adress? So if it's like mail1 => bla@blala.com, from that you get mail1?

Post if you found solution.

[Systems Navigator]

Hi,

The issue I described above is still not solved.

I tried to use a dropdown field first to get an email address for a workflow alert. But even if I use a textfield and enter an email address there, it does not work.

So the workflow does not send out the email. However it works if I just use assigned user for example. So the trigger works correctly, but it is not sending anything based on a custom field containing an email address.

Anyone an idea what could be causing this issue!

Thanks!!

[grex22]

Having the same issue -- did you ever figure out a solution for this?

It's odd that Sugar allows you select any field to send an email to, yet doesn't work at all for anything other than the default email field.

[grex22]

With the help of friendly Sugar support, I figured out the problem I was having -- maybe this will help the OP or others having the same problem.

My issue laid in the fact that for some reason the same relationship between modules was defined twice. I was selecting the wrong 'version' of that relationship when choosing the related module field to send the alert to.

Support helped me troubleshoot this, and choosing the other version of the relationship module solved the problem.