Forum Discussion
Date issues with Sharepoint file sources
Anonymous
Thanks for your instructions, but it's not working for me.
Even before I "change type, using locale.." there is an error reported in the dates columns from the sharepoint.files line:
so I believe there's something broken when getting the data via the sharepoint.files command. I can get other date columns to behave correctly, and I've managed to replace what I was after with a sharepoint.tables query. The sharepoint.tables query takes a while to run, so I'd prefer to go back to the sharepoint.files command.
Anything else I could try?
Michael
Buzz123,
I suspect that there are extra spaces in the date values after using sharepoint.files command to import data. Please remove these extra spaces following the guide in the similar thread below and change data type.
https://community.powerbi.com/t5/Desktop/DataFormat-Error-We-couldn-t-parse-the-input-provided-as-a/m-p/84355
Regards,
Lydia
Same issue. Was working fine before, now its not. I tried the changing data tyapes and removing spaces. Nothing seems to be working. The error happens at the first step when the data is being read.
When I opened up Power BI desktop to have another look at this, I got notfied that a new version was available. Hoping that it would be sorted, I instaled the new version (2.56.5023.942), but the problem is still there.
As mentioned above, the error occurs in the first line of the query (source = ...). The Date Modified and Date Created fields are defaulting to a Date/Time type data type as expected. However the cells in both columns show an error. Selecting an individual cell shows this error:
DataFormat.Error: We couldn't parse the input provided as a DateTimeZone value.
Details:
6/03/2018 9:05 a.m.Changing type to anything else (including text, and date/time/timezone with locale set to English (NZ)), still returns the same error. So, I can't get in to manipulate the date field.
(I've just tried to do the same thing in Excel, and the data loads correctly...
So, that would seem to indicate that there's a problem with the query engine in Power BI desktop.)
Any ideas?
Michael
Same issue here. I downgraded to the previous version and it works ok again.
