Create a breakdown-to-breakdown relation

To set up navigation in a visualization between the elements of two breakdowns at the same level, create a breakdown relation between the breakdowns. A table must exist with fields that reference the records for both breakdowns.

Before you begin

Review the use cases for breakdown relations in Navigating breakdown elements with breakdown relations.

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 want to be able to navigate quickly between two breakdowns at the same level that are logically related.

Note:

Breakdown relations are one-way relationships. To create a bi-directional relationship, define multiple breakdown relations.

Procedure

1. Navigate to All > Breakdowns > Breakdown Relations and tap New.
2. Fill in the fields on the form, as follows.

   Table 1. Breakdown Relation form

   Field	Description	Example
   Breakdown	Select the breakdown that this relationship belongs to. You can access related breakdowns from this breakdown only.	If you want a selection of group members to appear when you select an Assignment Group, the Breakdown is Assignment Group.
   Related breakdown	Select the breakdown you want to associate with the first breakdown.	If you want a selection of group members to appear when you select an Assignment Group, the related breakdown with the Assignment Group members is Assigned To.
   Table	Select a table with fields that reference the facts table records of the sources of both breakdowns. For many-to-many relationships, select a many-to-many table. For one-to-many relationships, select a facts table.	The Assignment Group breakdown uses Group data. The Assigned To breakdown uses User data. Assignment Groups can have many members, and a user can be a member of more than one Assignment Group, so they have a many-to-many relationship. Therefore, you select the Group Member [sys_user_grmember] table, which is a many-to-many table that joins groups and users.
   Breakdown field	Select the field from the specified table that identifies the breakdown element you can navigate from.	To relate Assignment Group and Assigned To, select the Group field. This field in the Group Member [sys_user_grmember] table identifies the element of the Assignment Group breakdown.
   Related breakdown field	Select the field from the specified table that identifies the breakdown elements you can navigate to when viewing this relation.	To relate Assignment Group and Assigned To, select the User field. This field in the Group Member [sys_user_grmember] table identifies the element of the Assigned To breakdown.
   Common field	Leave this field empty when defining a relation between breakdowns.
   Conditions	Define any further conditions that a record must fulfill to appear as a related breakdown for this relationship.	Add the condition [User.Active] [is] [true] to filter out inactive group members.

What to do next

View examples of breakdown relations that are shipped by default in every instance. The example shown here is the Members breakdown relation. The Member of breakdown relation provides navigation in the reverse direction, starting with an element in Assigned To and navigating to an Assignment Group. Lastly, the Manager breakdown relation is similar to Members, but because each assignment group has only one manager, it shows a many-to-one relationship. It thus uses a facts table instead of a many-to-many table.

Related tasks

• Create an Indicator Scorecard
• Create or add a filter on an inline dashboard