Oh this is interesting. I found the source of the error message by some sluething about. I looked at one of the date fields in the query edit view and tried to get it show all date values and got this very hidden error message at bottom of date picker list.
[DataFormat.Error] We couldn't parse the input provided as a Date value.
This is odd because upon inspection of original data files (csv files) all of the values in this date column are in fact dates.
@konstantinos Thanks that didn't work though. This error message seems to indicate broad spectrum of issues so lots of specific resolutions.
Like you, I haven't ever seen this error over past 2 years working with Power BI/Power Query/Power Pivot.
The quirk here is that the query refreshes successfully when run manually in editor. Itworks when the offending query is run individually, manually, and it works with the Refresh All in query editor too.
But it is failing with the error when queries run during report Refresh or Apply Changes. It indicates that there is 1 error in the offending query, but again, there is no error message when run manually.
Glad to hear the issue has been solved by yourself.
In Power BI Desktop, we can enable tracing log via File –> Options –> Diagnostics –> Enable Tracing. When we meet the error when use Power BI desktop, we can go to check detail information. Please take a look at links below:
I am new to PoweBI, but I got this error quite soon.
I was notice I had a query with a warning. In those query I had an incorrect DAX formula. Once I removed the error(I just delete the formula) the load went smoth again. I guess it's a general error due to some incorrect sintax.