Bring your best ideas to the AI Use Case Contest! Enter to win 40 hours of expert engineering support and bring your vision to life using the powerful combination of Alteryx + AI. Learn more now, or go straight to the submission form.
Start Free Trial

Alteryx Designer Desktop Discussions

Find answers, ask questions, and share expertise about Alteryx Designer Desktop and Intelligence Suite.

Issues with Publishing to Tableau Online with TDS file

jvaucher0804
7 - Meteor

Hello! 

 

Having some issues publishing to Tableau Online using the Publish to Tableau tool. 

 

I currently can publish to Tableau Server (2020.3.4) via Alteryx Designer (2021.1) with the same .TDS with no issues.

 

Is there a known issue or a workaround that I need to do with the .TDS file for publishing to Tableau Online?

 

Thanks so smuch!

Jory

 

jvaucher0804_0-1616621946570.png

Error: Publish to Tableau Server (8): Tool #252: Tool #4: Tableau Server API Request (Publish file) Error Code 400011: Bad Request -- There was a problem publishing the file '21403:59520b319c10444abc0135237f520b67-0:0'.H

14 REPLIES 14

Hi - yes, I found a workaround: when I run Alteryx as an administrator I have no issues uploading to Tableau Server. Took me a while to figure that out; not sure what changed but I didn't have to do that in the past... 

Hope this works for you!

sm7746
7 - Meteor

Hi @Frank_Reijgersberg,

 

Thanks for the reply. Unfortunately that doesn't work for me when I try to publish a Hyper format with a TDS file included.

 

Is that what you are doing?  

 

I am running Alteryx 2021.1.4.26400, and publishing to Tableau Online  

 

Hi sm7746,

 

No, in my case there's no TDS file included...

sm7746
7 - Meteor

Hi @SabrinaCB 

 

Is there any workaround available for the error reported by @jvaucher0804 ?

 

I am running Tableau Desktop 2021-1, Tableau Online and Alteryx 2021.1.4.26400

 

The same error is happening for me in multiple workflows. I have tried TDE format & Hyper format, both with TDS file 

sm7746
7 - Meteor

@SabrinaCB @jvaucher0804 

 

Is there any update or workaround for the error reported at the start of this thread

Labels
Top Solution Authors