Forum Discussion
Number Mismatch Between Power BI Desktop and Service
Hello,
I have a report in Power BI where I receive numbers from a SharePoint list. The model is very simple, consisting of just numbers and dates. I adjusted the date to the local timezone by adding 3 hours, as the dates are in UTC from SharePoint.
The problem arises when I publish the report to the Power BI Service. One of the numbers is always different from the number in the Power BI Desktop report (and the SharePoint list) by 2.
Here is the number from the Power BI Desktop report (the SharePoint list has the same number):
And here is the number from the report in the Power BI Service:
I suspect the issue might be related to rounding. In the SharePoint list, where I initially get the data, the number is the sum of two numbers from different SharePoint lists. Perhaps Power BI Service is rounding the number differently.
Could you please help me identify the cause of this issue?
Thank you.
Hi alsalikh_1416 , It might be because of rounding differences or data refresh inconsitencies
Rounding: Ensure correct data type and explicitly round values using Power Query or
RoundedValue = ROUND(SUM(Table[Column]), 2)Time Zone: Verify the 3-hour adjustment doesn't exclude rows due to mismatched time zones.
Data Refresh: Ensure the dataset in Service is refreshed and matches Desktop.
Filters: Confirm identical filters and aggregation logic in Desktop and Service.
Regional Settings: Match regional settings between Desktop and Service.
If this post helped please do give a kudos and accept this as a solution
Thanks In Advance
2 Replies
Hello, thank you for your answer.
The problem was in rounding, power BI rounded to the smaller value, while the Sharepoint rounded to the bigger value.
I used this formula in the Power Query: Number.RoundUp([Column])Hi alsalikh_1416 , It might be because of rounding differences or data refresh inconsitencies
Rounding: Ensure correct data type and explicitly round values using Power Query or
RoundedValue = ROUND(SUM(Table[Column]), 2)Time Zone: Verify the 3-hour adjustment doesn't exclude rows due to mismatched time zones.
Data Refresh: Ensure the dataset in Service is refreshed and matches Desktop.
Filters: Confirm identical filters and aggregation logic in Desktop and Service.
Regional Settings: Match regional settings between Desktop and Service.
If this post helped please do give a kudos and accept this as a solution
Thanks In Advance
