Facilities location hierarchy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-10-2018 07:51 AM
I'm in the process of manually creating campus, building, floor and space information through the facilities application to see what I would need to set it up for asset tracking. I'm running into an issue where I don't see a nested, parent/child view of my locations like we do in the demo for the ServiceNow San Diego campus. It doesn't have the hierarchy.
For example, I created the building > levels > space but the records show as a flat list and not like the demo data. What would I need to do so my manual records are show up like the image below when selecting a location?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-15-2024 12:19 PM
cmn_location points to a cmn_location_type choice list. The list contains 12 oob options for use in this order
When you create a cmn_building, there is a reference cmn_location. This creates the Parent->Child architecture using table relationships. I can't say the same for Campus, although I assume it is the same! When organizations install Workplace Service Delivery/Facilities there are field mappings that leverage cmn_location, cmn_building, intsalls cmn_campus (i think) and a few WSD/Facilities tables (sn_wsd_indoor_mapping) etc.
If you are creating those tables in the Facilities application, I don't believe you will ever make the "parent<->child" relationship. You have to make edits on the cmn_location table and link them to the facilities app.