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

The ultimate Microsoft Fabric, Power BI, Azure AI & SQL learning event! Join us in Las Vegas from March 26-28, 2024. Use code MSCUST for a $100 discount. Register Now

Reply
dr2506
Advocate I
Advocate I

PowerBi Server shows dates one hour earlier than in Desktop (Converting from ISO-8601)

Hi community,

 

Appreciate if anyone can assist here as I have been struggling to get my head around this for weeks. 

I am pulling a data set through an API from our Service Desk managament system which provides dates in ISO-8601 format. I am in the UK and our timezone is set to London/GMT. When I convert the data in power query (change type) to date and time they are correct. However performing the same in PowerBi Service the data is one hour behind so causes the stats to be incorrect especially as we need to show the rate of calls per hour. 
I understand that the PowerBi service uses UTC which is the same as GMT so should not be an issue for us in the UK. If I publish the data from Desktop to Service then it is correct but as soon as they PowerBi performs a refresh throught he api the date is incorrect again by one hour.
Going crazy on this one so appreciate any guidance/advice please.

1 ACCEPTED SOLUTION
Burningsuit
Resident Rockstar
Resident Rockstar

Hi @dr2506,

You're right that Power BI service uses UTC which is the same as GMT, but currently the UK is not on GMT, we are on BST (British Summer Time) which is GMT+1hour. So that is why there is a difference between the times.

You'll need to account for this in your data, either with Power Query or DAX.

See: Convert UTC to Local Time in Power BI - IntelliTect

or 

Solving DAX Time Zone Issue in Power BI - RADACAD

hope this helps

Stuart

View solution in original post

1 REPLY 1
Burningsuit
Resident Rockstar
Resident Rockstar

Hi @dr2506,

You're right that Power BI service uses UTC which is the same as GMT, but currently the UK is not on GMT, we are on BST (British Summer Time) which is GMT+1hour. So that is why there is a difference between the times.

You'll need to account for this in your data, either with Power Query or DAX.

See: Convert UTC to Local Time in Power BI - IntelliTect

or 

Solving DAX Time Zone Issue in Power BI - RADACAD

hope this helps

Stuart

Helpful resources

Announcements
Fabric Community Conference

Microsoft Fabric Community Conference

Join us at our first-ever Microsoft Fabric Community Conference, March 26-28, 2024 in Las Vegas with 100+ sessions by community experts and Microsoft engineering.

February 2024 Update Carousel

Power BI Monthly Update - February 2024

Check out the February 2024 Power BI update to learn about new features.

Fabric Career Hub

Microsoft Fabric Career Hub

Explore career paths and learn resources in Fabric.

Top Solution Authors
Top Kudoed Authors