Organize Views using Hierarchical Views
Overview
What are Hierarchical Views?
Hierarchical Views (HV) organize Views into a parent-child structure. In this hierarchy, a View can contain other Views — called child Views — which can themselves have additional children, forming a nested structure.
A View that contains child Views is called a View Group. Its filter condition is automatically inherited from its children, representing the union of all their filter statements. This means you can manage a View Group’s logic simply by adding or removing child Views—no manual editing of filter criteria required.
In addition to simplifying filtering, the hierarchical structure of an HV also streamlines user access management. When a user is assigned to a View Group, they automatically gain access to all of its child Views—and any descendants further down the hierarchy.
Hierarchical Views are automatically generated from a Hierarchical Business Mapping (HBM), saving time and reducing manual setup. Each value in the mapping file becomes a View, and the file defines how Views roll up into View Groups. Once created, the HV structure stays in sync and is automatically updated whenever the HBM changes.
Setting up Hierarchical Views
Create a Hierarchical View
- Navigate to Organize > Views.
- Select New Hierarchical View. The New Hierarchical View dialog opens.
- Select a Hierarchical Business Mapping to be used for defining the views in the hierarchy.
- Click Add to create the view hierarchy.
This will automatically create views matching the HBM definition. This may take a few minutes to complete.
Manage Hierarchical Views
Edit and share views within the hierarchy, or delete the entire hierarchy.
You cannot edit the filter conditions of views within a Hierarchical View (HV), nor can you delete individual Views. Both the views and their filter conditions are controlled by the Hierarchical Business Mapping (HBM) associated with the HV.
Changing the privacy permissions of the entire Hierarchical View
Views authors can change the permissions (increase or decrease) of the view hierarchy. Here's how:
- Navigate to Organize > Views.
- Click the ellipsis (…) icon on the row of the HV root node and select Edit.
The Edit Hierarchical View Group panel is displayed.
-
Change the permission between ‘Entire Organization’ and ‘Individuals’.
Note:Changing the privacy mode to Entire Organization, when Saved, will remove all existing user sharing assignments for all nodes in the hierarchy. Proceed with caution.
Editing a View
Users with view access can edit the sharing for a View. Here's how:
- Navigate to Organize > Views.
- Click the ellipsis (…) icon on the row of the view you want to edit and select Edit.
The Edit Hierarchical View Group panel is displayed.
-
-
Select the Individuals to share your view with specific users. Use the Shared With dropdown to select specific users to share the View with.
Note:When users are assigned a view, they automatically inherit access to all child views well. You can see users who have inherited access to the current view in the Inherited View Permission section.
When assigned, users can not see any data until they have the ViewsFeatureFullAccess permission. For more information, visit Managing user permissions and roles =
-
Deleting a Hierarchical View
To delete a hierarchical view, follow the steps below:
- Navigate to Organize > Views.
- Click the ellipsis next to the root node and select Delete
- Confirm that you wish to delete the imported View Group.Note:
You cannot delete individual Views within a Hierarchical View (HV); only the root node can be deleted, and only by a user who has access to the root node.
However, the root node cannot be deleted if any of its child Views are shared with other users. To proceed with deletion, you must first remove all user access to the entire HV.
To remove all sharing access:
- Edit the root node and set its sharing mode to Entire Organization, then click Save.
- Re-edit the root node and change the sharing mode back to Individuals, then Save again.
This process should clear all existing user access, allowing you to delete the root node.