Télécharger dès maintenant
This version is available from the Customer Account Center.

Cette version contient une mise à jour de sécurité cruciale qui corrige le problème de sécurité Heartbleed.

Heartbleed est une faille de sécurité critique dans la bibliothèque OpenSSL (version 1.0.1). OpenSSL est un logiciel open source utilisé par de nombreux sites Web et logiciels, y compris par certains produits Tableau. La faille Heartbleed permet à un pirate distant de lire la mémoire d'application d'un serveur ou d'un client. Cela peut permettre la lecture des clés de cryptage et permettre ainsi le décryptage des données obtenues en interceptant le trafic. Pour plus d'informations sur les mises à jour de Tableau concernant ce problème, les produits Tableau concernés et la mise à niveau de Tableau, consultez l'article de la base de données Problème Heartbleed.

Date de publication:
10 Avr, 2014
Numéro de version Tableau Desktop:
Numéro de version Tableau Server:

New Capabilities

Added support for Vertica 7.0.

Added support for Microsoft SQL Server Parallel Data Warehouse V2.

Tableau Desktop (Back to top)
Issue ID

When connecting to Google BigQuery, connecting to multiple tables would sometimes cause the error: Table name cannot be resolved: dataset name is missing


Corrected an issue with relative date filters for Hive data sources.


It was not possible to establish connections to Cloudera Hadoop when Impala was being used for Kerberos authentication.


Corrected a problem connecting to PostgreSQL and RedShift databases with SSL enabled.


A security issue in libcurl was fixed, having to do with re-use of wrong HTTP NTLM connection. This could affect certain network connections not handled by database drivers.


Implemented a performance optimization for retrieving data from Vertica databases. The change was to increase the fetch buffer size from 128k to 8,192k.


Updated geocoding to improve placement for a number of locations.


Corrected a problem when retrieving data from SQL Server where the datatype of the column is an unsigned tinyint.


Using TDC files to customize connection options for Hadoop Hive connections was not always working.


Tableau views embedded into other pages where the parent page URL included the # character in the URL path would truncate the URL after the #.


Fractional second date fields were being truncated at about 1024 characters. They now get truncated at 16,383 characters.


After refreshing a Salesforce.com extract, the following error would occur: "Error parsing filter for field 'YEAR(Created Date)', ignoring filter". The error would occur only if there was a date field on the filter shelf.


When quick filters from secondary data sources were exposed on dashboards and were not set to have a fixed height, the filters expanded to fill all available space in the layout container.


Quick filters would not be displayed after a view was exported as an image or PDF file. The issue would occur only when table calculations were being used to return string values that were being used as filters.


In certain cases connecting to Netezza databases could incorrectly show null values for columns of data. The root cause was trailing spaces sometimes being used in the SQL alias names generated by Tableau.


With data blending, user calculations using cube measures and having non-additive aggregate derivations would sometimes display and log an “Internal Error” message (without any additional details) in Tableau Desktop. Under such circumstances, relevant fields and views are now correctly flagged as "invalid."


When using the VAR function in a large worksheet (50,000,000 or more records) with an extract data source, the function would return a negative value


Converting a single table Excel connection to a Custom SQL connection would sometimes result in a JET database error.


Essbase connections that time out are now silently re-established. If a connection attempt fails, an error message displays.


Queries generated when using action filters could lead to performance issues. The problem would occur when clearing the filter.


Connecting to Amazon RedShift databases where the database is running on a single node configuration would not work. The error returned was 'Fetch size 10000 exceeds the limit of 1000 for a single node configuration. Reduce the client fetch/cache size or upgrade to a multi node installation.'.


Publishing a workbook that connected to a Microsoft SQL Server Parallel Data Warehouse data source erroneously displayed the "Impersonate via embedded credentials" option.


Mark labels would sometimes overlap. The issue would affect vertical labels that use multiple text styles in the same line.


When adding a calculated field to the view with a PostgreSQL database connection, the following error would be returned: "Error: function strpos(interval, text) does not exist".

Tableau Server (Back to top)
Issue ID

Installing the 64-bit version of Tableau Server would install the 64-bit version of Tabcmd but not the 32-bit version. Both versions are now installed.


Parameter controls where you type in values would not autocomplete if the parameter had more than 199 values.


Addressed a "Denial of Service" vulnerability in Tableau Server's Ruby on Rails code.


On Tableau Server, a vertical line (slice/angle) would appear on pie charts that used Measure Names/Measure Values with null values; in this case the pie chart should either be full or empty.


In certain versions of Firefox, views would sometimes take a very long time to load or to redraw after scrolling down. Other browsers performed these actions quickly. Firefox versions now perform the same as the other browsers.


Workbooks that connected to cube data sources would open with intermittent errors from the data source. This was due to numerical counters being added to measures, and to calculated measures in particular.


Extract refreshes would hang in the background process until the process was manually terminated by a user.


On Tableau Server, accessing a report that points to SQL Server Analysis Services 2012 would sometimes result in the error: "Analysis Services database error 0x80004005: An error was encountered in the transport layer." After clicking "Yes," the user would get routed to the other available server and the report would refresh.


Working with a single workbook over a long period of time which includes navigating between tabs could encounter a CSS rules limit in Internet Explorer versions 6-9. Tableau was adding the CSS rules on each tab switch within the workbook which could accumulate to the IE limit. We now clear the unneeded rules when leaving a tab.


When restoring a Tableau Server backup from a production environment running Tableau Server 7.0.8 to an environment running Tableau Server 8.0.0, the backup would fail with an error: “ActiveRecord::JDBCError: ERROR: could not create unique index "users_luid_unique" Detail: Key (luid)=(8da1bbdf-10dd-4f5d-ba9c-7c732f1cf7a7) is duplicated.”


Invalid JSON syntax caused issues with filters in published workbooks.


When publishing a workbook to Tableau Server, all users and groups would be displayed, including users and groups that were not associated with the selected project.


After exporting a Tableau Server view to a PDF, the server view could then display broken image icons in place of the proper view elements.


On Tableau Server, selecting "Assign Permissions to Contents" would not work as expected. For example, permissions assigned at the project level were not being applied to the workbooks in the project.


When using SAML configured to access multiple domains in AD, logging in with domain\username would fail.


In Tableau Server, mark labels would sometimes overlap. The issue would affect vertical labels that use multiple text styles in the same line.


Quick filters on hidden sheets would not be not exposed when a workbook was downloaded from or viewed on Tableau Server 8.0 or 8.1.


Under heavy load, Tableau Server could generate frequent "502 – bad gateway" errors.

On Tableau Server, quick filters would not be displayed after a view was exported as an image or PDF file. The issue would occur only when table calculations were being used to return string values that were being used as filters.


Custom logos would not display on gateways located on worker servers.


On Linux, the Tableau Data Extract API would return an error after running MakeOrder. The error text would begin: "com.tableausoftware.TableauException: server did not call us back".


The Tableau Server background process wasn't executing certain tasks in the PostgreSQL database, resulting in outdated cluster configuration details being kept instead of discarded.

Tableau Mobile (Back to top)
Issue ID

The Tableau Mobile client would not always recognize changing between sites and it would return the error: "Couldn't load all data from Tableau Server. The operation couldn't be complete. (SURELErrorDomain error - 1012.)"