Forum Discussion
How to treat Duplicate rows as Unique Rows
Hi,
I am relatively new to BI space, I looked through the posts but I coudn't find what I was looking for. I need a way to treat duplicate rows as unique values so that the visual is not grouped by or showing me the only unique values without including a EmpID column in the visual.
1. Here is my tableThe Emp table
2. The requirement is, I want to display all the columns except for EmpID and all the rows. However there are duplicate values in EmpFName & EmpLname and PowerBI shows only unique values. Notice that John A is a repeat value and I would like to see it repeated. But in the following visuals in 1st John A is aggregated acorss salary appears as one value, in the 2nd without aggregation(If I remove aggregation on the Salary), and the 3rd visual is the what I want.
Aggregation Applied on SalaryAggregation Not appliedbehavior I need
Any idea on how this could be acheived?
Thanks!
Hi, an easy wayis insert the ID Field and reduce his width to hide it.
Regards
Victor
Lima- Peru
4 Replies
- VvelardeCommunity Champion
Hi, an easy wayis insert the ID Field and reduce his width to hide it.
Regards
Victor
Lima- Peru
- BILearnerAdvocate I
Vvelarde Thanks for this solution/workaround, is there any other way to do it without including the ID column at all? because in the original data there are more number of Columns with bigger column headings and I am using column header word wrap to adjust the width of the columns to present data in the available space. So the problem with this solution is the width of header row increases significantly covering more area of the visual if I hide(Reduce the width of column to hide it) the ID column.
And if I do not use the word wrap for column headings then column heading would not be readable.Thanks,
- v-jiascu-msftMicrosoft Employee
Hi BILearner,
I am afraid adding another column is necessary. There is a message that "Duplicate rows were removed from the data" even I tried to use a R visual. That makes sense. Firstly, it's a report, which isn't just a list of records. Secondly, if there are hundreds of such rows, how we can handle them.
Best Regards!
Dale