[rt-users] Multiple Values don't show in email header using CustomFieldValuesAsString

Thomas Sibley trs at bestpractical.com
Wed Jun 6 19:48:57 EDT 2012

 06/06/2012 07:32 PM, matt schneider wrote:
>     However, if change Subject: to
>     {$Ticket->CustomFieldValuesAsString('CF Name');}, the email doesn't
>     even get sent out! I get this error in RT: [Wed Jun  6 15:21:03
>     2012] [error]: error:    couldn't parse head; error near:
>     ID1 (/opt/rt4/sbin/../lib/RT/Template.pm:363)
>     ID1 is the first custom value that is selected ( out of 4 ).
>     Is there any way of getting around this?

By default CustomFieldValuesAsString separates values with newlines.
Newlines in email header values are invalid unless they are followed by
a space to indicate a value continuation. This is basic rfc822 compliance.

Try this:

   Subject: { $Ticket->CustomFieldValuesAsString('CF Name', Separator => ", ") }

That is, using an alternate separator than a newline.

More information about the rt-users mailing list