Flexible Hierarchies Data Model
The Flexible Hierarchies data model includes Flexible Hierarchy and related objects to create and manage hierarchies according to your business requirements.
Required Editions
Available in: Lightning Experience Available in: Unlimited and Agentforce Editions |
Flexible hierarchies provide a visualization layer for your Salesforce data. Unlike standard hierarchies that require lookup or master-detail relationships, you can group and visualize records even if they aren't connected in the schema.
Define your hierarchy by the nodes that you add. You can structure your hierarchy based on your business logic rather than your Salesforce data model. To provide this flexibility, the system uses a dedicated wrapper data model that manages your hierarchy structure without altering your Salesforce object records.
Review these objects of the Flexible Hierarchies data model. Organizations can configure their systems to insert flexible hierarchy-related details into the Flexible Hierarchy and related object records.
| Object | Description |
|---|---|
Name: Flexible Hierarchy API Name: FlexibleHierarchy |
Represents the hierarchy. This record defines your entire hierarchy. Use this object to name your hierarchy, identify its unique root node, and manage its status. |
Name: Flexible Hierarchy Node API Name: FlexibleHierarchyNode |
Represents a single point in your hierarchy that points to a specific Salesforce record. For example, one node can point to an account, while the node next to it points to a contact or a case. Because the node doesn't alter the underlying Salesforce record, the same account can exist in multiple hierarchies simultaneously. User access to the underlying records is enforced when viewing hierarchies. If a user doesn't have access to an underlying record, its details don't appear in the grid or graph views. These views also enforce field-level security for the underlying fields. |
Name: Flexible Hierarchy Node Relationship API Name: FlexibleHierarchyNodeRela |
Define how nodes relate to one another to represent your hierarchy structure. You can:
|
Name: Flexible Hierarchy Node Summary API Name: FlexHierNodeSummary |
Represents rollup data for a hierarchy node, including direct, child, and total aggregate values. |
Name: Flexible Hierarchy Validation Job Run API Name: FlexHierVldJobRun |
Represents an execution instance of a hierarchy validation job that includes validation requests for one or more hierarchies. |
Name: Flexible Hierarchy Validation Job Run Item API Name: FlexHierVldJobRunItm |
Represents the execution status and results for a specific hierarchy processed in a validation job. |
Visualize Disconnected Data
Place separate objects in a hierarchy, such as object A and object B, in the same visual tree even if no relationship or junction object connects them. With flexible hierarchies, you can create a relationship for your business views without modifying your data schema.
Visualize Connected Data
Even when records are connected, such as accounts and contacts by using Contacts to Multiple Accounts, you can select which relationships to show. Use flexible hierarchies to provide a focused workspace that filters irrelevant data. For example, if an account has 50 contacts, create a legal hierarchy that includes only the 5 legal contacts, and build a separate service hierarchy that includes only the service contacts.
