Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
2 years ago

Discrepancy Between Individual and Total Values in Power BI Service Report

 

The report works correctly in Power BI Desktop, but it shows value errors in the Service. In the above picture, the "issue" column shows significantly different values for the individual dates and the total at the bottom. The formula used is as follows. Currently, the slicer in the report is set to select June 1, 2024, to June 4, 2024.

issue = CALCULATE([Sales Amount], DATEADD('Sales_cal'[Date], -1, YEAR))

6 Replies

  • Remember that the Power BI Service runs on UTC timezone.  Their June 4 is most likely not your June 4 especially if you use datetime columns

    • Anonymous's avatar
      Anonymous
      Not applicable

      Thank you for the good answer. However, if that were the problem, the other column value (current year amount) next to it should also be incorrect, but that value matches the actual amount correctly.

      The issue is that the previous year's amounts are displayed correctly by date in the actual table, but the total suddenly includes data for dates from June 5 to June 30, which are not in the slicer.

  • Anonymous's avatar
    Anonymous
    Not applicable

    I discovered an interesting phenomenon. Today is June 5th, and when I select June 1st to June 4th in the slicer, the aforementioned issue occurs. However, when I select June 1st to June 3rd, the issue does not occur, and the total is accurate.

    Is there perhaps a rule where selecting the final date in the data using the slicer returns the entire month?

    Ultimately, the core problem seems to be with the slicer rather than the time intelligence function. When selecting dates "between" in the slicer and choosing two dates, the start date is specified accurately, but the end date sometimes does not apply correctly depending on the situation.

    If anyone has encountered and resolved this issue before, I would appreciate your help.

    • lbendlin's avatar
      lbendlin
      Super User

      Check your data model. Make sure your slicer is fed from a dimension table or a disconnected table, not from the fact table.

      • Anonymous's avatar
        Anonymous
        Not applicable

        Thank you for your interest and for leaving a comment.
        The slicer I use is created with the date values from a separate calendar table, not directly from the Fact table's dates. I heard that this is necessary to use time intelligence functions. However, the issue I'm facing is that when I select the last date in the Fact table, the previous year's same month's data gets converted to the end of that month, not up to the selected date.