Table Visual: Prevent Automatic Removal of Duplicates

[Anonymous]

I'm using a table visual in Power BI to attempt to show records with filtering capabilities using slicers. I'm finding that there seems to be some weird default behavior with the visual though that automatically removes duplicate records from the data set when they are shown in the visual. To test this behavior, I put together a basic dataset, shown here:

Data from the query editor

Note that lines 3 and 4 are duplicates and lines 5 and 6 are duplicates. This mimics my dataset.

When I view this using the Table visual, with no filters and all fields set to the "Don't Summarize" option, I see the following:

Has anyone else encountered this or found a workaround for this? Note that I don't want to show any other data fields in my table (i.e. an index) or summarize the data in anyway. Simply let my users view it exactly as it exists and filter using slicers. I found this on Stack Overflow, but it seems it did not get much attention there: https://stackoverflow.com/questions/49559137/power-bi-table-automatically-removing-duplicate-rows-er...

Thank you in advance for the help!

[v-lid-msft · Accepted solution]

Hi @Anonymous ,

Sorry for that, but based on my research,  it seems that this is by design that won't show the duplicate rows on Power BI. I also not found an effective solution to achieve your requirement except for add a externel field such as index,You can come up a new idea and add your comments there to make this feature coming sooner: https://ideas.powerbi.com/forums/265200-power-bi-ideas

Best regards,

Community Support Team _ Dong Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Anonymous]

Thank you for your response and confirmation about the table functionality. Appreciate the help @v-lid-msft !

[Anonymous]

HI @Anonymous ,

Please take a look at this post with similar issue.

https://community.powerbi.com/t5/Desktop/Duplicate-data-in-Table-visualization-Displaying-as-is-Data/td-p/32314

The workaround was to add an index column.

you can post your idea on the link.

Thanks,

Tejaswi