Jetzt downloaden
This version is available from the Customer Account Center.

24 Jul, 2014
Tableau Desktop (Back to top)
Issue ID

SAP BW calculations that mixed strings and numeric data showed as valid in Tableau Desktop, even though SAP BW does not support calculations returning strings, and the calculations generated errors. Tableau Desktop now marks these non-numeric calculations as invalid.


Teradata connection performance is improved for connections that include fields marked as not Null.


Fonts available in the Edit Label dialog (available by clicking Label in the Marks shelf and then clicking the ellipses next to the Text box) did not always appear in the Font dropdown list in the label formatting window (available when you click Label in the marks shelf).


Switching to a worksheet after clicking the home icon in the upper right sometimes changed the connection icon to the live connection icon.


With cube data sources, you could not filter on calculated fields that used the SIGN function.


Specifying an odd number of Stepped Color steps on a color palette sometimes displayed an extra color.


Tableau Desktop didn't recognize some Japanese words for geographic locations. For example: アメリカ (United States of America), チャイナ (China), ジャパン (Japan), and 新加坡共和国 (Singapore).


When copying and pasting a sheet to another workbook, Tableau Desktop did not always properly paste parameters into the target workbook. A parameter in the target workbook could be maintained and this could alter results of calculations that included the parameter.


Passwords for Amazon Redshift data sources that contain percent symbols are now correctly handled.


When using an EXASolution data source, you could not sort by a dimension.


When a field was on the Pages shelf in a map view, mark labels sometimes appeared only on the first page.


On zip-code filled maps, the 04090 zip code displayed in both Maine and Puerto Rico.


When using a secondary data source, a percentile aggregation in a calculated field caused an "Unexpected Error Incorrect data type" error.


Custom images sometimes appeared blurry or broken when scaled up to a larger size than the original.


Tableau Desktop was not using temporary tables with Amazon RedShift connections. Temporary tables improve performance in some cases.


When republishing a workbook that used an extract, you were not prompted for a password even when the original workbook had included an embedded password. Subsequent attempts to refresh the extract would fail due to an invalid (missing) password.


Using a calculated dimension whose value is determined by a parameter results in performance issues due to an unnecessary join and subsequent queries.


Copying sheets from one workbook and pasting them to another workbook sometimes created duplicated shapes on the shape palette.

Tableau Server (Back to top)
Issue ID

When refreshing OData extracts, an “Out of memory” exception or an “HTTP Request timed out” error sometimes occurred.


On SSL-enabled server running Tableau Server, using Java client code to generate a URL with a trusted ticket sometimes caused an exception "handshake alert: unrecognized_name".


On a site with a storage quota, administrators with a language other than English set in User Preferences could not edit site settings.


Opening a view with a connection to a Teradata data source that prompted for credentials sometimes failed with an "IllegalArgumentException" error.


Images in a subscription email for a workbook that had a filter applied to all views showed the filter applied to only one of the views.


Opening a published workbook sometimes resulted in a "TableauException: Could not send Query (connection dead)" error and the workbook becoming inaccessible until Tableau Server was restarted.


After upgrading Tableau Server in a distributed environment, PostgreSQL drivers were updated on the primary but not on the workers, and no message explained this. You must upgrade the workers manually.


Exporting a published view with two or more measures on the Rows or Columns shelf resulted in duplicated exported rows. The number of times the rows were repeated was based on the number of measures on the shelf.


The 64-bit version of Tableau Server did not install the 32-bit PostgreSQL ODBC (psqlodbc) driver that was required for Amazon Redshift connections.


Accessing the Data Sources page by administrators was restricted and displayed an “internal error” message, whereas non-administrative users could access the page.


The Java component used by Tableau Server was updated to 1.7.0_60 to address multiple critical security vulnerabilities described in an Oracle Critical Patch Update.


The error "org.postgresql.util.PSQLException: FATAL: role" repository "does not exist" sometimes appeared in the repository.log file during Tableau Server installation.

This version is available from the Alternate Download Site.

non-humans click here