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

27 Aug, 2013
Tableau Desktop (Back to top)
Issue ID

Implemented a significant performance optimization for worksheets that include totals. Test workbook results showed reductions in time to display from 46 seconds down to 26 seconds in one case, from 25 seconds down to 11 seconds in a second case, and from 5 seconds down to 2 seconds in a third case. Only worksheets that include totals benefit from this optimization, and results will vary, but we are seeing significant improvements in a number of scenarios.This change affects both Tableau Desktop and Tableau Server.

The product could become unresponsive after a wildcard filter was applied with a large data set as it was incorrectly querying for the entire domain rather than the subset specified by the filter.

When automatic updates were paused, quick filter menus would collapse rather than displaying all relevant values and maintaining the correct card height.

When automatic updates were paused and selections on a multiple values quick filter selected, resuming automatic updates caused the filter to re-select All instead of using the correct selections.?

Added a new TDC option: CAP_SUPPRESS_QUICK_FILTER_ACCELERATION_VIEWS. This option prevents Tableau from issuing queries to construct acceleration views for relative values quick filters. This option can be used in cases where product performance was degraded when using quick filters. See Knowledge Base article Customizing ODBC Connections for more information on using TDC files

Date calculations when using Tableau Extracts could result in months being assigned to the wrong quarter due to a discrepancy in how the end of month was computed.

Added support for connecting to EXASOL EXASolution data sources.

Updated the built-in geocoding data with a large number of missing cities and provinces in Turkey and Brazil.

Added support for connecting to Cloudera HiveServer2.

Permanent tables were being generated to support Top N filters. These filters now correctly generate temporary tables. This issue was known only to affect SAP Sybase ASE data sources, and the fix is specific that that data source.

Added support for connecting to MapR HiveServer2.

When using dual axis views combining area charts with either bar, square, or Gantt marks; edges on the area chart could be jagged or pixelated when OpenGL was disabled.

Added support for connecting to Hortonworks HiveServer2.

When using SQL Server impersonation, it was possible under certain conditions for users to access data that they did not have permission to view in the SQL Server database. The problem would occur after one user (user A) logged on, when another user (user B) logged on. The view for user B would, until the database was re-queried, show data belonging to user 1. When vizql caching was set to Balanced/Cache for no longer than 1 minute, the correct data was initially loaded in the view as long as users waited longer than a minute between requests to load the view.

Added support for connecting to Teradata tables that contain spatial columns.

When connected to Hadoop Hive data sources, column names that began with integers could cause an 'EncodeInteger: bad argument' error when creating an extract.

Certain image files added to a dashboard would not resize properly which could cause Tableau to exit with a Runtime Error.

Connecting to a Teradata database with larger data sets or multiple table joins could result in an Invalid Cursor State error.

Opening a workbook which references a font which was not available on the machine could cause the application to unexpectedly exit.

Exporting a dashboard to EMF format would sometimes result in inconsistent legend heights.

When a mark type was set to line, setting a specific mark's label to 'never show' had no effect and the mark label continued to display. It was also not possible to turn labels on for other points on the line.

When connecting to a Greenplum data source, a connection that had timed out was not being handled properly and would cause a Could not send query (connection dead) error.

The More/Fewer quick filter indicator did not change even though the selected change was reflected in the quick filter.

A 'no such function: Sum' error could occur and the application could unexpectedly exit when using a calculated field that uses the REPLACE function and fields from a blended data source.

Tableau could stop responding when performing a licensing check because of network permission issues. Tableau now provides a message as to why the licensing check failed (network returned access denied).

Dragging-select zoom on a map would not properly zoom to the selected location.

When connecting to views with a Sybase ASE data source, joins are not being executed correctly.

When a single value dropdown quick filter was set to show Only Relevant Values, the filter would become unresponsive when there were no relevant values to show. The quick filter now displays a No items. message in this case.

Tableau Server (Back to top)
Issue ID

Workbooks containing a filter action which opened another sheet in a new window would sometimes not perform the action correctly once the workbook was published to Tableau Server. The filter action would work as expected when client-side rendering was disabled.

