Tableau Help Page Use the Tableau tools to read data from HYPER data sources, create a HYPER data source, and save it to Tableau Server or locally. Current version Tableau Tools v1.3.1 (July 19, 2023) * Compatible with Alteryx Designer and Server 2021.4.2 Patch 6, 2022.1 Patch 4 and later. * Requires AMP engine. * Alteryx Server requires stored credentials in DCM to run workflows. * Fixed issue where Tableau Output wrote Null values as “nan” for float data types. (TPM-2210) Known Issues * The tool becomes unstable when uploading dataset larger than 3GB. (TPM-2121) * The refresh button isn’t working for either the Tableau Output or Tableau Input tool. (TFLN-1436) Previous versions Tableau Tools v1.3.0 (June 30, 2023) * Compatible with Alteryx Designer and Server 2021.4.2 Patch 6, 2022.1 Patch 4 and later. * Added new Tableau Input tool to read data from HYPER data sources. * Live data sources aren’t supported. * Only data sources created with the Tableau Output tool are supported for reading. * Requires AMP engine. * Alteryx Server requires stored credentials in DCM to run workflows. * Fixed issue where NULL numeric values were converted to 0. (TPM-1546) * Tableau shows NULL numeric values as 0 by default on dashboards. * Fixed issue where NULL string values were converted to empty string. (TPM-1528) * Fixed issue where DATE was converted into STRING. (TPM-2138) * Fixed issue where Designer ran indefinitely or crashed when DCM was used. (TPM-1986) * Fixed issue with error “The system could not find the path specified” when multiple Tableau Output tools were used on canvas. (TPM-1915) Known Issues * Tool becomes unstable when uploading dataset larger than 3GB. (TPM-2121) * Refresh button is not working for either the Tableau Output or Tableau Input tool. (TFLN-1436) Tableau Output v1.2.1 (March 31, 2023) * Compatible with Alteryx Designer and Server 2021.4.2 Patch 6, 2022.1 Patch 4 and later. * Requires AMP engine. * Fixed issue where dates were converted 70 years in the future (TPM-1896) * Fixed issue where Site couldn't be left blank while authenticating via DCM (TFLN-1170) * Data Source and Project lists are now sorted alphabetically. * Minor UI updates. Known Limitations * Alteryx Server requires the AllowAll value of the SDK Access Mode settings. * NULL values are converted to 0. Tableau Output v1.2.0 (December 13, 2022) * Compatible with Alteryx Designer and Server 2021.4.2 Patch 4, 2022.1 Patch 2 and later. * Requires AMP engine. * Added support for DCM. * DCM is required for running this connector in Alteryx Server. * Added support for SpatialObj. * SSL/TLS validation is now performed against Windows Certificate Store. * FIPS capable. Known Limitations * Alteryx Server requires the AllowAll value of the SDK Access Mode settings. * NULL values are converted to 0. Tableau Output v1.1.1 (December 23, 2021) * Fixed issue with conversion of boolean and datetime fields. Tableau Output v1.1.0 (November 03, 2021) * Added support for Tableau Server On-Premise (Tableau Server 2019.2 or later required). Tableau Output v1.0.1 (September 02, 2021) * Compatible with Alteryx Designer version 2021.3 and later. * Initial release. * Username and Password and Personal Access Token are supported authentication methods. * Create, Overwrite, Append, Update or Upsert multiple tables in a dataset. * Post SQL support. * Proxy support. * Conversion from WKT to Spatial object support. Known Limitations: * v1.0.1 does not support Tableau Server On-Premise. * When working with multiple tables, a .tds file has to be provided (can be obtained from Tableau Desktop). This tool uses a .yxi file format. A .yxi file is a package that includes an Alteryx Tool and all of its dependencies zipped into a single file. When this file is imported into Alteryx, the tool is added to the tool palette in the category specified by the tool. When sharing a workflow that uses a .yxi tool, the tool is not included and must be installed by the recipient.

