SAP Marketing Cloud: Label column within custom field segmentation

[former_member558862]

I created two custom fields. Let's say:

• Dog breed (e.g. "GS")
• Dog breed description (e.g. "German Shephard")

There are no translations for the descriptions. The same description is used for all languages.

In the segmentation I want to filter on the codes. However, it would be good to have a description column available in the preview just as in this case for the marketing area:

Is there any way to do this?

I already thought about some ideas...

In the segmentation configuration there is some option to select a data source for values. However, I think this would mean that I would need some create such a data source first. So I can not just select the description attribute within the customizing of the code attribute.

Probably I could create some custom view which uses the description attribute as label column.

However, is there some more practical and easier way to set this up?

Thank you & BR
Christian

[SCHNEIDERT · Accepted solution]

Hi Christian,

may I ask why you created two Custom Fields? In your case above it looked like they belong together. So that's why my first thought is why don't you use a Custom Field of type Codelist?

As a Code you could enter GS and as the description you could enter German Shephard and use the "Translation" option in the Custom Field app to maintain the description in every needed language.

Then the Segmentation would look like on your screenshot for the Marketing Area.

BR Tobias

[former_member558862 · Accepted solution]

Hi schneidert,

thanks for that. Was also some point a head in mind. However, I think there are two reasons why that's not sufficient in my case:

• There will be new values in the future which would probably mean that I would need to ensure that those are also always added to the code list. I would not like to have this dependency...
• The description should be available in the export/personalization. Is this possible with the code list as well or would I have the code list for the code attribute and still some additional attribute in order to enable the description seperately for export?

Thanks for the input 🙂

BR
Christian

[SCHNEIDERT · Accepted solution]

Hi chackbusch,

regarding the first point: Yes, that's true

regarding the second point: If you enable the attribute in Segmentation Configuration also for the Export, you could automatically add the code and/or the description in the Export Definition. So, you can choose what you would like to have there, the field is automatically listed as two attributes (one for the code and one for the description).

So, that's why I would go that way, even if it means more effort for maintaining new values.

BR Tobias

[vervinckt_joyca · Accepted solution]

I agree with Tobias, I would also use a custom field of type "Code List", that way the code and description will always stay together, both for segmentation and for personalisation.

Even with a Custom View, I'm not sure if you would be able to relate the two. Because the two custom fields are only single-value, so there's nothing to make a Join on? Plus a custom view that is used for value help has a specific rule:

"A field in a calculation view contains the filter on $$language$$ if no text join exists in the calculation view."

And as you don't maintain translations you wouldn't be able to add such a filter. (I've been stuck on that point with one of my own custom views recently. I have a custom field field "Parent Account ID" with the BUPA ID of an account, and I also wanted to add the Account's name next to it, and I haven't succeeded in doing so yet...)

Maybe with a CBO you could maintain a code-value list, I haven't tried if CBO's are accepted in the "data source for values" within the segmentation configuration though.