Flexible Hierarchies Overview
Flexible Hierarchies provide a dynamic way to visualize, manage, and analyze complex business relationships. Get to know the key elements of Flexible Hierarchies.
Required Editions
Available in: Lightning Experience Available in: Unlimited and Agentforce Editions |
Hierarchy Types
A hierarchy type defines a structural schema for your data. Define this schema first, as it provides the framework to create a hierarchy.
Here are the key components of a hierarchy type.
- Nodes: In Flexible Hierarchy, a node is a virtual representation of business data and the building block of your structure. You define a node by selecting an object, such as Account, from a predefined set of objects. The node is a decoupled entity without a real-time connection to the underlying Salesforce record.
- Display Fields: Show the specific object fields visible to users in both the Graph and Grid views. For each node, select the fields that provide the most relevant data for analysis within the interface. These fields make sure that users see consistent, actionable information across all visualization perspectives.
- Node relationship Definitions: Establish the rules that determine how nodes at one level connect to the immediate next level (parent — child, descendants). To define a relation, specify a parent and child object. Optionally, you can reference the junction object used in the underlying business data. For example, in an account hierarchy, a Parent Account (parent) connects to a Child Account (child). If accounts are linked through an Account-Account Relation record, you can reference that as the junction object.
Hierarchy types provide secure, relevant business views by focusing on required business data and excluding unrelated data. It simplifies the hierarchy creation process by abstracting the complexity of the underlying data schema away from hierarchy managers.
Flexible Hierarchies
An instance of your data mapped to the structural logic of a specific hierarchy type. While the type provides the underlying schema or lens, the flexible hierarchy serves as the actual representation of your records at a precise point in time. This distinction helps you to transform static data models into dynamic, historical, or future-state visualizations of your organization.
To create a flexible hierarchy, specify:
- Reference hierarchy type: The pre-configured structural schema that includes nodes and node relationship definitions.
- Root object and record: The specific starting point of the flexible hierarchy.
- Effective dates: The to and from dates that define the period during which a flexible hierarchy is applicable.
- Source system identifier: A unique ID that maps the record to an external system, such as a core banking system, ensuring data alignment across your enterprise.
Flexible Hierarchies transform static records into dynamic structures that reflect the real-world complexity of business relationships. Here are a few advantages of flexible hierarchies.
- Streamlined External Integration: Maintain a digital thread between your external systems of record by using a Source System Identifier. This unique mapping makes sure that your hierarchies are in sync with external systems, eliminating data silos across the enterprise.
- Root-Based Perspective: Create diverse flexible hierarchies from a single hierarchy type by selecting specific root objects and records. This flexibility helps a relationship manager to set a Regional Subsidiary as the root for a local tactical view, or a Parent Global Organization for a global strategic account plan.
- Multi-System Context: Achieve cross-object flexibility by specifying a root record object. This capability makes sure that you aren’t limited to standard hierarchy structures, instead, you can initiate hierarchies from custom objects or any allowlisted object. By supporting a diverse range of starting points, the framework provides a comprehensive, 360-degree view of your business relationships across different data domains.
Explore the different ways to visualize and manage flexible hierarchies in the hierarchy builder.
Related Contacts in Graph View
Configure a hierarchy type to show all direct and indirect contacts for an account node directly in the hierarchy graph view. This centralized view helps your sales and service teams understand relationship dynamics and identify who influences each account without navigating multiple records.
The feature uses Account Contact Relationship (ACR) records to determine which contacts to show for an account node, categorizing based on their association.
- A direct contact has a primary relationship with the account.
- An indirect contact is primarily associated with another account, but can influence this relationship.
If your org doesn't use the Multiple Contacts to Account feature, the account ID field on the contact record is used to retrieve and list direct contacts.
