Large Text Fields Segmentation - Improved Search and Selection

RichardGar

We use large text fields for storing interest. Someone can have lots of different interests and to preserve space we have used codes for interests which means more can fit but harder for the end user to instantly know what the interest its.

Some of our contacts are interested in a lot of things and as such they have reached the limit of the 250 characters for a CDO text field. We have had to go to large text.

Both text and large text are harder for the users to select compared to picklists for example. It would be great to provide an improved way to search and select for sub strings based on reference data such as the value and name being different as it is for picklists. For example if I have this data set

Sample Contact Record

Contact ID | 123

Interest Field Codes | FOOT, RUGB, BASE, HOCK...

Reference / lookup table

FTB | Football

RGB | Rugby

BSE | Basket Ball

HCK | Hockey

If I was creating a segment to contacts with an interest in basketball it would be great if they can see the lookup, so when they type "Foo" it auto suggests "football" and when I select football would use "FTB" as the critiera. Therefore running a partial search and returning a readable value rather than the code

This is the same functionality as we have at the moment for select lists such as with country per below:

Interesting in Eloqua topliners the ability to add tags is another way this could work. So each of these tags would be interests in my example.

RichardH

I'm curious if you considered using custom objects to store these values?  It would make segmentation easier but perhaps not as much for updating within Eloqua.

RichardGar

I'm curious if you considered using custom objects to store these values?  It would make segmentation easier but perhaps not as much for updating within Eloqua.

Hi Richard,

Yes we are currently using CDO fields for these. One issue is dynamic content rules don't work on large text fields though and as you say updating within Eloqua as well.

Kind regards

Thamina Christensen-Oracle

We are currently not considering this feature.