# Data Structure for Columnar Group View This document explains the process to dynamically convert a standard data structure to the data structure required to plot a columnar group view in the xViz Performance Flow visual

*Image 1: Column Group (Swim lane) View in xViz Performance Flow | Power BI*

{% hint style="success" %} **Prerequisite** - Before proceeding with this page, please go through the following pages to ensure a comprehensive understanding of the configurations required: * [Data Structure](/performance-management/configuring-the-chart-structure.md) * [Swim Lanes](/performance-management/configuring-the-chart-structure/grouping-swim-lanes.md) {% endhint %} Let’s explore this with an example. We have a dataset with specific IDs, but we don't have the Parent ID, Group ID, and Subtree ID included. However, we can easily create these columns in [Power Query](https://learn.microsoft.com/en-us/power-bi/transform-model/desktop-query-overview#power-query-editor) using a few transformation steps. {% hint style="success" %} Reference links have been provided next to each step for your convenience, allowing you to explore more about that specific transformation if you are encountering it for the first time. {% endhint %} ### Steps to dynamically convert your data for the Swimlane view: 1. We have a Source table with the columns Id, Title, Subtitle, and Group Name. The Group Name column represents the groups that we used for grouping to create swim lanes.

2. We sort the data by "Group Name" column to ensure that unique group names are arranged in the correct sequence.

*Image 3: Data sorted by the Group Name column*

{% hint style="info" %} Sort the Group Name column according to your requirements for preferred group order. This will ensure that the Subtree Id and Group Id are ordered according to the sorted column. {% endhint %} 3. Add an Index column starting from 1 - [Add an index column | Power Query](https://learn.microsoft.com/en-us/power-query/add-index-column)

4. Next, we will add the "Subtree Id" column - [Add a custom column | Power Query](https://learn.microsoft.com/en-us/power-query/add-custom-column#create-a-custom-column)\ Create a Custom Column - paste the code below as its definition and name the column as "Subtree Id": {% code overflow="wrap" %} ```powerquery let // Create a list of unique Group Name values UniqueGroupName = List.Distinct(#"Sorted Rows"[Group Name]), // Create a mapping table from Group Name values to numbers GroupNameMapping = List.Zip({UniqueGroupName, List.Transform({1..List.Count(UniqueGroupName)}, each _)}), // Convert mapping to a record GroupNameRecord = Record.FromList(List.Transform(GroupNameMapping, each _{1}), List.Transform(GroupNameMapping, each _{0})), // Lookup the Group Name number from the record GroupNameNumber = Record.Field(GroupNameRecord, [Group Name]), // Subtree ID SubtreeID = "G" & Text.From(GroupNameNumber), // if the current row is the first in its Group Name CurrentGroupName = [Group Name], CurrentIndex = [Index], PreviousRows = Table.SelectRows(#"Added Index", each [Group Name] = CurrentGroupName and [Index] < CurrentIndex), IsFirst = Table.RowCount(PreviousRows) = 0 in if IsFirst then SubtreeID else null ``` {% endcode %} {% hint style="danger" %} Make sure to replace the "Group Name" text in the above code with the name of the column you used for grouping. {% endhint %} This will result in a new column named "Subtree Id" is displayed in the image below:

5. Then, we will add the "Parent Id" column - [Add a custom column | Power Query](https://learn.microsoft.com/en-us/power-query/add-custom-column#create-a-custom-column)\ Create a Custom Column - paste the code below as its definition and name the column as "PId": {% code overflow="wrap" %} ```powerquery let // Get the Group Name and Index CurrentGroupName = [Group Name], CurrentIndex = [Index], // Filter previous rows with same Group Name PreviousRows = Table.SelectRows(#"Added Resident Id", each [Group Name] = CurrentGroupName and [Index] < CurrentIndex), // If there are previous rows, get the ID of the most recent one PreviousID = if Table.RowCount(PreviousRows) > 0 then PreviousRows{Table.RowCount(PreviousRows) - 1}[Id] else null in PreviousID ``` {% endcode %} {% hint style="danger" %} Make sure to replace the "Group Name" text in the above code with the name of the column you used for grouping. {% endhint %} This will result in a new column named "PId" is displayed in the image below:

6. Now, we will add the "Group Id" column- [Add a custom column | Power Query](https://learn.microsoft.com/en-us/power-query/add-custom-column#create-a-custom-column)\ Create a Custom Column. Then enter double quotes in the custom formula tab to create a blank column for now. Name this column as "Group Id":

This will result in a blank column named "Group Id" is displayed in the image below:

7. We will now perform basic transformations, such as changing data types and reordering columns, as shown in the image below:

8. Now, we will create a static table to define the groups in the visual. 1. Click on "Enter Data" in the Home tab of Power Query Editor and input the data - [Enter Data Directly | Power BI](https://learn.microsoft.com/en-us/power-bi/connect-data/desktop-enter-data-directly-into-desktop) 2. Enter the same values in both the Group Id and Id columns which we got in Subtree Id during transformation. 3. Now, add the Group Names to the Title column to create a suitable structure for swim lanes, leaving the remaining columns blank. {% hint style="info" %} * After entering the data, we will append both queries. Ensure that the structure and column names in the static table match those in the source table. * You can choose to maintain this table in any data source of your choice and connect to the report {% endhint %}

9. Finally, we will append the Static Groups table to the Source table - [Append Queries | Power Query](https://learn.microsoft.com/en-us/power-query/append-queries)

*Image 11: Appending Static Table to the Source Table*

Our data structure is now ready!

*Image 12: Data Structure suitable for Swim Lanes*

Finally, populate the data columns in the visual to display the data in swim lanes, as shown in the image below:

*Image 13: Column Group (Swim lane) View in xViz Performance Flow | Power BI*

{% hint style="danger" %} The transformation code blocks are suited to create simple groups and linear structures of nodes within groups as displayed in the last image. *If the parent node is in a group, the child node will automatically be included in the same group and displayed below the parent node. To position nodes side by side within a group, skip adding Parent ID but provide the Subtree ID for both nodes.* {% endhint %} ### Sample Report File - Columnar Group View {% file src="/files/bNHppntBjVFvEL28SakV" %} {% hint style="success" %} This example is inspired by common, real-life dataset structures. Your source data structure may vary and may require additional data transformations to align with this example. {% endhint %} > Refer to the documentation link below for details on the group structure, which allows multiple nodes to be displayed side by side within a single group - [Data Structure for Wide Group Views](/performance-management/configuring-the-chart-structure/grouping-swim-lanes/data-structure-for-wide-group-views.md) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.xviz.com/performance-management/configuring-the-chart-structure/grouping-swim-lanes/data-structure-for-columnar-group-view.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.