Forum Discussion
totals dont match
- 1 year ago
i removed the one FYTD table from the model. I converted floats to decimal (18,6). I moved some calc responsibility away from DAX into the sql views. I left some applied sort , rename and maybe dupe steps deleted. I removed one critical flag that was probably working but now cant even get to pbi thanks to a sql predicate blocking it.
All numbers match now not only to our warehouse $'s, but between the desktop and service as well. Hard to explain (rounding errors) to the user when the main focus was on making the report smarter on the 1st of the month. The report always tried to report thru "Yesterday". With previous authors so fixed on the Today() function, that created some challenges.
Hi db042190
Hi please keep a note of the following points:
-
Check relationships in Power BI, especially for duplicates or incorrect join types.
-
Compare filters and slicers used in each model/report.
-
Review calculated columns/measures for logic differences.
-
Verify data source and refresh settings, make sure all are pulling from the same data and updated.
-
Look for Row-Level Security (RLS) differences between environments.
-
Check for hidden duplicates or data being counted twice in the model.
-
Check float/decimal handling but usually this isn’t a large discrepancy.
Break down the total by facility/customer to see where numbers diverge. Usually, it's a relationship or filter context causing this kind of mismatch.
thx rohit. I'm poking around today. Luckily RLS isnt in our environment just yet. Data sources should be identical. Im suspecting both reports are wrong by a few $. I have an old ssrs report that the prod pbi report replaced and i have a feeling its going to be very useful in both this mystery and also verifying my dax fixes in the clone to the short sighted use of Today() for a report that reports thru yesterday . When Today() is the 1st of the month, nothing shows. We've known about this shortcoming for a long time. I finally went down the rabbit hole of fixing it.