Download Now

This version is available from the alternative download site.

Release Date:
June 11, 2013
Desktop Build Number:
Server Build Number:
Tableau Desktop (Back to top)
Issue ID

Views and dashboards that connect to data extracted from a Tableau Server data source would show as empty when opened in Tableau Reader. The problem occurred when the view contained a parameter-based table calculation.

Improved memory usage with both Tableau Desktop and Tableau Server.

When connected to DB2 databases, custom date bins on a secondary date dimension caused an error.

When connected to a multidimensional data source, the application would unexpectedly exit when filtering on a hierarchy that does not have any levels.

Dashboards with text at the top and bottom of views were sometimes partially cut off and misaligned with the border of the view.

Fixed an issue in which the borders of custom polygon marks on a filled map were not as smooth as they were in previous versions.

Improved filter action behavior in Tableau Desktop.

Printing a dashboard to a PDF that spans multiple pages sometimes resulted in PDFs that were missing some elements.

Fixed an issue where the initial connection to an IBM Netezza database sometimes took longer than expected.

Tableau Desktop no longer stops responding when it's running on a computer with OpenGL graphics acceleration and ATI graphics cards.

Fixed several issues in Tableau Desktop and Tableau Server related to PDFs, including: unusually large file sizes, compared with earlier versions of Tableau; white areas within some PDFs; blank pages when size was set to Unspecified; issues with the color legend displaying in Tableau Server even though it had been disabled in Tableau Desktop; floating legends in dashboards; and fuzziness and illegibility in the PDF output.

When using Tableau Desktop with a data repository pointing to a UNC path, editing shapes would cause Tableau to appear unresponsive.

When connected to a Tableau Server data source, using calculations that use the ATTR() function would cause the data engine error, Invalid field formula due to limitations in the data source.

Highlighting colors on a legend based on the Measure Names field, a set, or a binned measure would cause the view to not refresh properly when switching between values.

An error message sometimes appeared when attempting to deactivate a license for Tableau Desktop and the license would not be deactivated.

The selection indicator would not stay aligned with the cursor as you move the cursor along a line in a view. This issue affected both Tableau Desktop and Tableau Server.

Creating a context filter would fail when connected to Google BigQuery.

An Incorrect data type error would sometimes occur in Tableau Server in workbooks that connected to SAP BW data sources.

Axis rulers (lines that mark the x and y axes in a view) were not displaying.

Version 7.0 workbooks that included a set made from two combined fields caused errors after upgrading to version 8.0. The message, An error occurred while communicating with the data source. No such function: Sum would display after the upgrade.

Addressed an issue in Tableau Desktop where editing A location to add longitude and latitude caused Desktop to become inoperable.

On a computer where Windows ClearType Text Tuner was used to adjust the quality of font rendering, Tableau would stop using ClearType to render text for labels and annotations. Grayscale rendering was used instead.

In Windows 8, sets could not be dragged or right-clicked in the Data window without first re-sizing the Data window to introduce a horizontal scroll bar.

Fixed an issue in Tableau Desktop where Menu Filter Actions were inadvertently cleared when scrolling twice or clicking marks.

Clicking theShow Fewer Valuesoption in a quick filter or the Filter dialog box would sometimes return a null result and the application would appear to be unresponsive.

In workbooks that contain several filters, selecting a drop-down filter, then turning off automatic updates, and then selecting a multiple select filter would result in the filter reverting back to selecting all when the automatic updates were resumed.

Moving a field from the Columns shelf to the Rows shelf sometimes caused the product to become unresponsive, although the action would eventually complete.

WhenRepeat headers and legends on each pagewas not selected in Page Setup, pages after the initial worksheet were printed as blank pages.

When using a workbook with a large number of marks, dragging a dimension to Label and then quickly removing it before labels display caused the view to become inactive.

In some specific cases, workbooks with totals turned on would sometimes cause the application to unexpectedly exit.

Printing to PDF from a Tableau workbook that uses transparency may result in blurry output in the PDF file.

After publishing a workbook, switching tabs in the preview window would not load the views if the default web browser was set to Internet Explorer 10.

Exporting word clouds using Print, Print to PDF, or Copy Image were not rendering correctly when the base size of the text was larger than the default 20 x 60 pixels.

In some cases, the application would exit immediately upon launching before a workbook was opened. This issue was caused by corrupt thumbnail images that are used to show the most recently used workbooks on the Start page. Tableau now handles these cases by removing the thumbnail images until the workbook is once again opened and saved.

When running on Windows XP, Tableau Desktop can stop responding when exiting or when switching between workbook tabs. The problem is due to an accumulation of menu handles.

In a view with a sorted dimension, changing selections in a quantitative quick filter would not consistently update the sort order. The sort order now correctly updates based on the filtered values.

Calculations that use the IIF function computed with a calculated string and a constant could result in missing data or a data engine error.

