---
sourceDocument: Xanadu Platform Analytics
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/now-intelligence

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Platform Analytics

ft:clusterId :

    - par

bundleId :

    - par

workflow :

    - Platform


---

# Create relations between elements of one breakdown

# Create relations between elements of one breakdown {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read

Use a breakdown relation to set up navigation on an Analytics Hub between a hierarchy of
elements within the same breakdown. A field in the breakdown records must identify the
hierarchical relationship of one record to another.

## Before you begin

Review the use cases for breakdown relations in [Navigating breakdown elements with breakdown relations](https://servicenow-prod.fluidtopics.net/BKnEhWAoP~F0XeYB0dMlcA "Breakdown relations open a new navigation path for viewing breakdown scores, by moving from one breakdown element to another breakdown element. Breakdown relations can be between the elements of different breakdowns, or they can be within a hierarchical structure of elements in the same breakdown. Breakdown relations affect navigation on the Analytics Hub and in breakdown widgets.").  
Important:  
Platform Analytics features, such as KPI Details and data visualizations, do not support breakdown relations.

Role required: pa_data_collector, pa_power_user, admin  
Note:  
While a business analyst, typically with the pa_power_user role, is most likely to know what breakdown relations to create, creating them requires the knowledge and access to tables of a technical expert with pa_data_collector. A pa_admin is likely to understand both. Consider having either a pa_admin create the relation or have a collaboration between a pa_power_user and a pa_data_collector.

## About this task

You can create breakdown relations to navigate the
following hierarchical relationships between elements of a breakdown:

* Child relations, to navigate from a parent element to its children
* Parent relations, to navigate from a child element to its parents
* Sibling, or peer relations, to navigate between elements that share the same parent element

{#create-relation-btwn-bkdn-elements__ul_nzb_jh2_p2b}

In a breakdown with a hierarchical relationship between elements, one field in
the element record identifies the position of the element in the hierarchy.
Typically this field is Parent, and identifies the parent element. Elements that are
the parent of one element can themselves have a parent element, and you can navigate
this multi-level hierarchy in the Analytics Hub.

The example used in this topic is
the Location breakdown for the Number of open incidents indicator. A child relation
and a parent relation are needed to navigate the several levels of hierarchy, such
as from region to country to city and back.

Note:  
Breakdown relations are one-way relationships. Define multiple breakdown relations to create a bi-directional relationship.

## Procedure

1. Navigate to AllBreakdownsBreakdown Relations and click New.
2. In the Breakdown and Related breakdown fields, select the breakdown whose elements you want to navigate between.  
   These fields have the same value when you are creating a relation between elements of the same breakdown. For our example, select the Location breakdown in both fields.
3. In the Table field, select the same table as the breakdown source facts table.  
   In our example, select Location \[cmn_location\].
4. Fill in the rest of the form, depending on whether you are creating a child, a parent, or a sibling/peer relation.  
   {#create-relation-btwn-bkdn-elements__table_bkdwn-relations__entry__4}

   | Field | Child relation | Parent relation | Sibling/peer relation |
   |-|-|-|-|
   | Breakdown field | Select the field that identifies the parent element. For the Location breakdown, select Parent. | Select the unique identifier field for elements of this breakdown. For the Location breakdown, as for most breakdowns, select Sys ID | Select the unique identifier field for elements of this breakdown. For the Location breakdown, as for most breakdowns, select Sys ID |
   | Related breakdown field | Select the unique identifier field for elements of this breakdown. For the Location breakdown, as for most breakdowns, select Sys ID | Select the field that identifies the parent element. For the Location breakdown, select Parent. | Select the unique identifier field for elements of this breakdown. For the Location breakdown, as for most breakdowns, select Sys ID |
   | Common field | Leave empty. | Leave empty. | Select the field that identifies the parent element. For the Location breakdown, select Parent. |
   [Table 1. Breakdown Relation form]

   {#create-relation-btwn-bkdn-elements__table_bkdwn-relations}
5. Under Conditions, define any further conditions that a record must fulfill to appear as a related breakdown for this relationship.

## Result

After you submit the Breakdown Relation form, the navigation options are available in
the Analytics Hub for the relevant indicator. You do not need to run
a data collection job first.

## What to do next

View examples of breakdown relations that are shipped by default in every instance.
For the Location breakdown, the Child Location and
Parent Location breakdown relations are included. The
Sibling Group breakdown relation is an example of a
sibling or peer relation.

*[\>]: and then