Forum Discussion
SharePoint date differs from Power BI date
is there any news on this item? I got the exact same issue and it is annoying.
how can i change the api from 15 back to 14? the funny fact is it was working yesterday and the days before and just with today (I actually do notknow if there was an update or not) it does not work anymore.
Ni, I've noticed the same yesterday. I'm not sure if it was there before, but strange behaviour... Changing the API to 14 could work, but then I have to recreate my entire data table...
I would be happy about a solution too.
In any case, my column in SharePoint is set to Date only, I'm not sure why it comes over with a time to PowerBI in the first place.
You should just be able to edit the M code for the read from the SharePoint list and probably the first few lines of code without having to completely rewrite the query.
IIRC when I had to do this for another problem I started off a new query against the same List, changed the API to 14 and then expanded the data out until it was in the same structure as the original query. Then cut and paste the M code from the temporary query into the M code of the old query, probably adjust a few #stepname bits and off you go.
If I've misunderstood your problem, then please excuse my ramblings :-)
You understood right, I think. But with the different API, somehow some column names are also different, for example gets an extra "0" to the end, so I think at the end of the day, it will be easier to make it again step by step.
But this basic issue should be still solved, as this is just a workaround.
