Issues with Publish .tde to Tableau Server Tool; FileName/Not Published but No Error

A couple of issues I've noticed from my first day playing with the Publish to Tableau Server tool.

1. There were a couple of times(First couple of times I ran it) where my flow finished running without any errors, but the .tde was not actually published to the server. When I went into the log, I could see that there was a parentheses next to one of the entries upstream that said it was stopped by a tool downstream.

I'm not sure what the issue was with this one. It hasn't errored out on me since the first couple of runs, but it is a bit alarming to me that it could not publish the .tde and also not cause an error flag when doing so.

2. I have a dataset that I create/append to each week, in which I insert the file name("FileName" default) as a field in the data in order to create a trending view. When I left this field with the default header, I could see it going into the Publish to Tableau Tool, but it was not coming through my extract once I linked it up to Tableau to rebuild my dash.

For the second issue, I went in and changed the name to "File Name" from "FileName" and that made it show up in the .tde.

Publish

Error Message

Tips and Tricks

Tableau

Accepted answers

MacRo

Yep, the key is the "Refresh project name list" checkbox -- if that is checked, then it *only* updates the list of projects available in the dropdown above it. Nothing will be published to Tableau Server when that is checked.

(In the future we hope to make this a bit more streamlined, but for now you can either manually enter in the project name, or suffer the two-step process of refreshing the project name list and running then workflow, then unchecking it, selecting the project, and running again to publish.)

All comments

MacRo

Hi @FFFool, thanks for posting this. As far as the first issue, that's something we've not yet heard so far, and so we'll need more to go on to get to the bottom of it -- if you run into this again, can you take screenshots of your logs and configuration?

For the second one, this is indeed an oversight as the macro creates a field called "filename" that gets added to the input datastream. Sorry for the inconvenience this may have caused you, but we'll get a fix in and will report back when it's been updated on the Gallery. Thanks again for reporting this!

FFFool

Hey MacRo,

Attached is the log in Excel and snapshots of the Config(Blurred Name/Password but the same name/password work on other workflows) and Output saved in that file. There are a good amount of Warnings, but most of them should be there based on what I'm doing(Also exporting to an error file items that don't meet the join requirements). Notice that the Publish to Tableau tool seems to process before everything else, but never actually publishes to the server at the end. There are data conversion errors, but no regular errors that cause the workflow to stop or show up as red at the end.

Thank you,

Publish to Tab Error.xlsx

FFFool

So, I seem to have fixed my issue, but I'm not sure which of 2 things I did managed to fix it.

The first thing I did was uncheck the box that says save connection history.

The second thing was I selected the option to select project name, rather than enter project name. I had selected that before and selected the Refresh project name list... box. I unchecked that, and then went back to Enter project name.

Ran my workflow and it published no problem. I'm thinking it was probably the Refresh Project name list that did it, but I don't know. Either way it's odd that refreshing the list or saving the connection would override the actual publishing of the data source to Tableau.

Now that you know the causes, hopefully you can put some of this information to good use.

Thanks again,

Quick Links

This months top contributors

hhaigh1 280

FláviaB 262

JORGE4900 235

caltang 177

DanM 167