Hello Community, I had many issues with trying to get the tableau input and output tools working and I was able to get this achieved. Here is what I found out, in case it helps: The issue is that the Tableau tools cannot pull in data that was created in tableau. For instance, if tableau queries snowflake, you will not be able to pull that query result data into Alteryx via the tableau input tool. If you try you will get the table does not exist error. The solution is to query the data from say snowflake directly via the data input tool or In-database tools( I used the data input tool). then use the tableau output tool to push the workflow results to tableau. Now any data that you push to tableau via the tableau output tool will be retrievable via the tableau input tool. to make this all work you must configure the tableau output tool as follows: 1) first make sure to set up DCM following this guide: How to: Set up DCM for Designer and Server (alteryx.com) 2) then create a connection to your database of choice, by entering and saving your connection credentials. 3) in the tableau output tool on the data tab click on the Select project option you want, then lower down the select data source you want. the first time you do this select "New Data Source". this is where your data will be pushed to 4) in the Options tab Name your data in the Data Source name field, then Select the Output Option as create the first time you publish the data, and change it to Overwrite for updates to that data in Tableau. Make sure to leave Data Source Metainfo blank, and don't select Encrypt at Rest or local path. In table Mapping in the table name for incoming Connection #1 enter "#1:table1". Finally, leave the Spatial tab options all blank. For the tabluea input tool you must configure it as follows: 1) in the Connect to area select your saved tableau connection 2) in the Data tab Select your Project(Tableau folder), then Select Data Source, that you created and pushed to Tableau with the tableau output tool with the above steps. In the options tab enter "table1" in the Anchor #1 Table Mapping field. That's it. Good luck and hope this helps others

Potential bug with Alteryx Designer 2022.1 and Tableau Output v1.3.1 (and possibly earlier versions): * Tableau Output tool does not support spatial data.* "We are not supporting spatial data at this time. All incoming anchors closed, but plugin has errors". * We've confirmed that this issue occurs on even the latest patch of 2022.1: 2022.1.1.42673 * We've confirmed that this issue does not occur on 2022.3 or 2023.1

@JonathanAllenby There was some issue with the Access Tokens losing their names when updating to new version and syncing. I had to fix all Access Tokens again for it to work.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Tableau Tools

AlteryxProducts

ChatGPT Image May 12, 2026, 02_56_10 PM.png

Tableau Help Page

Use the Tableau tools to read data from HYPER data sources, create a HYPER data source, and save it to Tableau Server or locally.

Current version

Tableau Tools v1.3.1 (July 19, 2023)

Compatible with Alteryx Designer and Server 2021.4.2 Patch 6, 2022.1 Patch 4 and later.
Requires AMP engine.
Alteryx Server requires stored credentials in DCM to run workflows.
Fixed issue where Tableau Output wrote Null values as “nan” for float data types. (TPM-2210)

Known Issues

The tool becomes unstable when uploading dataset larger than 3GB. (TPM-2121)
The refresh button isn’t working for either the Tableau Output or Tableau Input tool. (TFLN-1436)

Previous versions

Tableau Tools v1.3.0 (June 30, 2023)

Compatible with Alteryx Designer and Server 2021.4.2 Patch 6, 2022.1 Patch 4 and later.
Added new Tableau Input tool to read data from HYPER data sources.
- Live data sources aren’t supported.
- Only data sources created with the Tableau Output tool are supported for reading.
Requires AMP engine.
Alteryx Server requires stored credentials in DCM to run workflows.
Fixed issue where NULL numeric values were converted to 0. (TPM-1546)
- Tableau shows NULL numeric values as 0 by default on dashboards.
Fixed issue where NULL string values were converted to empty string. (TPM-1528)
Fixed issue where DATE was converted into STRING. (TPM-2138)
Fixed issue where Designer ran indefinitely or crashed when DCM was used. (TPM-1986)
Fixed issue with error “The system could not find the path specified” when multiple Tableau Output tools were used on canvas. (TPM-1915)

Known Issues

Tool becomes unstable when uploading dataset larger than 3GB. (TPM-2121)
Refresh button is not working for either the Tableau Output or Tableau Input tool. (TFLN-1436)

Tableau Output v1.2.1 (March 31, 2023)

Compatible with Alteryx Designer and Server 2021.4.2 Patch 6, 2022.1 Patch 4 and later.
Requires AMP engine.
Fixed issue where dates were converted 70 years in the future (TPM-1896)
Fixed issue where Site couldn't be left blank while authenticating via DCM (TFLN-1170)
Data Source and Project lists are now sorted alphabetically.
Minor UI updates.

