The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hi,
in the table read by Power BI I have a timestamp column:
but when I import the table on Power BI, the column (automatically set on Date/Time) is displayed in this way:
It seems like it is in some way rounded... How can I prevent this and display the original timestamp of the source table?
Thanks,
Andrea
Solved! Go to Solution.
In the end, I discovered that it wasn’t a rounding issue. The source table contains the value '2025-06-30T22:00:00.000Z', which is in standard UTC (Zulu time), while the local time is UTC+2 — so Power BI was converting the timestamp to local time.
In the end, I discovered that it wasn’t a rounding issue. The source table contains the value '2025-06-30T22:00:00.000Z', which is in standard UTC (Zulu time), while the local time is UTC+2 — so Power BI was converting the timestamp to local time.
Hi @arimoldi
That doesn't seem rounded to me. Both are the same - June 30 2025 10PM. If you want to include the timezone, ensure that the data type is datetimezone.
If you want it in the format as your original, create a custom column in the query editor or don't change the date type at all. Keep in mind that either way, the column, new/original, will be of type text.
Text.From(DateTimeZone.ToText([Timestamp], "yyyy-MM-ddTHH:mm:ss.fffZ"))
If you look at the screenshots they are not the same:
In the source table it is displayed: "2025-06-30T22:00:00.000Z"
While on Power BI it is written "01/07/2025 00:00:00"
Thanks,
Andrea