Matrix Visual – Show All Child Issue Keys as Separate Rows Without Adding “Child Issue Key” to Rows

[p1410]

Hi,

I’m working on a Power BI Matrix visual with the following setup:

• Rows: Category -> Parent Issue Key

• Columns: Version 

• Values: A measure ( cap ) that retrieves issue keys based on some conditions.

Currently, when I include Child Issue Key in the Rows, I can see all individual child issues under each parent (like in my second visual).
However, when I remove Child Issue Key from the Rows, Power BI only displays one child issue key per parent, instead of showing each child as a separate row (like I’d prefer in my third visual).

Here’s my current measure:

cap =
VAR IssueGK =
CALCULATE(
MIN('Fact Table'[Issue_GK]),
'Dim Issue'[Issue Type] = "xyz"
)
RETURN
CALCULATE(
VALUES('Dim Jira Issue'[Child Issue Key]),
'Dim Issue'[Issue_GK] = IssueGK
)

My goal:
I want the Matrix to display all child issue keys as separate rows under each parent, without having to explicitly place “Child Issue Key” in the Rows area.

I’ve tried using VALUES, CONCATENATEX, and even calculated tables, but so far either I get one concatenated cell or only one issue key per parent.

Has anyone achieved this type of setup?
Is there a DAX or data model approach that can make the Matrix automatically expand to show all child rows without adding the field to the Rows section?

Thanks in advance!

(Here is the screenshot - first one with counts, second one with Child Issue Key in Rows, and third one showing my desired layout.)

[Angith_Nair · Accepted solution]

Hi @p1410 ,

This cannot be achieved as there is no direct relationship between the two dimension tables. If you choose not to display the Child Issue Key in the rows, no filter context will be applied to the measure, since it relies on the MIN aggregation function for evaluation.

As a workaround, you can hide the column by first turning off Text Wrap for the Child Issue Key column and then reducing its column width. This way, the end user will not notice whether the column is included in the matrix or not.

[Shubham_rai955 · Accepted solution]

In Power BI’s Matrix visual, showing all child issue keys as separate rows without adding “Child Issue Key” directly to Rows is not possible with standard Matrix behavior. The Matrix needs a field in Rows to split data properly.

Possible Approaches:

• Power BI requires a field (like "Child Issue Key") in Rows to expand and show each child separately.

• Using DAX (such as VALUES or CONCATENATEX) inside measures will return values in a single cell (either first value or a concatenated string), but cannot force visual expansion into separate rows.

• To display each child issue on its own row, you must include “Child Issue Key” in the Rows section. That is how Matrix visual dynamically creates rows per child.

• For advanced layouts not supported by Matrix, consider the Table visual, which displays each row individually.

[p1410]

I believe these are some limitations of matrix visual which i have encountered, anyways i've implemented it this way - hiding the Child Issue Key column by disabling text wrap and reducing the column width.

Thank you for looking into this.

[v-ssriganesh]

Hi @p1410,

Thank you for posting your query in the Microsoft Fabric Community Forum, and thanks to @Zanqueta & @Angith_Nair for sharing valuable insights.

Could you please confirm if your query has been resolved by the provided solutions? This would be helpful for other members who may encounter similar issues.

Thank you for being part of the Microsoft Fabric Community.

[Angith_Nair · Accepted solution]

Hi @p1410 ,

This cannot be achieved as there is no direct relationship between the two dimension tables. If you choose not to display the Child Issue Key in the rows, no filter context will be applied to the measure, since it relies on the MIN aggregation function for evaluation.

As a workaround, you can hide the column by first turning off Text Wrap for the Child Issue Key column and then reducing its column width. This way, the end user will not notice whether the column is included in the matrix or not.

[p1410]

Thanks for the reply.
This workaround is actually the same approach I’ve already implemented. I just wanted to check if there were any alternative solutions beyond this method.
Thanks again for looking into it.

[Ashish_Mathur]

Hi,

Share the download link of the PBI file.

[Zanqueta]

Hello @p1410,

To display all child issue keys in a single cell, use CONCATENATEX to aggregate them as a comma-separated list

try it:

cap =
VAR IssueGK =
CALCULATE(
    MIN('Fact Table'[Issue_GK]),
    'Dim Issue'[Issue Type] = "xyz"
)
RETURN
CALCULATE(
    CONCATENATEX(
        VALUES('Dim Jira Issue'[Child Issue Key]),
        'Dim Jira Issue'[Child Issue Key],
        ", "
    ),
    'Dim Issue'[Issue_GK] = IssueGK
)

If this response resolved your issue, please mark it as correct to assist other members of the community.

[p1410]

Hi @Zanqueta , 

Thank you for the reply!

I want to show all the child issue keys in separate rows and i dont want to concatenate and display in a single cell. 

Let me know if you have any solution to show all the child issue keys in separate row.

[Zanqueta]

Hi @p1410, thank you for feedback.

I'm thinking to achieve the desired behaviour for viable approache, maybe you can try restructure the model using a Parent - Child supporting table

Create a calculated table that defines the relationship between Parent and Child Issue Keys, and use this table as the basis for your visual:

ParentChildTable =
SELECTCOLUMNS(
    'Dim Jira Issue',
    "Parent Issue Key", 'Dim Jira Issue'[Parent Issue Key],
    "Child Issue Key", 'Dim Jira Issue'[Child Issue Key],
    "Version", 'Dim Jira Issue'[Version]
)

Then, in the matrix visual:

• Place Parent Issue Key and Child Issue Key in the Rows.
• Place Version in the Columns.
• Add the desired measure to the Values.

Let me know if ir worked.

✅ If this response resolved your issue, please mark it as correct to assist other members of the community.