When exporting dashboards to PNG or EMF, text boxes were not always rendered correctly. Some UI elements were overwriting others.

Borders would occasionally be clipped and results truncated on the far right side of dashboards when selecting File > Print > Adobe PDF.

Mark labels could be slow to render when there were a very large number of marks in the view.

When running on Windows XP, the application would sometimes stop responding when exiting or when switching between workbook tabs. This problem was due to an accumulation of menu handles.

The 3rd party tool, RoboForm, could cause the application to unexpectedly exit.

Label text in Gantt charts would sometimes overlap with marks when the axis was set to automatic.

Publishing workbooks with version 7.0 extracts could fail with the error, Tableau Data Engine Error 4: The system cannot find the path specified. This error occurred when the extracts contained very long column names, which created very long file names that were not being truncated to a length that is supported by a version 8.0 data engine. These file names are now truncated correctly.

Tableau Server (Back to top)
Issue ID

An ampersand character (&) in a Salesforce username or password would cause an Internal Server Error.

On Tableau Server, legends for the mapping data layer legend would sometimes appear as an empty box.

Improved performance in retrieving and loading data for SAP BW connections.

When views were published to Tableau Server, excess space was sometimes introduced between mark labels and marks.

For views connected to multidimensional (cube) data sources, clicking on a quick filter based on a hierarchy would cause a Tableau Exception error message.

In certain server configurations, using the command line to append data to a published extract that contained a parameter could cause the application to unexpectedly exit.

An error would occur when a workbook was published by an author who belonged to a Tableau Server group that was owned by a user that no longer existed.

When workbooks were published to Tableau Server, mark labels were incorrectly given the same transparency as marks.

When using the Tableau for iPad application to connect to servers configured to use SSL, a Couldn't load all data from Tableau Server. The request timed out error would occur.

Locales that use English but not U.S. English could not load Tableau Public visualizations in either Internet Explorer or Safari. The problem affected both mobile devices and computers.

Tooltips would not display if they had a Menu Filter Action and an invalid URL action.

Optimized performance for some specific cases where the Data Server was slow to respond.

When exporting to PDF from Tableau Server, legends were not always positioned correctly. For example, legends configured to display below the view would be displayed to the right of the view. This issue only occurred after clicking the Export button at the bottom of the view and not when appending PDF to the URL.

When scrolling a view while editing a workbook on an iPad, marks would scroll correctly but row and column labels would not.

Favorites could not be set or deleted in Internet Explorer 7, 8, or 9 when Security Support Provider Interface (SSPI) was enabled.

When editing views on Tableau Server with an Essbase OLAP Cube connection, dimensions were not being displayed in the Data window.

On servers configured to use Active Directory authentication, custom views that were added as a Favorite would not load when the link in the Favorites menu was selected. The link generated a URL with a custom name that was not being handled properly.

In a distributed server environment, some VizQL processes would appear to be underutilized and others appeared overutilized causing Out of memory errors.

Drop-down lists with multiple values would not open upward when the list of values extended below the bottom of the browser window.

The error Tableau Exception: Could not send Query (connection dead) would sometimes display when accessing a published workbook that connects to an Amazon Redshift data source.

Workbooks that contained complex dashboards would cause a memory leak when opened in Internet Explorer 8 or 9.

When a background job was scheduled to run during a time that no longer exists due to a daylight savings time change, all background tasks would stop working.

A Commit called on nested editor error would sometimes appear when changing tabs in Tableau Server.

Assigning the Publish right to a user would successfully complete and then trigger the web browser error, Unable to get property 'text' of undefined or null reference.

For views published to Tableau Server, annotations placed over marks that trigger actions would cause those action to no longer be triggered.

In some cases, activating a license for Tableau Server 8.0 on a Virtual Machine (VM) could fail with the error, No license found for Tableau Server.

When importing Active Directory users from a *.CSV file, the email value was set to username instead of the actual email from Active Directory.

Performance was optimized to decrease the amount of time it takes to open the Users list as an administrator.

Enhanced security support for Tableau Server's PostgreSQL database.

Text in workbooks was sometimes compressed to the point of unreadability when client-side rendering was used.

Passwords containing square brackets caused the error message cannot convert instance of class org.jruby.RubyArray to class java.lang.String. Using an asterisk or curly brackets resulted in a similar error message.

In previous versions, for connections to Tableau Server data sources, acceleration views were cached remotely on Tableau Server. Now they are cached locally on the computer running Tableau Desktop. This change reduces latency and improves server performance.

Tableau Server sometimes displayed an Incorrect data type error message when opening a workbook containing stacked dual axis panes and pages.

Publishing workbooks could cause a 500 Internal error on servers configured with a European locale such as German or Portuguese. The error was caused by the product version being reported incorrectly, which created an incompatible version match between Desktop and Server.

This version is available from the Alternate Download Site.

non-humans click here