Workplace Services - Location Full Name not Populating
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-23-2024 05:28 AM
On the base location table [cmn_location], the Full Name field is auto populated with a concatenation of all the parents in the entries hierarchy. All the location entries (Building, Floor, Room) are all saved as generic entries and a user can't necessarily tell what type of entry it is (unless it's named in an obvious way). This allows the name field to be "Room 23" but the full name to be "Building 145/Floor 2/Room 23", which is obviously a better final location value for the end user to see than just a vague "Room 23".
On the Workplace Service Delivery module, we have separate tables for Buildings, Floors, Areas, and Rooms (and others), all extending from a WSD Core Location table [sn_wsd_core_workplace_location] which itself extends the base Location table [cmn_location]. This table includes a Full Name field (inherited from Location), but it doesn't get auto populated with the parental hierarchy, simply a copy of the name field.
I know I can easily put in a script that would do the same work as the business rule that's running on the base Location table to accomplish this task, but I'm not sure why ServiceNow decided to not let that rule run on the WSD tables. It doesn't appear to disrupt the workings of the WSD functions that I can tell, and having a Name and a Full Name allows for better experiences for the end user. Does anyone know? Am I missing something about WSD where generating that Full Name will have a negative impact?
Thanks!
- Labels:
-
Architect
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-14-2025 01:03 AM - edited ‎05-14-2025 01:07 AM
Hello Travis,
Facing the same issue here with our costumer.
Did you solve it?
Seems though that we have the issue only if we create a location via Indoor Mapping.
Best regards,
Gautier