Conversion Errors when using Input Data - How to avoid?

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.

Input

Accepted answers

danilang

Hi @elamp6

When I Input your file, I don't get any date fields created at all. All the fields are either string or double. Did you create the sample by copy/pasting to a new file? That may have changed the format. Can you try creating a copy of the file in Windows and deleting the extra rows from the copy and posting that?

Dan

All comments

Treyson

Check the "File Format" option 2 on the options panel.

elamp6

@Treyson -

Not sure what I'm supposed to do from there...It is an excel workbook and I am importing it as such.

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.

Screenshot 2024-09-02 172940.png

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

Quick Links

This months top contributors

atcodedog05 19458

Qiu 15866

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703