Additional Customer Information Fields

jared_wentzel
Kilo Contributor

What is the easiest way to populate additional incident form fields with information about the Customer selected? for example when creating an incident and selecting a customer I would like to populate a field (Customer Phone) with the customer selected's phone number. I would like to have a template setup so I can create additional fields using this method as well but I am stuggling...

1 ACCEPTED SOLUTION

Jim Coyne
Kilo Patron

As Avneet mentioned, you are probably better off adding the fields from the reference table.   This link shows you how - http://wiki.servicenow.com/index.php?title=Dot-Walking#Dot-walking_in_List_Collectors.   The data will be updated automatically for you whenever the reference field is changed.



Even better, teach your users they can just hover over the reference icon to see additional information related to the record - Reference Icon - ServiceNow Wiki.   This eliminates the need to add too many fields on a form.


View solution in original post

7 REPLIES 7

Wow... Dot walking... It was really that easy! I feel stupid now, I was going way out of my way to try to populate something from the sys_user table to a field on the Incident form so I could grab it in a notification


jared_wentzel
Kilo Contributor

On this topic, is there an easy way to view all the values for the fields listed when building notifications? There are so many to choose from and the navigation is still an enigma for me. If I could just see what each field is spitting out, it would make my life a lot easier.


Sometimes I think the easiest way is to add all the fields to your personal list view so you can see all the data - Creating Personal Lists - ServiceNow Wiki.   I suggest you do this temporarily in your Dev instance so you get used to what field contains what data and then you can reset the list view to the "Reset to column defaults" checkbox.



You can even add dot-walked fields in the same manner.   Just remember that it could end up being a lot of data.