Concat Custom Field Name instead of Value | Community
Skip to main content
Level 2
January 26, 2026
Question

Concat Custom Field Name instead of Value

  • January 26, 2026
  • 2 replies
  • 37 views

Hi all,

 

I have a custom field in my form that used a name as the name but an ID as the value underneath. For instance;

Starter: Soup - ID1234

Main Course: Pizza - ID2345

Dessert: Ice Cream - ID3456

 

Now I want to concat my three course meal in a different field called (three course meal) such that the outcome is;

Three Course Meal: Soup, Pizza, Ice Cream

 

However, if I concat based on the field itself it now gives the output:

ID1234, ID2345, ID3456

 

I know for all other ID fields in Workfront you can get rid of the ID and add .{name} but this does not seem to work for custom fields. Is there any other way that I can do this?

2 replies

KellieGardner
Community Advisor
Community Advisor
January 26, 2026

You have to use a series of IF statements to get this. Lots of questions on it out there without any solid answers. 

Level 2
January 27, 2026

Hi ​@KellieGardner, thank you for you reply!

I opened a few of the threads you linked to but could not find a consistent answer. The only thing I could find was that they use a replace function again to replace the ID with the label value afterwards, which seems interesting to say the least. This will make it very hard to scale when labels are added or removed. 

What do you mean by using IF statements? I cannot picture how this could be able to provide a solution.

ninoskuflic
Level 2
January 28, 2026

You cannot pull the label unfortunatelly, but you could have both the label and name in the name field.

For example:

  • Main Course:
    • Label: Pizza
    • Name:  Pizza - ID2345

You could then use the String functions to get the value of the name before the separator such as “-”. 😊

Depends on how you are using those fields later in the system but this is one of the options. Otherwise, you can use Fusion to achieve similar things and put the correct data in another custom field but this might be more complex. I would try going with String functions first. 

If this solved your issue, please mark it as solved so others can find the solution faster.
Level 2
January 30, 2026

Hi ​@ninoskuflic,

 

This seems to be the current “best” way of doing this. This will still create a need for one field to be split into two more which would result in three fields in total. This is because the ID is linked to the tags ID we use in AEM so I would still have to extract this to make sure this is consistent. 

 

Thank you for the help though!