Duplicate data in Table visualization - Displaying as is Data

[Abhaykumar]

I want ot display a table from SQL server as is in PowerBI Table visualization. However, PowerBI seems to remove the duplicates from the table when charted.

Table in Query Editor with duplicates :

When the table is displayed as 'Table' visualization:

Is there a way to change this behaviour and d

[Vishnu97]

I'm facing issue like I need to load the table which should have 500 rows out of that 300 rows will be duplicated. 

But currently in table visual view, it is pulling only the unique rows which is 200 rows in my case. But i wanted to include all the 500 rows eventhough it have duplicates. can you help me with the ways to fix this ?

[AhmedMahmoud]

I can't believe that we are in 2023 and this problem is not solved from 2016.

Power BI is a powerful software and developers till now cant solve a simple issue 

What a waste of time surfing the internet to find a solution of a simple problem like this one for hours.

[Vishnu97]

Have you find any solution for this issue. If so, please let me know.

[Anonymous]

@Abhaykumar @v-qiuyu-msft @Greg_Deckler 

Are there any updates/progress on the above mentioned issue? 

Thanks, 
Jash. 

[laxminarayana]

Hi,

@Abhaykumar @v-qiuyu-msft @Greg_Deckler

I'm also facing the similar issue, Is there any solution/update on this?

Thank you

[Anonymous]

As far as i can see there isn't. It's crazy that this is such a basic thing and cannot be done. Also i don't agree with the point "this is by design". The user should have ultimate control over whether the data is showed "as-is" or being aggregated in any way. So in the worst case, there MUST be a mechanism allowed to turn this off and allow duplicates in the table visual to show. Unreal!

[S_Sanchez]

@Anonymous well said, and this is unfortunately a thought that comes to mind every day I work with Power BI.  However, it is still a great tool, it's just frustrating to see some of these seemingly easy-to-fix issues remain unsolved as time goes on.

[Anonymous]

I really need to de-aggregate duplicate values in the table viz and see all entries. 

Is there any update on this??

[Anonymous]

I'm also having this problem.  We are trying to dig into financial details and want to be able to see which payments are duplicated (and thus erroneous), but the Power BI Desktop table doesn't show duplicates, it shows each unique row only.  I get that this is an aggregate tool, but it seems like the table should have a property that allows you to show distinct or show raw.

[Sean]

You can show a count of each code for each date? Would that work?

[Abhaykumar]

Thanks @Sean for your reply. This is a work around that I am using right now. However, it is baffling that i cannot display data as is. I wanted to explore if there is any way to turn auto-unduplication off.

[Greg_Deckler · Accepted solution]

@Abhaykumar - You could also add an Index column to your query on import so that you have a unique number. Power BI is first and foremost a data aggregation and visualization tool, it sort of assumes you want to DO something with the data, not just display it raw.

That being said, surprisingly, I have not see this posted in Ideas, so I would recommend that you submit it and post the link back here so we can vote for it.

[Abhaykumar]

Thanks @Greg_Deckler. I have posted the idea here

[v-qiuyu-msft]

Hi @Abhaykumar,

I also have reported this issue internally, will keep you update once I get any information.

Thanks for your question.

Best Regards,
Qiuyun Yu

[SorrowsofGoethe]

Any update?

[Greg_Deckler]

Thanks @v-qiuyu-msft, I have also noticed this behavior with the R visual implementation in the default data set that it creates and there is no way to "undo" it other than to have the R script reference the source information and essentially create a new data set. I have posted this in Ideas to allow one to turn off removing duplicates in the default R visual data set that is created or at the very least allow us to create a data set using the same syntax as shown in the comments so that we can at the very least create our new, non-dedupped data set from the data in our data model instead of having to go back to the source.