UX Highlighted Value is not working for the decimal field on CSM/FSM Workspace.

rajendrabanoth
ServiceNow Employee

13 hours ago

I am trying to configure highlighted value for a decimal field. It is working as expected in form but not working on list view(It is not a first column on list).
I have used the same configuration on other field of the same table which working on both list and form levels.
Here are the some screenshots attached below:
Can someone please help me to highlight a value for a decimal field?


Preview file
30 KB
Preview file
21 KB
0 Helpfuls
  • 89 Views
1 REPLY 1

SachinNasa
Tera Contributor

13 hours ago

Hi @rajendrabanoth ,

I’ve faced a very similar issue earlier, including in ServiceNow Workspace scenarios.

In my case, the highlight/field style configuration worked correctly on the form view, but did not reflect in the list view, especially when the field was not the first column. This can be confusing—particularly when the same configuration works for another field on the same table.

After investigating and raising a case with ServiceNow, the explanation provided was related to scope and framework differences:

  • Forms and Lists use different rendering frameworks

  • Workspaces and Platform UI (UI16) are built on different frameworks

  • When fields are created or extended across different scopes (for example, global vs application scope), style rules may not behave consistently

  • Because of this, field styles can work on forms but fail on list views, even with identical configurations

This also explains the common question:

“If it works for one field on the same table, why not for this decimal field?”

In my experience, the inconsistency often comes down to:

  • The scope in which the field was created

  • The workspace vs platform context

  • How the list framework evaluates non-first columns

Unfortunately, in my case, the issue was not fully resolved, even after the ServiceNow case, as it’s tied to framework limitations rather than configuration mistakes.

Suggestion:
Check and compare:

  • The application scope of the field

  • Whether the list is rendered in Workspace or Platform UI

  • Any differences in how the working field was created vs the non-working decimal field

Hopefully this helps narrow down the root cause. I’ll update here if I receive a definitive fix from ServiceNow.

If you find this response helpful, please mark it as Helpful and accept it as the solution if it addresses your question—it would encourage me to contribute more to the ServiceNow Community.

 

Thanks & regards,
Sachin Narayanasamy