Multiple Values don't show in email header using CustomFieldValuesAsString

Hi,

I have a few custom fields that I display in my autoreply template email
header when a user creates a tickets.

This works fine and dandy when it’s grabbing the Custom Fields via
{$Ticket->FirstCustomFieldValue(‘CF Name’);}, but one of the CFs is of type
"select multiple values"/ render type “List”. If I select this field via
FirstCustomFieldValue, then only the first value in the field will be
selected, but I have up to 4 that I need to show, so this is no good.

I’ve noticed in the body of the email I can display all the values in this
field by using CustomFieldValuesAsString, and this works fine.

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?

Cheers,

Matt

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:

That is, using an alternate separator than a newline.