Known Limitations

Alteryx Server requires the AllowAll value of the SDK Access Mode settings.
NULL values are converted to 0.

Tableau Output v1.2.0 (December 13, 2022)

Compatible with Alteryx Designer and Server 2021.4.2 Patch 4, 2022.1 Patch 2 and later.
Requires AMP engine.
Added support for DCM.
- DCM is required for running this connector in Alteryx Server.
Added support for SpatialObj.
SSL/TLS validation is now performed against Windows Certificate Store.
FIPS capable.

Known Limitations

Alteryx Server requires the AllowAll value of the SDK Access Mode settings.
NULL values are converted to 0.

Tableau Output v1.1.1 (December 23, 2021)

Fixed issue with conversion of boolean and datetime fields.

Tableau Output v1.1.0 (November 03, 2021)

Added support for Tableau Server On-Premise (Tableau Server 2019.2 or later required).

Tableau Output v1.0.1 (September 02, 2021)

Compatible with Alteryx Designer version 2021.3 and later.
Initial release.
Username and Password and Personal Access Token are supported authentication methods.
Create, Overwrite, Append, Update or Upsert multiple tables in a dataset.
Post SQL support.
Proxy support.
Conversion from WKT to Spatial object support.

Known Limitations:

v1.0.1 does not support Tableau Server On-Premise.
When working with multiple tables, a .tds file has to be provided (can be obtained from Tableau Desktop).

This tool uses a .yxi file format. A .yxi file is a package that includes an Alteryx Tool and all of its dependencies zipped into a single file. When this file is imported into Alteryx, the tool is added to the tool palette in the category specified by the tool.

When sharing a workflow that uses a .yxi tool, the tool is not included and must be installed by the recipient.

Accepted answers

All comments

Newt

I'm getting "Credentials denied" for our Tableau Online and I think it's because I'm not filling in the blanks correctly on the Personal Access Token method.

For the Server URL, how detailed should it be?

"11ab.online.tableau.com/mycompanyname/projects/1234567" or something shorter?

What goes in the Site section? I'm not given any choices.

Is there any catch if I've copied the Token Secret to a Word doc and then copied it back out?

Thanks!

eccl318

URL: //11ab.online.tableau.com

Site: mycompanyname

Once you enter your token info the Connect button will activate. Once you connect, the configuration pane will change to allow you to enter the project folder and data source name.

AlteryxProducts

Hi @Newt ,

in your case the "11ab.online.tableau.com" should be URL and "mycompanyname" is the Site.

Copy/pasting from Word could be tricky as sometimes it auto-select the trailing space, so you might be accidently adding a space char to your token. doing the same via Notepad should be general more safe. But I believe the URL/Site is the reason for your credentials being denied.

Should you have any further issues, please do not hesitate to reach out to our customer support.

Vojta

Newt

Never mind.

I tried sufficient variations to get the right combination.

JSE

Hello, I am having the same issue than Newt, it is not possible to access by Token, I would like to know how to fix this issue.

eccl318

@JSE Not sure what you mean by 'it is not possible to access by Token'. Are you indicating you have been switched to SSO, generated a token, using that token and can't successfully publish to Gallery?

cleigh

I'm trying to use the personal access token to configure the Tableau Output Tool. There are two messages that come through, the second of which is an error:
1. Inserted 1000 rows into 'table1'

2. Connection to platform was unsuccessful.

What am I doing wrong in configuring this tool?

The connection was successful in the configuration pane when I entered the Token Name and Token Secret...

My company uses SSO, so I think that's why the Username/Password option doesn't work for me.

Any help would be appreciated!

VojtechT

Hi @cleigh , that seems like a proxy issue. Try to follow this article: https://community.alteryx.com/t5/Alteryx-Designer-Knowledge-Base/Connection-Errors-with-Python-based-Connector-Tools-when-running/ta-p/460217

Emil_Martensson

Hello! When using the tool Null values in Integer columns (only tested with Int64 so far) are converted to 0. When creating a local hyper file and uploading it manually to our Tableau Online server, Null values are kept.

In our old Tableau Server environment Null values are also kept, so I believe this issue is tool related.

stylem

