Field: "Field Name" is 0 Length

I am querying a view on an Oracle database that has fields in it that are null. I didn't have any issues with this in the prior version of Alteryx but now that I have upgraded to the latest version it's crapping out on me and it's frustrating that it used to work before and now it does not.

When I try test query, I get an error that says: Field: "CLOSEDSTATUS" is 0 length. As mentioned before, there are many fields that are null in this view.

Short no selecting the null fields from the original view and putting them in downstream using a formula object is there anything I can do on the initial query with the Input Object.

Thanks

Input

Accepted answers

hhaigh1

Hi all!

This has been fixed for 2018.3 which is available for download at licenses.alteryx.com.

Thanks again for bringing this to our attention!

Henriette

All comments

unknown

If these are an integer or numeric fields, you could try casting them as varchar in the select statement and see if that gets by the issue.

Mark_Lurie

I ended up doing the following: cast(null as varchar2(1))

Thanks

brucedataguy

I'm using version 2018.1.4. When working with an In-DB connector and selecting a table (or view), I get this same error when it was fine using version 11.7.

From what I read, the "solution" is to cast the data type? I'm not able to add a SELECT tool because the In-DB connector doesn't return the metadata about the table.

The use of the tools is to make it easy -- now I have to write custom SQL in the In-DB tool to handle varchar2(0) fields?

I think I need to downgrade to version 11.7.

randykluver

I agree, it appears to be a bug in the new version.

We have a lot of inputs just pulling views that have been built for the business. Not allowing these fields to come in is detrimental to the 'Self-Service' space, and doesn't seem to align with Alteryx's general line of thinking.

Quick Links

This months top contributors

atcodedog05 19458

Qiu 15866

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703