Forum Discussion
Sharepoint folder date problem
After updating to March 2018 version of PBI desktop, the Sharepoint folder integration is off when it comes to the Date modified and created.
The error shown is:
DataFormat.Error: We couldn't parse the input provided as a DateTimeZone value.
Details:
2/26/2018 1:01 AM
I have tried to change the the data type to "Using Locale..." but without luck.
This is a bug in March issue and unfortunately also on the Service.
17 Replies
Hi.
We encountered the same issue right now. We solved it by extracting and trasforming the Error.Detail
1. Create a cauculated column with the following formula
=try([Date modified])2. Expand the records in the new column
3. Expand the records in the new ".Error"-column
4. Trasform the new ".Error.Detail"-column and the [Date modified]-columns to a datetime value with the correct locale.
5. Merge the two columns with a new calculated column.
6. Delete the two "old" date columns afterwards.
7. Rename the new datetime column "Date modified", and voila!
Hi kimmend,
According to error message, it seems like you are try to convert date value to datetimezone but failed.
Did these values works in normal data type? Can you please share a part of sample data for testing?Regards,
Xiaoxin Sheng
Hello Anonymous, thanks for the reply. The problem is that I am not trying to convert anything, this is how it looks when the data is pulled in from Sharepoint folder.
Already when the query is presented before editing the query, it shows errors for most dates. This wasn't the case before the March update. Does it have something to do with the regional settings of Power BI?
This is a bug in March issue and unfortunately also on the Service.
I haven't been able to find any workaround for this issue -- so basically I can't pull 'date created' from a sharepoint folder source. This is a significant impact/issue.
I haven't been able to find any workaround for this issue -- so basically I can't pull 'date created' from a sharepoint folder source. This is a significant impact/issue.
The work-around I used is to set the regionalization on my sharepoint consistent with the one I'm using in Power BI, since my hunch is that the API is having issues when having different date formats (ie. mm/dd/yyyy versus dd/mm/yyyy)... eventual timezone shift you still can compensate in your power query logic.
I still don't understand why the Power BI support team needs votes to resolve bugs that harm global implementations.
