Tableau Output Error: Tool #XX: 'NoneType' object has no attribute 'get'

just experiencing this as we are trying the new Tableau tool on our side. any update?

theyele

same here. i wonder if @support is gettgin more than just us with that error.

Ukashi

I have the same problem - bumping it in gope to get solution other than reverting to the old tool.

i discovered that if you have more than one output you have to block until done to get it working. so basically whoever designed this tool made it so only ONE can run at a time.

i also discovered that if you put a block node to get it to not error the tools do not Load data. Soo this was fun...

swadson

I get this error from the Designer as well. Any ideas what the issue could be? One of my colleague us able to run it though. Could it be a tool installation issue?

Error: Tableau Output (6): 'NoneType' object has no attribute 'dtypes'

Solved:

Sync your connections File>Manage COnnections>Sync
Log in to server
Select DCM Data sources
Pick your Connection that is having issues>Select Connections at bottom the three dots on far right
Hit edit
Click Allow connection for SDK

Let us know if that solves your problem

msmith6986

Am having similar error: NoneType object has no attribute dtypes

Any one here find a solution yet?

chvizda

When it not runs on the Server. Here a possible solution: The server must be run with DCM Settings SDK "Allow All" sdk all.PNG

Regards Steffen

BeaBon

this worked for me. thank you @pitmansm

I've noticed that there have been multiple issues with this tool.

Dates over 9999-12-31 throws an error
Data to be published is over 4GB in size
As someone mentioned earlier, this tool cannot run simultaneously with other Tableau Output tools in the workflow.
The table name for incoming connection default of "table" would blow up. Need to change it to table1 or something that isn't table

Tableau Output 1.4.1 is currently in beta and should be out later this month. It solves many issues but not all of them, IMO.

An alternative is to use python code and the Tableau library to publish the data to your Tableau server.

screenshot.png

apathetichell

@TheCoffeeDude I have my share of issues with Alteryx products - but:

Dates over 9999-12-31 throws an error

That makes sense. That should throw an error. That throws an error almost everywhere.

SagarSri

In my case, I have temporarily made this change for date fields until Alteryx comes up with a newer version

kindly add a formula tool before Tableau Output and update the date field with the below logic

If [Date]>='2099-12-30' then '2099-12-29' else [Date] endif

Many ongoing issues... I was able successfully connect it and run with ONE output source after multiple attempts . However, adding more than 2 outputs in the same workflow creates additional challenges. No solution at the moment and we are trying to engage Alteryx support team... I am using 2021.4.2 version of Alteryx and the latest "Tableau Output" v1.4.1

Errors:
1. “Failed to signin to Tableau”
2. “NoneType” object has no attribute “get”
3. “Failed to connect to the server”
4. “Expecting value: line 1 column 1 (char 0)”

Thanks

SagarSri

@michaelkostinovski I am using 1.4.0 for writing the data to the Tableau Server and for reading back 1.4.1 which is working as expected

1. “Failed to signin to Tableau” - This could be due to a DCM sync issue. Check if you have AMP enabled and SDK Mode set to "Allow All"
2. “NoneType” object has no attribute “get” - DCM issue
3. “Failed to connect to the server” - This could be due to a DCM sync issue. Check if you have AMP enabled and SDK Mode set to "Allow All"
4. “Expecting value: line 1 column 1 (char 0)” - Check if your data header is having two rows.

1.4.0 is not available to download, so I can't check it.

DCM issues were checked and tested with ONE output (2 MAX) and they worked, but as soon as you configure more workflows and schedule them on the server then all kind of issues with synch are popping up. Looks very sporadic and not consistent. Very frustrating... Sometimes, the workflow overwrites 2 files and fails one. The other day, just one out of 3 and etc...

I got tired of dealing with Tableau Output's issues in my environment and created a workflow that publishes the hyper file to Tableau using the Python tool. It's a hack job, but it gets the job done. One day or another, I'll go back in and make it prettier.

One of the biggest issues I faced occurred when publishing huge amounts of data to the Tableau Server. The dataset I used to test has 13,661,853 rows and is 15.6 GB uncompressed. When published to a hyper file, it is slightly under 3.7GB.

Publish to Tableau on Alteryx Server 2022.1 – approximately 30-45 minutes to publish.

Tableau Output on Alteryx Server 2023.2 – Anywhere between 45 minutes to 21 hours. However, the tool fails more often than it succeeds.

Similar results are observed when using Alteryx Designer.

publish to tableau using python.yxmd

Unfortunately, it doesn't work for older 2021 version of Alteryx that allowed by my company to use. - Thank you thou

You should be able to open it in 2021 even though it'll throw a version error.

My Alteryx crushes all the time. I still have to push towards the "approved" tool thou as company uses it in many different departments. Thank you for your help thou!

This was shared internally by a user in my company when dealing with the Tableau Output tool.

1. Replace the previous Tableau Output tool with the following configurations. This ensures a new tool ID. Fixing the existing tool doesn't seem to work if it failed previously.
2. Use DCM connection for Tableau credentials
3. Use version 1.4.1.
4. Use the overwrite method for the datasource.
5. Do not output date-time columns to the Tableau server. Convert it to string.
6. For workflows with multiple Tableau outputs, use block until done before Tableau outputs (tested this works for same data source names across different Tableau projects).

I hope this helps you.