Forum Discussion
Web behaves differently than Desktop
I have a report that utilizes a summary matrix on the top of a page and a data table at the bottom. Both the data table and the matrix utilize the same measures. The measures are doing some additional filtering for things like expiration date window and record value and everything works perfectly on desktop. When I publish the same report to the web the measure totals for the matrix do not match those in the table. I have updated filters, rewritten the measures, republished the report and it always works in desktop but the issue persists on the web. Does anyone have any possible solutions I can try?
Hi. This might sound weird but click at the button "refresh visuals" at the report and the shift+F5 or Ctrl+R. Most browser keep so many cache or cookies that will show you old developments that can be tricky.
I hope that helps,
3 Replies
- ibarrau
Super User
Hi. This might sound weird but click at the button "refresh visuals" at the report and the shift+F5 or Ctrl+R. Most browser keep so many cache or cookies that will show you old developments that can be tricky.
I hope that helps,
DreamITLearnAdvocate I
Hi GRikerWilli ,
worth checking one thing beyond cache: since your measures filter on an expiration date window, this is a classic symptom of a time zone mismatch between Desktop (uses your local machine time) and the Power BI Service (processes based on UTC/dataset refresh time). If your DAX uses TODAY() or NOW() for the expiration window, the date boundary can shift by hours between Desktop and Web, causing records to fall in/out of the window differently, which would explain totals matching perfectly in Desktop but not after publishing. Try hardcoding a specific date temporarily to test if the discrepancy disappears; if it does, you'll need to adjust your DAX to account for the Service's UTC-based evaluation.Thank you both! These are both excellent suggestions. I confirmed on my side that the matrix AND the table are matching on the web both yesterday and today. I suggested to my user that they clear their cache. I also suspect that they are comparing 2 different calculations. I'm publishing a new version without the other calculation to see if that solves the problem. If not, I will look into hard coding a date.
