Unable to apply UX Highlighted Value color on primary (first) column in CSM Workspace list

[AviKadam]

Hi Experts,

I am trying to change the color of the Case Number field in CSM Workspace list view using UX Highlighted Values.

What I have done:

• Created a Highlighted Value configuration for:
  • Table: sn_customerservice_case
  • Field: number
• Added conditions:
  • when field xyz  = true
  • and field abc is not empty
• Set the color (e.g., orange)

Current Behavior:

• When the Number field is placed as the 2nd column, the highlight works correctly and the color is applied.
• However, when I move the Number field to the 1st column (primary column):
  • The color is not applied
  • It remains blue (default hyperlink style)
  • The field is still clickable (which is expected)

Requirement:

I want the Case Number (first column) to:

• Have a custom color (e.g., orange) based on conditions, this will be applied to sort some specific cases.
• Still remain clickable (retain navigation behavior)

Question:

Is it possible to apply UX Highlighted Value styling on the primary column (Number field) in CSM Workspace while keeping it clickable?
If yes, what is the recommended approach?

Any guidance or best practices would be really helpful.

Thanks in advance!

[pr8172510 · Accepted solution]

Hi Avi,

Yeah — this is a known limitation in CSM Workspace.

What’s happening

The first column (primary field) in Workspace lists is rendered using a special component (record link), not the standard field renderer. Because of that:

• It always uses the default link styling (blue)
• UX Highlighted Values are not applied to the primary column
• When you move the field to 2nd column → it uses normal renderer → highlight works

---

Short answer

No, OOTB you cannot apply UX Highlighted Value styling to the primary column while keeping it clickable.

---

What you can do (workarounds)

1. Keep it as second column (simplest)

• Move Number to 2nd column
• Keep highlight working
• Use another field as primary

Not ideal, but fully supported

---

2. UI Builder customization (advanced)

If you really need this behavior:

• Go to UI Builder → Workspace list page
• Override the list component / cell renderer
• Apply conditional styling to the link

 This requires:

• Custom component logic
• Handling navigation manually

---

3. Use additional visual indicator (recommended compromise)

Instead of coloring the number itself:

• Add a status/flag field with highlighted value
• Or use an icon/indicator column

This keeps:

• Clickable primary column
• Visual distinction via adjacent field

---

Why this limitation exists

The primary column is treated as a navigation anchor, and its styling is controlled separately to maintain consistency across Workspace.

[pr8172510 · Accepted solution]

Hi Avi,

Yeah — this is a known limitation in CSM Workspace.

What’s happening

The first column (primary field) in Workspace lists is rendered using a special component (record link), not the standard field renderer. Because of that:

• It always uses the default link styling (blue)
• UX Highlighted Values are not applied to the primary column
• When you move the field to 2nd column → it uses normal renderer → highlight works

---

Short answer

No, OOTB you cannot apply UX Highlighted Value styling to the primary column while keeping it clickable.

---

What you can do (workarounds)

1. Keep it as second column (simplest)

• Move Number to 2nd column
• Keep highlight working
• Use another field as primary

Not ideal, but fully supported

---

2. UI Builder customization (advanced)

If you really need this behavior:

• Go to UI Builder → Workspace list page
• Override the list component / cell renderer
• Apply conditional styling to the link

 This requires:

• Custom component logic
• Handling navigation manually

---

3. Use additional visual indicator (recommended compromise)

Instead of coloring the number itself:

• Add a status/flag field with highlighted value
• Or use an icon/indicator column

This keeps:

• Clickable primary column
• Visual distinction via adjacent field

---

Why this limitation exists

The primary column is treated as a navigation anchor, and its styling is controlled separately to maintain consistency across Workspace.

[Ankur Bawiskar · Accepted solution]

@AviKadam 

not possible if you keep Number column in 1st position

1st field in list is always a link to that record and is shown in blue color

This is the same behavior I believe when you use Field Styles in native.

This is platform behavior and I don't think you can change this

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[AviKadam]

thanks for the clarification Ankur