Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more

Reply
Anonymous
Not applicable

SharePoint List Date Offset Problem

My source is a SharePint Online List in (in one of the US time zones). The column in question is a standard date type column ('Implementation Date').

When I load them in Power BI (it is located in GMT TZ), most of the dates are offset by one day in the past. All but one, that was freshly added today, are wrong. I will paste an example with two items that have the same implmentation date, but Power BI 'sees' them differently. SIte 2 is shown in Power BI as 14 March.

Here what it looks like in SP ('modified' is the generic SP column):

LoationImplementation DateModified
Site 115/03/202110/03/2021 11:24
Site 215/03/202115/03/2021 12:19

nadger_0-1615825835329.png

Here is what it looks like in Power BI Query Editor:
IMPL_Date

Site 114/03/2021 00:00:00 +00:00
Site 215/03/2021 00:00:00 +00:00
 
 
 

I have no explanation about why is that, but since the 'SIte 2' record was the latest to be added and that happened today, I suspect it might be due to have omething to do wiht the DST time hange. From what I know, in USA, that happened on Sunday?

So it seems that whatever item was added after Sunday seems to have the correct date, but what should I do for the rest of the records on that SP list? I tried editing them, but they are still with the wrong date.

2 REPLIES 2
lbendlin
Super User
Super User

Use the DateTimeZone column type.

 

Solving DAX Time Zone Issue in Power BI - RADACAD

Anonymous
Not applicable

Thanks, but NOW just gives e the current date with some deductions. That does not solve much since each 'IMPL_DATE' row has a different date. And even if this column is converted, there'd still be items with the correct dates and will need no conversion. Pretty much every item that was created after 15.03 is ok. and needs no intervention.

Sounds like an inherent problem with Power BI's time zones and DST settings, that from what I see is around for quite some time.

Helpful resources

Announcements
Power BI DataViz World Championships

Power BI Dataviz World Championships

The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!

December 2025 Power BI Update Carousel

Power BI Monthly Update - December 2025

Check out the December 2025 Power BI Holiday Recap!

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.