Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.

Reply
Fyousif92
Frequent Visitor

Graph Values Keep Doubling on Refresh – Possible Data Duplication or DAX Issue

Hi Power BI Community,

I’ve created a diversity dashboard, and I’m running into a strange issue: some of the values in my charts (e.g., bar charts) keep doubling seemingly at random. This happens sometimes in Power BI Desktop, and also after I publish the report to the Power BI Service.

A few things I’ve noticed:

  • The values appear to multiply (double, triple, etc.) as if data is being duplicated during refresh or interaction.

  • I’m using a mix of Power Query transformations and DAX measures.

  • No use of volatile functions like RAND() or NOW().

  • The issue is intermittent – not every refresh causes it, but it happens enough to be a problem.

  • I’ve checked the relationships, disabled Auto Date/Time, and I’m not intentionally appending data.

What I’d appreciate help with:

  • What could cause this kind of behavior where data looks compounded after refresh?

  • Could it be related to Power Query logic, like reappending the same dataset unintentionally?

  • Any best practices to debug step-by-step whether it’s from the ETL steps or a logic issue in DAX?

I’d be happy to share snippets of my M code, measures, or screenshots. Thanks so much!

2 ACCEPTED SOLUTIONS
Akash_Varuna
Super User
Super User

Hi @Fyousif92 This issue might stem from unintentional data duplication in Power Query or incorrect DAX aggregations. Check Power Query steps for accidental appends and validate relationships to avoid many-to-many joins. Review DAX measures for unnecessary iterations or summations.

View solution in original post

danextian
Super User
Super User

 

hi @Fyousif92 

If this behavior occurs in M, it's most likely due to a merge operation where multiple rows from the right table match each row on the left. As a result, the left-side rows are duplicated based on the number of matching rows.

If it happens in DAX, it's more difficult to diagnose without examining the specific measures (including any referenced ones) and the structure or contents of the tables involved.





Dane Belarmino | Microsoft MVP | Proud to be a Super User!

Did I answer your question? Mark my post as a solution!


"Tell me and I’ll forget; show me and I may remember; involve me and I’ll understand."
Need Power BI consultation, get in touch with me on LinkedIn or hire me on UpWork.
Learn with me on YouTube @DAXJutsu or follow my page on Facebook @DAXJutsuPBI.

View solution in original post

5 REPLIES 5
Anonymous
Not applicable

Hi @Fyousif92,

 

Thanks @danextian  and @Akash_Varuna  for addressing the issue.

 

we would like to follow up to see if the solution provided by the super user resolved your issue. Please let us know if you need any further assistance.
If our super user response resolved your issue, please mark it as "Accept as solution" and click "Yes" if you found it helpful.

 

Regards,

Vinay Pabbu

Anonymous
Not applicable

Hi @Fyousif92,

 

we would like to follow up to see if the solution provided by the super user resolved your issue. Please let us know if you need any further assistance.
If our super user response resolved your issue, please mark it as "Accept as solution" and click "Yes" if you found it helpful.

 

Regards,

Vinay Pabbu

Anonymous
Not applicable

Hi @Fyousif92,

 

we would like to follow up to see if the solution provided by the super user resolved your issue. Please let us know if you need any further assistance.
If our super user response resolved your issue, please mark it as "Accept as solution" and click "Yes" if you found it helpful.

 

Regards,

Vinay Pabbu

danextian
Super User
Super User

 

hi @Fyousif92 

If this behavior occurs in M, it's most likely due to a merge operation where multiple rows from the right table match each row on the left. As a result, the left-side rows are duplicated based on the number of matching rows.

If it happens in DAX, it's more difficult to diagnose without examining the specific measures (including any referenced ones) and the structure or contents of the tables involved.





Dane Belarmino | Microsoft MVP | Proud to be a Super User!

Did I answer your question? Mark my post as a solution!


"Tell me and I’ll forget; show me and I may remember; involve me and I’ll understand."
Need Power BI consultation, get in touch with me on LinkedIn or hire me on UpWork.
Learn with me on YouTube @DAXJutsu or follow my page on Facebook @DAXJutsuPBI.
Akash_Varuna
Super User
Super User

Hi @Fyousif92 This issue might stem from unintentional data duplication in Power Query or incorrect DAX aggregations. Check Power Query steps for accidental appends and validate relationships to avoid many-to-many joins. Review DAX measures for unnecessary iterations or summations.

Helpful resources

Announcements
September Power BI Update Carousel

Power BI Monthly Update - September 2025

Check out the September 2025 Power BI update to learn about new features.

August 2025 community update carousel

Fabric Community Update - August 2025

Find out what's new and trending in the Fabric community.

Top Solution Authors
Top Kudoed Authors