How To Display Custom Field Data in RT 3.4.0

RT Users
1

What do I need to pass to TicketList’s Format in order to display Custom
Fields, in RT 3.4? I use to use CustomField.{Name} in RT 3.2, however,
this now returns any/all custom fields.

I see references on rt-devel to FirstCustomFieldValue, but I can’t figure out
any variation or combination which makes this work.

For example, I have a Global Custom Field (of style “select one”) named
PrimaryContractor, and I would like to display that field inside of
Elements/TicketList.

Any feedback is appreciated.

-jd

2

Jason A. Diegmueller <doogles doogles.com> writes:

What do I need to pass to TicketList’s Format in order to display Custom
Fields, in RT 3.4? I use to use CustomField.{Name} in RT 3.2, however,
this now returns any/all custom fields.

I see references on rt-devel to FirstCustomFieldValue, but I can’t figure out
any variation or combination which makes this work.

Any progress on this issue? I’m currently experiencing the same problem (3.4.1)
and would like to be able to build queries with custom fields shown in the
results.

Sincerely,

Mattias Nordstrom
CTO
Oy Realnode Ab

nordstrom@realnode.com
www.realnode.com

3

Jason A. Diegmueller <doogles doogles.com> writes:

What do I need to pass to TicketList’s Format in order to display Custom
Fields, in RT 3.4? I use to use CustomField.{Name} in RT 3.2, however,
this now returns any/all custom fields.

I see references on rt-devel to FirstCustomFieldValue, but I can’t figure out
any variation or combination which makes this work.

Any progress on this issue? I’m currently experiencing the same problem (3.4.1)
and would like to be able to build queries with custom fields shown in the
results.

I’m running in to this as well. Modifying $DefaultSearchResultFormat
to get it to display a couple of custom fields gives me the wrong ones.
Any docs/pointers on how to fix this? Running 3.4.1 as well.

-jkl