cmn_location - where is the field descriptions on the ServiceNow product website?

SB87
Tera Expert

Hi,

Surely there is documentation on the Servicenow website that provides a field-by-field description of each cmn_location field? (some of them are self-explanatory, but others are not).

I've been searching but am unable to locate. Can anyone help? Thanks in advance.

 

Column Name:Description???Label
city City
cmn_location_source Location source
cmn_location_type Location type
company Company
contact Contact
coordinates_retrieved_on Coordinates retrieved on
country Country
duplicate Duplicate
fax_phone Fax phone
full_name Full name
latitude Latitude
lat_long_error Lat long error
life_cycle_stage Life Cycle Stage
life_cycle_stage_status Life Cycle Stage Status
longitude Longitude
managed_by_group Managed by group
name Name
parent Parent
phone Phone
phone_territory Phone territory
primary_location Primary location
state State / Province
stock_room Stock room
street Street
sys_created_by Created by
sys_created_on Created
sys_id Sys ID
sys_mod_count Updates
sys_updated_by Updated by
sys_updated_on Updated
time_zone Time zone
zip Zip / Postal Code
sys_domain Domain
sys_domain_path Domain Path
primary Primary
consumer Consumer
managed_domain Managed domain
account Account
type Type
3 REPLIES 3

G24
Kilo Sage

Agree.  Where are these field descriptions? 

Stefan_Garcia
Tera Contributor

Well I'll chime in because I was looking for the same thing and couldn't find it.

 

Consumer - reference to csm_consumer table, used for CSM, visible in Case view

Primary Location - controlled by UI policy and only visible when duplicate is checked

Primary - controlled by UI policies and only visible when Consumer is populated

Full Name - system generated field, built from location hierarchy

bkopitzke
Tera Contributor

Any update on this?  Description of the fields that are OOB from ServiceNow ensure the fields are not misused.  In this case I'm looking for specifically for Locations but I do have the need for other tables too.  Again - helps so it is clear on what the purpose of a field is for so it doesn't get repurposed or filled in incorrectly and cause issues in other configurations.