Forum Discussion
Power Query - Date error after filtering (but not before)
Step 1: Lie down
Step 2: Try not to cry
Step 3: Cry a lot.
I managed to fix it though, I copied the exact M code from the other 3 tables that used almost identical Excel tabs (they had one or two extra steps that did redundant things like removing unrelated columns etc) and it magically decided to cease torturing me.
Thanks for your help regardless!
Jake
Hey Anonymous ,
as we don't have you Excel file, we can't reproduce it like that.
It would be easier if you can share the Excel file.
Otherwise what does the error say?
Hi Denis,
Here is a link to a copy of the Excel tab with any potentially sensitive data replaced:
https://www.dropbox.com/scl/fi/c6yqyxqp2i5plg7ai14l0/PBI-Share-File.xlsx?dl=0&rlkey=ramp23if8yayas5h3dalo549b
The error wording is:
"OLE DB or ODBC error: [DataFormat.Error] We couldn't parse the input provided as a Date value.. An unexpected exception occurred."
Thanks,
Jake
Hi Anonymous ,
Please share the file publicly. I have no access.
In addition, it is suggested to check "Column distribution". Then we can clearly know whether there is an error and will not ignore error rows.
Best Regards,
Icey
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi Icey,
I'm not sure why you can't access as the file is set to public view:
Here is the result from checking 'Column Distribution':
Thanks!Hi Anonymous ,
Sorry, my mistake. I can access it. And in your scenario, only "Column quality" option is needed to check. With this feature, we can find if there is any errors. "Column distribution" is not needed, which provides a set of visuals underneath the names of the columns that showcase the frequency and distribution of the values in each of the columns.
Back to the topic. I have tested with the file you shared, but can't reproduce your issue. It works on my side. Could you check if there is really nothing wrong in the previous step?
Best Regards,
Icey
