LAE

Welcome to the LAE community!  Please feel free to start a discussion in the discussion tab or join in a conversation.

Discussions

Members

Resources

Events

 View Only

  • 1.  E-mail Node Error from Null Addresses

    Employee
    Posted 06-02-2016 10:28

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: HHamilton

    Hi,

    I am getting an error on the e-mail node because the cc email is null. Is there any way around this without having to populate that email address?

    Thanks,
    Heather


  • 2.  RE: E-mail Node Error from Null Addresses

    Employee
    Posted 06-02-2016 11:25

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: stonysmith

    That shouldn't happen. Can I assume that you're using the "Send Email+" node? It should allow you to send an email without having to populate that parameter. In the dropdown, select "Default" (not Literal or Field) and then leave the parameter empty.

    What version of LAE and more importantly, what version of LAL are you using?


  • 3.  RE: E-mail Node Error from Null Addresses

    Employee
    Posted 06-02-2016 14:18

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: ryeh

    I spoke with Heather as I was on-site today. So I, too, had initially misunderstood the question. The problem is, Heather wants to send the e-mail to AddressA and cc: AddressB. Based on the data conditions, sometimes AddressB is null/blank. In that case, the e-mail node errors. The work-around we came up with was to merge both addresses and use only the To: field. If AddressB is null/blank, then AddressA is used, otherwise the two are concatenated with a semi-colon ( ; ) separator.


  • 4.  RE: E-mail Node Error from Null Addresses

    Employee
    Posted 06-03-2016 00:28

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: awilliams1024

    Hi,

    an alternative approach for the work-around could be to split the input records depending on whether the Cc: field was populated. This would allow the emails to retain the original context - i.e. whether the email recipient was the To: party or a Cc: party. The attached data flow shows how it could be achieved by checking for the presence of the '@' character in the field. It also splits off records that do not have an '@' in the To: field as this is an erroneous condition:

    Send_Email_Plus_Node_Handle_Missing_cc_Fields-share.brg

    Regards,
    Adrian