March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early bird discount ends December 31.
Register NowBe one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now
As annotated by the arrows, I have a measure that totals to different amounts in a card and a table. The table figure is correct. The exact same filters are applied to both(I copied the table and turned it into a card). Why might this be and how can it be solved?
Hi,
Share the download link of the PBI file.
It's a measure totals issue and it's by design. Search for 'dax measure totals' and have a go at fixing it.
Post back with your measure, model and some data if you can't work it out
@IssieWissie , That is strange. Please share the measure calculation.
Make sure no row is selected/clicked in the table and there is no visual level filter
If this does not help
Can you share sample data and sample output in table format? Or a sample pbix after removing sensitive data.
Table 1:
JOB CODE | PLANNED HRS | START DATE | END DATE |
1 | 35 | 20/01/2023 | 31/01/2023 |
2 | 35 | 21/01/2023 | 31/01/2023 |
3 | 35 | 21/01/2023 | 31/01/2023 |
4 | 35 | 25/01/2023 | 31/01/2023 |
Table 2:
JOB CODE | SECTION | ACTUAL HRS | STOP DATE |
1 | A | 4 | 22/01/2023 |
1 | A | 6 | 23/01/2023 |
1 | B | 10 | 23/01/2023 |
1 | B | 11 | 24/01/2023 |
2 | A | 2 | 22/01/2023 |
2 | A | 5 | 23/01/2023 |
2 | B | 9 | 23/01/2023 |
2 | B | 13 | 24/01/2023 |
3 | A | 3 | 22/01/2023 |
3 | A | 6 | 23/01/2023 |
3 | B | 12 | 23/01/2023 |
3 | B | 11 | 24/01/2023 |
I have put together a sample which is similar to what I'm using. The data is coming from a direct query (table 2) and excel sharepoint (table 1). Measure 4 is only a sum of all different sections for a job. So for Job 1, Measure 4 is 31.
Since table 1 is a sort of unique job code table, I've related table 1 and 2 through "JOB CODE". Then I've related table 1 by connecting "END DATE" with my calendar table. My reasoning was that due to the nature of table 2 having different dates allocated to a job code, relating the table 1 instead which has a single date allocated instead to "group" all data to a single date. Lastly the filters I have on the actual visuals are the following:
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
User | Count |
---|---|
90 | |
89 | |
85 | |
73 | |
49 |
User | Count |
---|---|
169 | |
144 | |
90 | |
70 | |
58 |