Why does the Tableau Output Tool stay in the queue and not start when I schedule it with Alteryx Designer add-on Automation?

VojtechT

Hi @Emil_Martensson , thank you for reporting the issue. We're looking at it and will try to fix the issue as soon as possible.

VojtechT

Hi @stylem , please reach out to our customer support. They should be able to help you with your issue.

dbmurray

Hi all.

I would love to use this tool all the time, but it seems very prone to failure.

9/10 times it doesn't work for me. Current error I get trying to publish locally is 'name may not be empty'. But I cannot find the corresponding configuration option for this error.

Other issues that occur with using the tool include frequent writing of errors to a log file which seem to fill up with Python errors.

I'm happy to send on logs to the appropriate person, but it would be appreciated if more informative error messages could be presented to the user otherwise it's difficult to troubleshoot.

contoist

I have a dataset of 10.8GB (11 Million Records). This dataset writes out to a hyper file just fine to be used on Tableau Online. However, it doesn't seem to work with the Tableau Output Tool and crashes my alteryx workflow or errors. I have other Tableau Output Tools that work just fine, just with smaller datasets. Is this a known issue, or are there any workarounds to this? Thanks!

dbmurray

Hi all

I have had a few minor frustrations behind this tool, particular around this annoying 'error' where the tool would complain about 'name may not be empty'. I kept running into this and it was so frustrating, I stopped using it. But after a chat with a colleague of mine who'd been using it for a while (shout out @caitlynmcintyre ) , they guided me in the correction direction.

Turns out if you click on the 'options' config in the tool at any point after originally configuring it, the tool will delete your previous table name configuration.

To demo this with pictures:

1. Here' is a simple data source of cities connected to the tool. Note I have named the connection

Step 1.png

2. For this example, I use it locally and point it to a local .hyper file.

Step 2.png

3. I config the table mapping - nominating the connection to output a table within the .hyper as "Cities Table"

Step 3.png 4. Say then I want to push a new table of data into the Tableau Output Tool, called countries, I repeat the process.

Step 4.png

5. However, when I then go to config the new table, the OPTIONS tab has removed the previously configured 'cities' table. This was the source of my original issue - I had failed to notice that the output table name had been removed.

Step 5.png

6. Running this workflow without updating the table names in the options tab of the Tableau Output Tool will result in Alteryx throwing an error like this.

Step 6.png

7. Easily solved by re-entering the table outputs in the options section. However somewhat frustrating if one has to go do this every time the options tab is clicked in the configuration of the tool

Step 7.png

Perhaps this was super obvious to many others, but I didn't notice it and I almost just gave up using it because I assumed it was broken. Hopefully if anyone runs into the same issue, this post should help.

@AlteryxProducts I don't know if you're the primary developer behind this tool, but this might be something to consider - I'm unsure why the tool removes the table name config for previously mapped tables as soon as you click the 'options' tab - or if that the intended behavior - but it seems very unintuitive to me, but something that I'm sure those who love this tool would appreciate being tweaked.

caitlynmcintyre

@dbmurray such a good and detailed explanation of a really frustrating problem! @AlteryxProducts the tool appears to already be picking up connection names into the Table Name field, updating the tool to use connection name if no Table Name is entered would be a game changer and make this a 10/10 tool. Currently the Options config is a really frustrating barrier to entry.

Linas

@cleigh, the solution provided here Connection Errors with Python-based Connector Tool... - Alteryx Community seems to fix this issue. @AlteryxProducts, could we please have the certificate modified as shown in the solution?

Esolano

Hi everyone,

I'm having a trouble with Tableau Output tool. When I run a workflow that contains a Tableau output tool, my computer's RAM reaches its limit and Alteryx Designer stucks

I attach other pictures of the issue

This issue causes you to be unable to load data into Tableau.

I appreciate any help with this.

Thanks!

Linas

@AlteryxProducts Can this tool be run in a workflow from Alteryx Gallery?

patrick_digan

@AlteryxProducts @VojtechT Cool tool! I have a similar question to @Linas . A user setup the tool with a PAT on their machine and everything worked fine. When they saved it to the gallery, it errored out with this message "Failed to signin to Tableau." I logged onto the server box and opened the app in designer, and got this message:

