Forum Discussion
Matrix Visual – Show All Child Issue Keys as Separate Rows Without Adding “Child Issue Key” to Rows
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.
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.
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.
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.
