Validation Errors for Hierarchies
Review common validation errors encountered when validating a hierarchy. Learn about the root causes and recommended resolution steps to ensure structural integrity.
Required Editions
Available in: Lightning Experience Available in: Unlimited and Agentforce Editions |
When you validate a hierarchy, the system runs an integrity check to ensure that the structure is sound. If the validation fails, you’ll receive an error code. Use this guide to understand why the error occurred and how to resolve it.
Root Node Errors
Root node errors indicate that the hierarchy lacks a single starting point or the referred root node is invalid. A hierarchy must have exactly one root node.
| Error Message | Description | Recommended Action |
|---|---|---|
| VE10: Invalid root record ID for the specified node. [Node(s): {0}] | The root record ID exceeds 18 characters. | Specify a valid ID for the root record and try again. |
| VE11: Root record ID invalid for the root object. [Node(s): {0}] | The specified record ID doesn't match the defined root object. For example, the hierarchy is configured for an Account root object, but you provided a contact record ID. | Specify a valid ID and try again. |
| VE12: Root node cannot have a predecessor node. [Node(s): {0}] | When a root node is assigned as a parent or predecessor. Because a hierarchy must start from a single point, the root node can’t have nodes preceding it. | Remove the predecessor nodes or select a different root node. |
| VE13: We couldn't find a record with the specified root record ID. [Node(s): NA] | The specified root record ID doesn't exist. | Specify a valid root record ID and try again. |
Structure and Relationship Errors
These errors indicate that the "branches" of your hierarchy are logically broken or looped.
| Code | Error Message Summary | Recommended Action |
|---|---|---|
| VE1: One or more nodes have more than one predecessor. [Node(s): {0}] | A node is assigned to multiple parents. For example, you assigned both node A and node B as parents of node C. In a flexible hierarchy, a child node must have exactly one parent. | Specify only one predecessor node for each node, and try again. |
| VE2: Nodes occur more than once. [Node(s): {0}] | A single record is added to the hierarchy multiple times. For example, the hierarchy includes nodes A, B, and C, but node C is listed twice. Each record must be a unique entry. | Specify each node only once and try again. |
| VE3: One or more nodes have duplicate relations. [Node(s): {0}] | A parent-child relation is defined more than once in a hierarchy. For example, the relationship from node A to node B appears twice. | Specify each node relation only once and try again. |
| VE7: Relation between nodes creates a loop. [Node(s): {0}, {1}] | A circular reference is detected. For example, node A is the parent of node B, and node B is the parent of node A. | Remove the node relation and try again. |
| VE8: One or more nodes don’t have a predecessor node. [Node(s): {0}] | Orphaned nodes are detected. Every node except the root node must link to a parent. For example, nodes A and B are included in the hierarchy but have no assigned parents. | Specify valid predecessor nodes and try again. |
Data Integrity and Record ID Errors
| Code | Error Message Summary | Recommended Solution |
|---|---|---|
| VE4: Reference record IDs of one or more nodes are not found. [Node(s): {0}] | The specified reference record doesn't exist. | Specify valid reference record IDs and try again. |
| VE5: Reference record IDs of one or more nodes are invalid for the hierarchy type {hierarchy type name}. [Node(s): NA] | The specified record belongs to an object that is not defined in the hierarchy type configuration. For example, you added a contact record, but the Contact object is not included in the hierarchy type. | Specify valid reference record IDs and try again |
| VE6: Reference record IDs of one or more nodes invalid for relevant reference objects. [Node(s): {0}] | The specified record ID doesn’t match the node’s object type. For example, you defined the node object as Account but provided a contact ID. | Specify valid reference record IDs and try again |
| VE9: One or more nodes have invalid reference record IDs. [Node(s): {0}] | The node record ID exceeds 18 characters. | Specify valid reference record IDs and try again. |
Did this article solve your issue?
Let us know so we can improve!
