This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
Use Tableau Output tool to create a hyper dataset and save it to Tableau Server or locally.
Compatible with Alteryx Designer and Server 2021.4.2 Patch 4, 2022.1 Patch 2 and later.
Requires AMP engine.
Added support for DCM.
Added support for SpatialObj.
SSL/TLS validation is now performed against Windows Certificate Store.
FIPS capable.
Known Issues
Alteryx Server requires the AllowAll value of the SDK Access Mode settings.
NULL values are converted to 0.
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.
Known limitation:
v1.0.1 does not support Tableau Server On-Premise.
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.
Having the same issue as @Emil_Martensson (null numeric values automatically converted to 0's instead of keeping them as null). Has there been any updates on this? Thanks!
@JesusER @Emil_Martensson I think that error might be to do with the rules of the Tableau Hyper API - I don't think it allows you to store a value as 'null' if its numeric/bool. You'll have to use string unforunately and deal with it in Tableau.
Is there a way for this tool to recognize who on Alteryx Gallery is running the workflow and use their credentials to authenticate and publish to Tableau Server? Just because the Alteryx developer had access to publish to Tableau doesn't mean the person who shared the Alteryx workflow would have the same access.
You can test the 1.2.0 Beta version.
@elsastark I have this EXACT problem as well. Tool works fine locally, won't work on gallery.
@barcris Where is this 1.2.0 beta version?!
@dbmurray
You can download from the following link, but you must log in with the alteryx user account, or if you wish I can send you a message, as it does not allow me to attach.
Regarding this Tableau Output tool, I've tried the link above to the Tableau Help page, and it says Access Denied. Anyone else getting this? I'd like to understand some of the configuration options, for example, the Data Source Metainfo TDS file - what are some use cases of why this option would be used and how you use it. Thank you.
We created a "universal" credential set and publish most workflows using those (rather than individual user credentials). At the time of publication, you have to select that set of credentials rather than what you might be using in the local workflow. This allows analytical apps to run regardless of who signs in and also keeps scheduled workflows from breaking as individuals come and go. We did the same with the Tableau tokens.
Having an issue with v1.2. The output tool creates a temp folder, but looks like it tries to make the same folder twice, resulting in a "FileExistsError" which stops the flow.
I'm having an issue with this tool where persistent crashing occurs if I try use it inside a tool container. Enabling the container after it being disable will hang alteryx. Trying to move it out of the container will cause the same thing.
This tool is very handy, I just wish it wasn't so error prone.