Forum Discussion

HenryH's avatar
HenryH
Regular Visitor
10 years ago

SharePoint date differs from Power BI date

Hi,   I have imported data from a SharePoint list into Power BI including one column containing a date. The date in Power BI differs 1 day from the date in SharePoint. e.g. Sharepoint: 1/6/2016 >...
AleksanderPunt's avatar
AleksanderPunt
Helper I
8 years ago

Having the same issue!

When are they fixing this?? Or is it because of incorrect regional time settings within Power BI/Sharepoint?

 

We add items in the sharepoint list with current dates (probably at midnight), but an hour gets subtracted when importing the dataset in Power BI. So "Dec 1st - 00:00" becomes "Nov 30th - 23:00".

 

Irritating when doing monthly analysis.. A workaround is to create calculated columns in the sharepoint list with year, month and day - BUT it can't be used as a timestamp-filter within Power BI.

  • danielH's avatar
    danielH
    Helper I
    8 years ago

    This issue was resolved, yet since this month update it started again. could you please have a look ? 

    i check with the API 14 and it works. but this is just a work around. 

    • nate_bd's avatar
      nate_bd
      New Member
      8 years ago

      I know this isn't strictly related, however there are similarities to what I've just encountered while working on an SPFx solution where we're duplicating SharePoint Events that have a recurrence set.

       

      There appears to be a mismatch between the server generated timestamp (which appears to be UTC) and the FieldValuesAsX (X = Text or HTML). I believe that the base DateTime properties persist to maintain back end continuity, and the SharePoint Regional settings dictate what is seen within FieldValuesAsX.

       

      Here's what I saw within the console.

       

      odata.type:"SP.Data.EventsListItem"
      EndDate:"2018-08-11T05:00:00Z"
EventDate:"2018-08-10T21:00:00Z"

FieldValuesAsText:
EndDate:"11/08/2018 5:00 p.m."
EventDate:"11/08/2018 9:00 a.m."
      odata.type:"SP.FieldStringValues"

       

      I don't know whether this will help anyone here, however this enabled me to track down my non-PowerBI issue that is similar...

       

      I'll see myself out now :)