The quick answer
In a Location dataset, open the related Subsidiary fields and add Full Name if your account exposes it. Compare the result with the Subsidiaries list: Full Name may contain a parent-to-child path, a short name, or may be unavailable. Add a separate Subsidiary criterion to limit the actual locations; the filter does not match text in the displayed path.
The screenshots use sample data. Person and operating-company names are fictional. Field availability and visible records depend on the account and role.
Before you start
You need OneWorld, access to Analytics/Datasets, and permission to see the relevant Locations, Subsidiaries, relationships, and fields. Role, subsidiary, record, and inactive-status restrictions can narrow the visible rows. This example uses a Location dataset, not a workbook, and leaves the dataset unsaved. A role's results may be narrower than the account's full inventory.
01. Inspect the account hierarchy
Open the Subsidiaries list through Setup or page search. Find a parent and child that your role can view, then note how the hierarchy is displayed. Here North America is the parent of Canada and United States. Check that you can also see the relevant Location records.
02. Add a related field
Open Analytics > Datasets > New Dataset and select Location as the root record. If Location is unavailable, check feature and record access. The initial grid includes Name and Subsidiary in this account.
Expand the related Subsidiary record in the field tree, if the relationship is exposed to your role. If Full Name is available, add it to the data grid using the field control or drag action. Compare its values with the hierarchy you inspected. In this account it shows paths such as North America : United States. If the relationship or Full Name field is absent, or it gives only a short name, this method has not established a hierarchy path in your account.
03. Filter and verify locations
Add Subsidiary to the criteria area. Choose is any of, or the equivalent multi-value operator shown, and select the exact values Canada and United States. Inspect whether the filter offers an option to include child subsidiaries; choosing a parent does not necessarily include descendants.
Apply the criterion. Confirm that locations outside the chosen subsidiaries disappear and qualifying, role-visible locations remain. The filtered grid here shows the North America paths beside those locations. Leave the dataset unsaved for this investigation; saving a reusable dataset can follow after the field and filter behavior are validated.
Check the result
- The displayed Full Name paths are consistent with the Subsidiaries list.
- The criteria summary names the selected subsidiaries.
- Only matching, role-visible Location rows remain.
Common questions
What if Subsidiary Full Name is missing?
The related Subsidiary relationship or its Full Name field may be unavailable to this account or role. Another available field may identify the subsidiary, but a short name does not establish a full parent path. Check the Subsidiaries list separately.
Does selecting a parent subsidiary include its children?
Do not assume it does. Test a known child location. Select each required subsidiary explicitly or use an available child-inclusion option only after checking its behavior.
Does the filter search the displayed hierarchy text?
No. The Subsidiary criterion evaluates the Location's associated subsidiary. Full Name is a display field. Changing its text representation does not change which locations the criterion matches.
Why is a Location missing from the result?
Check the unfiltered dataset first, then the criterion. Role and subsidiary restrictions, inactive records, and unavailable relationships or fields can limit what appears. A missing row alone does not prove that the Location has no subsidiary.
Will another role see the same locations?
Not necessarily. Validate the dataset under the intended role because Analytics respects its record, field, and subsidiary access.