Tableau Output Error: Tableau Output: Got an invalid value 'X' for column "Y"

Hello,

I'm getting an error when publishing with the Tableau Output tool in version 2021.3: 'Error: Tableau Output (86): Got an invalid value '360' for column "LinesPerHour", it must be an int instance'

The field is set as Int 32 and '360' should definitely be a valid integer! Any ideas?

Capture1.PNG

Output

Tableau

Accepted answers

All comments

FaizanSayed

Were you able to figure the error out?

We were facing the same issue and from out testing this happens when you create a new column with just characters.

theyele

We have found that changing the field type to V_String enabled the Tableau tool to output the dataset, but we have not yet been able to find a solution that takes the Integer and process the dataset correctly. Strangely we have a second Tableau output in the workflow that uses the same data as an input and Joins it to another set, and this output did not produce the same error, thus accepting the integers correctly.

FaizanSayed

Just to confirm the second output was created and then no additional columns were added, correct?

theyele

Yes, no additional columns created.

Mitch_S

I too am having this problem with the Tableau Output tool. "Got an invalid value '8' for column ".....", it must be an INT instance. I used a SELECT tool to make sure the column was INT and it is INT32. I tried using INTO32:Forced to see if that helped at it did not.

I am trying to switch from the Publish to Tableau tool to the Tableau Output tool, but the new tool just sucks sooooo much. I have no workflow errors with the old tool, and many (this is just one case) with the new one.

Alteryx Tableau Output Error.png

Column Contents.png

FaizanSayed

Is there any chance you have any nulls in the dataset?

Mitch_S

Nope. In the SQL query I COALESCE all the NULLs with 0. There is no column in the entire dataset that contains a NULL value.

FaizanSayed

Did you add a new column after creating the first dataset?

Or try creating a new dataset completely and see whether that works?

Mitch_S

I received this update from Support in response to a ticket. Since sending data to Tableau is 95% of what I do with Alteryx, the software is no longer usable for me.

Hi Mitch,

Thank you for confirming.

Unfortunately, it looks like you've stumbled on to another known defect on our end.

The following data types seem to be running into similar issues, with different error messaging:
Float
Double
Int16/32/32:enforced/64
This has been written up by our team and is currently set with a status of Open. There is currently no timeline for a fix but I am hopeful that this is looked at/addressed for the next release of the Tableau Tool.

bsherman901

Anybody have an update on when this will be fixed? This is a pretty ridiculous bug considering how closely Tableau and Alteryx are used together.

Mitch_S

I agree bsherman901. I've had to switch to using python to push data to Tableau since Alteryx can't get their tools to work.

MichelleMitchellLutz

Hi!

We recently migrated to 23 1 and are running into a similar issue with the new Output to Tableau tool. Any update from Alteryx?

JohnMaty

Well mine can be added to the defect list

Error: Tableau Output (144): Got an invalid value 'POLYGON ((-79.85788... for column "Y", it must be a bytes or a bytearray instance

This is happening with polygons

aberry0613

I had this issue as well. I used the select tool to change to a fixed decimal and it now publishes with no error.

michaelkostinovski

1. Instead of Int - use Fixed Decimal (19.0)

2. DateTime is not working either, so convert to Date

3. Some Dates are not converting properly (shows 2089 for the year instead of 2019 for instance), so I just convert Dates to String and would do extra conversion on Tableau

A lot of bugs thou and I hope Alteryx team will resolve them soon

Hope that will help

FaizanSayed

There is new update of Tableau Tool 1.4.1 which supposedly fixes

Fixed issue where Tableau Output returned "'NoneType' object has no attribute 'dtypes'" error when writing date fields with a future year. (TPM-3246)
Fixed issue where Tableau Output returned "Got an invalid value" error for a mix of data types. (TPM-2968)
Fixed issue where Tableau Input returned "'NoneType' object has no attribute ‘year’" error when reading Date or DateTime data types. (TDCE-293)

michaelkostinovski

I just realized it after I posted it that 13.1 wasn't available any more. - Thank you

Quick Links

This months top contributors

atcodedog05 19598

Qiu 15867

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703