Forum Discussion
Load was cancelled by an error in loading a previous table
- 10 years ago
Issue resolved with no specific resolution.
I saved offending query M code, deleted query, recreated query using saved M code, and now it works.
I haven't see any info on how to read the Tracing logs. Can anyone say if these would hold relevant information to troubleshoot issues like these?
Sometimes the error messages in UI are not enough.
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.
- konstantinos10 years ago
Memorable Member
curtisp It is a strange error, happening to me a lot lately.
I think has to do with PQ trying to quess coloumn data type.
Try to go to query editor formula bar and change in step 'Change Type' the type of column to 'DateTime' instead of just 'Date', at least this was my issue due to csv data type.
- curtisp10 years ago
Helper II
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.
Fails with Apply Changes
Fails with Report Refresh
- curtisp10 years ago
Helper II
Issue resolved with no specific resolution.
I saved offending query M code, deleted query, recreated query using saved M code, and now it works.
I haven't see any info on how to read the Tracing logs. Can anyone say if these would hold relevant information to troubleshoot issues like these?
Sometimes the error messages in UI are not enough.