Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hello,
This is a dax query that I have used to create a measure.
CALCULATE(SUM(Invoice[AmountDueAUD]), Invoice[Type]="ACCREC")
The problem is that there are multiple rows with the same invoice number and each row has the same value in AmountDueAUD column. So I want to remove the duplicate invoices before summing up the AmountDueAUD column. I know I can remove the duplicates using "Remove Duplicates" option, but there are other charts in my report that require that multiple columns. So, I want to achieve removing duplicates using Dax. I tried this but didn't work:
CALCULATE(SUM(Invoice[AmountDueAUD]), DISTINCT(Invoice[InvoiceNumber]), Invoice[Type]="ACCREC")
Thank You
Solved! Go to Solution.
You could try and remove duplicates via the Query Editor (which has an excellent function for removing duplicates)
Or in DAX you could create a summary table with just the lines you need
Summary Invoice Table = SUMMARIZECOLUMNS( 'Invoice'[InvoiceNumber], --- Columns --- "AmountDueAUD",MAX('Invoice'[AmountDueAUD]) )
You could try and remove duplicates via the Query Editor (which has an excellent function for removing duplicates)
Or in DAX you could create a summary table with just the lines you need
Summary Invoice Table = SUMMARIZECOLUMNS( 'Invoice'[InvoiceNumber], --- Columns --- "AmountDueAUD",MAX('Invoice'[AmountDueAUD]) )
Thanks @Phil_Seamark. This worked for me.
I wanted to do it without having to create a new table and also I couldn't do it via Query Editor because there were other charts that relied on the duplicates.
Please let me know if you come across something that solved this problem without having to create a new summary table.
Hi @bjoshi,
It probably is possible to do as a measure over your original table, but it's probably not good data modelling to have the same number on repeating lines that shouldn't be there in the first place.
User | Count |
---|---|
76 | |
75 | |
46 | |
31 | |
28 |
User | Count |
---|---|
99 | |
91 | |
51 | |
49 | |
46 |