I then had the user send me their PAT, and as soon as I entered it into the tableau tool, it was now functioning on the server box. I compared the xml, and see that: even with the same token, the user's machine and the server box are storing a different TokenSecret:

User machine:

Server box:

So it looks to me like the encryption is user/machine specific, and thus saving to the gallery is not exactly viable. Hopefully I'm missing something!

eccl318

@patrick_digan We have successfully published and use the tool on gallery. A couple of points (many of these may not be an issue in your case but, quite honestly, it is becoming more difficult, in my opinion, to understand everything that is going on in any particular situation):

1. We set up generic PATs in Tableau rather than using individual PATs to ensure workflows don't break upon personnel changes.

2. Make sure the same tool is installed on gallery and installed so all users can access it. Again, we implemented early and the more recent versions may automatically handle this.

3. We initially could not publish due to a Python sharing error and had to make a change to our registry files. Again, I believe this might be handled with the more recent versions. Sounds like you're able to publish so that's most likely not an issue.

4. Make sure to package the tool into the workflow. If it runs fine on the individual designer but not on gallery, that suggests the server machine doesn't have access to the correct PAT. My first suspect would be that the tools weren't packaged.

I'm still not a fan of the new tool. We continue to receive errors from it which disappear when we manual rerun from gallery. My guess is that is mashes up against another workflow running with the same tool and confuses the server. However, it's a manageable issue.

LizPerry

@eccl318 how do you do no. 4, how do you package a tool into a workflow?

patrick_digan

@eccl318 Thanks for the info! it was #3 with the registry that fixed our issue. @michaelhakansson has a good post about the fix here, as well as @brucedataguy over here.

You always have to be super careful when changing the registry. The registry change has to be made on both the designer machine and the server machine. I don't have admin rights on my machine and had to get IT involved into to use regedit as an admin.

While the above posts proved more details, the fix is:

Spoiler

Type regedit in Windows Start Menu
Browse to the folder location: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\SRC\Alteryx
Right click and select New > String Value
Set the KeyName to PythonAllowHideEncryption and the Value to true

shaun_aa

The current version of this tool (1.1.1) does not work with Tableau's Ask Data feature. When the source is posted to Server, only the record count / Number of Records field is populated. I worked through this with Alteryx Support and determined the root cause is in their source code.

Aparker8709

Similar to @Emil_Martensson's comment above, I'm getting errors on Null date fields. Will there be a fix implemented? I'm on the newer version of the tool, has anyone had better luck with the older version?

Jon-Knepper

I had issues connecting to EXISTING data sources and outputting to them with Date Time fields. I was able to resolve it by converting all date time fields to strings, but this causes you to have to update them on the Tableau side which is a pain. I did notice that this error does not appear on NEW data sources. My theory is that the old publish tool that used only Username/Password wrote those fields differently to the server and now the server is expecting that for existing sources.

Aparker8709

Interesting. So I could delete out an existing datasource, republish with the same name, and then return to overwriting it each time without errors?

Jon-Knepper

That is an interesting thought. When I tested it I was able to create a new source and write a sample of the same exact data that was erroring out with no issues. I got the same results when I overwrote to that newly created data source.

One thing I am not sure is how Tableau would handle any existing dashboards or reports linked to that data source. In the past I didn't think it was that easy to delete it and write back with everything being fine, but I could be wrong (I hope I am). 😀

Aparker8709

I tried out creating new datasets and as you said, it worked without errors. But when I swap to overwrite the newly created dataset, I get errors for the null dates and it won't publish over the dataset. I changed my date fields to strings and it worked, but I am not looking forward to adjusting dates in all workbooks. I'm having the same issue as Emil with null numbers turning into 0s too. There are many cases where I need to be able to distinguish 0 from null. At this point I can't justify swapping to this tool. I've swapped the rest of the company over to single sign on but the two of us who publish to Tableau from Alteryx will stay on the normal Tableau log in for now. Hopefully they make adjustments to this tool or create a better option.

dbmurray

I'm now also getting an issue with date fields - I'm having to convert them to strings in order to output using the tool.

Quick Links

Popular Tags

This months top contributors

atcodedog05 19598

Qiu 15906

binu_acs 15783

MarqueeCrew 13709

apathetichell 13703