Conversion Errors when using Input Data - How to avoid?

[elamp6]

I have a dataset that I'm importing using the Input Data tool. When I run the workflow, I'm hit with thousands of conversion errors (one for every row). It appears to be interpreting a five digit ID number as a "date" rather than a string or numerical data type and this is what is causing the error. Is there any way to eliminate this issue via some setting in the input data tool? I believe it's causing the workflow to run much more slowly than it would otherwise.

[danilang]

@elamp6 

Glad to help.  It's the complex ones like this that are interesting

Can you mark at least one of the answers as solved, it can even be yours.  This will help users in the future.

Dan

[stephenfullergenerali]

I'm having a similar problem but from a SQL ODBC source rather than an Excel file.  The field in SQL contains a list of dates that cannot be changed at this point, but the field has had incorrect dates entered (the year has been entered as 0202 instead of 2020), and whilst this format is allowed in SQL, when inputting into Alteryx it gives file conversion errors.  This is an example of the data in this field.

Is there any way of supressing the file conversion errors when this workflow is run.