Forum Discussion
PowerBi vs. Amazon Redshift Different Minimum Report_Date from the same table After UTC Midnight
Hi UKapadia ,
Thank you for the update. Since adjusting the timezone logic did not resolve the issue and today's records are still missing after the UTC date transition, it would be helpful to review the exact query or filtering logic that is being used to return the current day plus the next three days.
Could you also confirm whether the dataset is using Import mode or DirectQuery. Microsoft Learn documents that current date/time functions can be evaluated differently across environments, but additional query details would be needed to determine why the current day's records are being excluded in Power BI while they continue to appear in DBeaver.
References:
https://learn.microsoft.com/en-us/powerquery-m/datetime-localnow
https://learn.microsoft.com/en-us/powerquery-m/m-local-fixed-utc-variants
Hi UKapadia ,
Thanks for reaching out to Fabric Community Forum.
This behavior appears consistent with a timezone boundary issue rather than missing data. Microsoft Learn notes that Power Query Online and cloud based scenarios such as Power BI service can evaluate current date/time functions differently from local environments, and differences become more noticeable around date boundaries such as midnight. If the source query logic depends on the current date, a UTC based evaluation in the service can result in a different effective date window than what is observed in another client.
To help avoid these inconsistencies, Microsoft recommends using UTC-based date/time functions when consistency across environments is required and applying timezone conversions explicitly when business logic must follow a specific local timezone. Since the discrepancy occurs exactly at the UTC day transition, it would be worth reviewing any current-date-based filtering and validating whether the same timezone context is being used throughout the query and reporting logic.
References:
https://learn.microsoft.com/en-us/powerquery-m/datetime-localnow
https://learn.microsoft.com/en-us/powerquery-m/m-local-fixed-utc-variants
https://learn.microsoft.com/en-us/powerquery-m/datetimezone-utcnow
https://learn.microsoft.com/en-us/powerquery-m/datetimezone-switchzone
Thank you.
Hi V-shirivolu,
We have tried adjusting the time zones, but the Power BI load is not displaying today's data at 19:00 CST / 00:00 UTC. The time zone function works correctly if we do have data available.
The issue is that the schema includes today's data along with data for the next three days. However, at midnight UTC, we are losing today's data and instead, we are only getting data for the tomorrow (as today) + next days in the schema when we load it into Power BI but it display different in dbeaver.
Best,
Urvin
Hi UKapadia ,
Thank you for the update. Since adjusting the timezone logic did not resolve the issue and today's records are still missing after the UTC date transition, it would be helpful to review the exact query or filtering logic that is being used to return the current day plus the next three days.
Could you also confirm whether the dataset is using Import mode or DirectQuery. Microsoft Learn documents that current date/time functions can be evaluated differently across environments, but additional query details would be needed to determine why the current day's records are being excluded in Power BI while they continue to appear in DBeaver.
References:
https://learn.microsoft.com/en-us/powerquery-m/datetime-localnow
https://learn.microsoft.com/en-us/powerquery-m/m-local-fixed-utc-variants
Hi UKapadia ,
I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you
Hi UKapadia ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.