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.
db042190 Hey,
Step 1: Check Import and Refresh Process: Ensure that the data refresh process on both the service and desktop includes all necessary tables and views. Double-check any filters applied during import.
Steps 2: Validate Relationships and Joins: Review the relationships in the Power BI model and the join logic in SQL. Ensure they align precisely, focusing on keys used for joins. Consider possible cardinality issues or missing join conditions.
Steps 3: Investigate Calculated Measures: If the semantic model includes calculated measures or columns, analyze them to ensure consistent logic. Check if measures apply correctly across all environments.
Thanks
Harish M
Kindly accept this as a solution if it resolves your problem, and please consider giving kudos to the post as well.
- db0421901 year ago
Impactful Individual
Thx Harish, thats pretty much what i'll try today. For full transparency, i should also have mentioned i made significant changes to dax based items in the clone which is intended to replace the original when the dust settles...mostly because the original author used Today() a lot in a report that reports on sales thru yesterday.
But...the mystery surrounding how a refresh on the desktop made the downloaded original show the same numbers as the clone on a semantic model that is static after 4 am kind of remains the 3 ton elephant in the room. That baffles me. I'll report back here what i find. Its like a needle in a haystack. Also, i should have mentioned the original author had (or maybe has) an applied step that eliminates dupes. I'll take alook at that too. bad practice in my opinion but maybe i'll get some insight.