Importing users from an recursive group in Active Directory using tabcmd syncgroup would take a very long time or never complete.

The error messages DataSourceException: The protocol is disconnected! or Communication link failure sometimes appeared when opening a Tableau Server workbook when the workbook met the following criteria: it had action filters, it was connected to an IBM Netezza database, and it was being simultaneously accessed by multiple users.

Modifying a filter while Tableau Server was still redrawing the screen sometimes resulted in a Session Ended by Server error.

In Tableau Server and Tableau Public, dashboards were not updated when modifying a DATETIME parameter slider control.

A published workbook that connects to a Microsoft Analysis Services database and contains multiple filters would not display data when refreshed if two or more filters had been changed.

Publishing a workbook to Tableau Server using an extract from an Excel data source, could result in an Unknown data source class 'excel' response code 500 error.

Hidden dimensions were visible when web editing a workbook that connects to a Microsoft Analysis Services database.

Users could sometimes not log in to the server when the domain nickname did not match the NetBIOS domain name.

The default Java memory setting was increased to help avoid wgserver out of memory errors.

Data engine synchronization activities on a Tableau Server worker would sometimes consume significant CPU resources, requiring a restart of the primary Tableau Server.

When sorting Sites by % Quota Used, sites were not always sorted from the greatest to smallest percentage.

In some workbooks with complex dashboards, filtering data from a worksheet to a dashboard would cause an Unknown VisualID error when the workbook was opened in a web browser.

When publishing to Tableau Server 8.0, views that had the quick filter Include/Exclude option disabled in Tableau Desktop would still show that option on the server.

If the Default project was removed from Tableau Server and a new site was created, the error message 'Tableau Server encountered an internal error' would sometimes display.

In some cases, users with only viewer permissions could browse to the Groups list via the project permissions page.

URL Actions that contained variables as part of the URL would not work properly when the workbook was published to Tableau Server.

While using Chrome or Firefox web browsers on Windows 8, clicking single-select quick filter menus or toolbar buttons with a mouse would not work if your computer was compatible with a touch screen.

Default worksheet shading was not displaying consistently after workbooks were published to Tableau Server. The color would display correctly when browser rendering was disabled.

The Tableau Server Administrator Guide was no longer available in PDF format. The guide can once again be downloaded from http://www.tableau.com/support/help.

In earlier versions of Tableau Server, when the VizQL server process ran out of memory, it would become unresponsive, then it would restart. Any server users who were using that process would receive the error message Session ended by server. Now, if a user session requests more memory than is available on the VizQL process, that user will receive an Out of memory message and the VizQL server process will remain responsive for all other server users.

When using the Google Chrome browser, text would sometimes be clipped.

When a workbook on Tableau Server used a parameter to choose the dimension on Color, combined with filters that also modify color, the colors in the view would not update correctly when the workbook was opened, even though the legend would update.

Tableau Server subscription emails would sometimes fail to post if the SMTP server was using SSL.

Using tabcmd to export a PDF with the fullpdf option would cause a nesting of 20 is too deep error message when the workbook contained complex visualizations. The maximum depth has been removed to accommodate exporting these types of workbooks.

If a view used a URL filter in combination with a parameter and the parameters display name was different from its value, the URL filter would sometimes display an incorrect value.

In some cases, subscribing to a custom view would deliver the original view in the email instead of the custom view.

When using Internet Explorer 8 to open a dashboard on Tableau Server, switching between tabs could cause images to disappear from the dashboard.

When using Internet Explorer 8 and Tableau Server with Active Directory and Enable Automatic Login, clicking between dashboard tabs would result in an Unknown Visual ID error.

Exporting an image from a published workbook using the URL option refresh=y would not show the latest data in the exported image.

When a Tableau Server workbook opened to a dashboard that was published with fixed axes (pin icon), the zoom controls would sometimes not work as expected.

On servers configured to use Active Directory for user authentication, users without a full name set in Active Directory would fail with a NullPointer Exception: Null TString error. The friendly name is now set to the username in these cases.

Calculated fields would sometimes return incorrect results after publishing to Tableau Server when the formula used COUNTD and referenced a field from a secondary data source.

This version is available from the Customer Portal.