Forum Discussion
Problem with the Incremental Refresh configuration
Hi Anonymous ，
This is a type conversion error but without looking at the power query steps it is difficult to tell you exactly what the solution will be. You could try to add a "Remove errors" at the end which will remove the erroneous rows but of course this won't be the ideal method since I am assuming you don't want to lose data. Also in my experience the data being displayed are only the first 1000 rows whereas the error might be in a row below so if you select "Column profiling based on the entire dataset" and use the drop down to try to scroll and see if you can identify something which doesn't look like a date.
Best regards,
Community Support Team Selina zhu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly
Anonymous , Please share the error in text format and I can see in the formula bar, the filter is on some other column of date data type. Please remove that step and add filter again on correct column
Hi amitchandak ,
Thank you for your quick response. Ready the correction. Now the filter has been applied for the proper column.
- However, I still continue speriencing the same error message: "OLE DB and ODBC Error: [DataFormat.Error] Cannot parse input supplied as a Date value.."
- Regards your request, "share the error in text format", what do you mean exactly with this? Unfortunately for me, the displayed error is not redirecting me to a specific step in the query editor so, I don't know the concret formula / query that we must require to correct / update.
Let me know what you could require in terms of screenshoots, files or code to support this issue.
Thank you in advance,
Regards.
Hi Anonymous ，
This is a type conversion error but without looking at the power query steps it is difficult to tell you exactly what the solution will be. You could try to add a "Remove errors" at the end which will remove the erroneous rows but of course this won't be the ideal method since I am assuming you don't want to lose data. Also in my experience the data being displayed are only the first 1000 rows whereas the error might be in a row below so if you select "Column profiling based on the entire dataset" and use the drop down to try to scroll and see if you can identify something which doesn't look like a date.
Best regards,
Community Support Team Selina zhu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly