@sayan-ghosh ,
Great question — this is a common scenario when working with location hierarchies in ServiceNow.
OOTB Reporting Limitations:
The standard reporting tool in ServiceNow doesn’t support recursive dot-walking through multiple levels of a hierarchical field like location.parent directly in a single filter. So, as you noticed, filtering on location.parent only checks one level up.
Recommended Approach:
Use a Scripted Filter or Business Rule to Flatten the Hierarchy:
Create a new field (for example, a custom field called top_level_location or location_path) on the Incident table that stores the full path of locations or the ultimate parent location.
You can populate this field via a Business Rule or Script Include that runs when an incident is created or updated, walking up the location hierarchy until the top parent is found.
Then you can easily filter your reports on that field (e.g., top_level_location = Location A), which will include all incidents from child locations as well.
Use a Scripted Report Source:
If you want to keep everything dynamic, you can write a Scripted Report Source where you query the cmn_location table recursively to get all child location IDs of the selected parent.
Then filter incidents with location IN (all child location IDs + parent location ID) in that scripted source.
Your report uses this Scripted Report Source.
Use Database Views or Performance Analytics (if applicable):
