Issue with Populating 'Customer' Field from Reference Table in ServiceNow

NikhithaNikki
Tera Contributor

I am experiencing an issue with a select box field named "customer" in ServiceNow. The field has the following choices and backend values:

  • Very Low (1)
  • Low (2)
  • Moderate (3)
  • High (4)
  • Very High (5)

This field is populated from the cmdb_ci_business_app table using dot-walking. When I select "existing digital platform," the customer field should be populated from the table. However, if the customer value is empty (none), it should display as "None" or remain empty in the form. Currently, it is showing as '0'.

Could you please help me understand why this is happening and how to fix it?

Thank you!

14 REPLIES 14

In the table the field customer is type of integer and it does not have the default value 

Ankur Bawiskar
Tera Patron
Tera Patron

@NikhithaNikki 

please share more details along with screenshots what's not working

If my response helped please mark it correct and close the thread so that it benefits future readers.

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

NikhithaNikki
Tera Contributor

1. this is my field that I have created with select box.

NikhithaNikki_0-1751964471139.png

2. and doing dot walking from the table.

 

NikhithaNikki_1-1751964578511.png

 

3.This is field from the table of integer type

NikhithaNikki_2-1751964637511.png

 

 

4.These are choices. and no default value was there.

NikhithaNikki_3-1751964674086.png

 

 

5. THis is i am getting.

NikhithaNikki_4-1751964757042.png

 

 

I want to display as "none" when value was not there

 

The field Customer is type integer, but the values in a variable Customer are choices.

Please try to change the Customer (field) from Integer to String and observe if there is any change.
Because in this case even 1,2,3,4,5 are treated as text (string).

 

Let me know if it makes any change

———
/* If my response wasn’t a total disaster ↙️ drop a Kudos or Accept as Solution ↘️ Cheers! */


Eventually make the field choice as well, and add the choices 1:1, to avoid the mismatch between the data types:

string <> integer

string <> string

choice <> choice

———
/* If my response wasn’t a total disaster ↙️ drop a Kudos or Accept as Solution ↘️ Cheers! */