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

Tableau 8.1 vous propose des fonctionnalités pour accéder à vos données et les analyser plus simplement, grâce à une conception plus puissante et plus élaborée que jamais. La moitié des fonctionnalités est directement issue d'idées de clients. Cette version propose de nouvelles fonctionnalités analytiques et statistiques, des améliorations au niveau de l'expérience utilisateur, des capacités d'intégration de Tableau Server à d'autres systèmes d'entreprise, des sources de données et une connectivité mises à jour et des fonctionnalités supplémentaires pour les créateurs en ligne et mobiles.

Découvrez les nouveautés de Tableau 8.1.

Date de publication:
20 Nov, 2013
Numéro de version Tableau Desktop:
Numéro de version Tableau Server:
Numéro de version Tableau Reader:

New Capabilities

Added support for Apache 2.4.4.

Added support for selecting a schema when connecting to multiple Amazon Redshift tables.

Tableau Desktop and Tableau Server are now available in 32-bit and 64-bit. Learn more about this change in the following Knowledge Base articles: Deciding Between 32-bit and 64-bit Tableau, Drivers for 64-bit Tableau, and 64-bit with Tableau Version 8.1.

Tableau 8.1 contains many new capabilities in both Tableau Desktop and Tableau Server. See what's new in Tableau 8.1

Tableau Online has been upgraded. You may need to upgrade to Tableau Desktop 8.1 to continue using some features of Tableau Online. See Tableau Online Version Compatibility to learn more about compatibility between Tableau Desktop and Tableau Online.

The version of Apache provided with Tableau Server was upgraded to 2.4.6.

Enhanced Tableau Server's support for trusted tickets. URL-safe Base64 values are now used for trusted ticket strings. Each ticket now has 24 characters by default instead of 9 digits. To use 9-digit tickets instead (as in version 8.0 and earlier), use the tabadmin setting vizqlserver.trustedticket.use_deprecated_9digit_token. See the Tableau Server online help for more information.

Tableau Desktop (Back to top)
Issue ID

Using the Tableau Data Extract command-line utility to refresh an extract that was published to Tableau Server could fail with an "Internal error encountered." message.


When connected to Oracle databases, evaluating a Top N filter that returns non-null values could cause the application to become unresponsive.

In some cases, filtering specific dimension members would also remove unrelated members. In addition, the Filter dialog box and quick filters would not show the members being filtered.


Improved connect time performance when connecting to Teradata.

Filter actions set to run on select would not run correctly if the target sheet was set to Fit Height, Fit Width, or Entire View.

When connecting to a Salesforce data source, list fields were not available in the connection dialog box.

Primary and secondary data sources would continue to be blended even after removing links if the link was based on a date field.

Duplicating a sheet that has not been opened in a workbook (e.g., using the Sheet Sorter) could cause the application to stop working.

When connected to Hive Server 2 with Cloudera ODBC 2.5 or later drivers, interacting with a dimension that contain long strings caused a ”Fetch type not supported” error.

Creating an extract that contained columns with invalid characters would result in data not being imported into the extract.


When exporting a dashboard image that contained Multiple Values (Dropdown) filters from Tableau Server (or Tableau Desktop), quick filter values of All or Multiple Values were blank.

The Add Reference Line, Band, or Box dialog box would show a mix of localized and English text.

When connected to Vertica databases, using non ASCII characters in group names would cause the database error "Non-ASCII characters are not supported in names".

When connecting to a Salesforce data source, number fields with the Unique flag selected would not be available in the connection dialog box.


Creating a set based on latitude and longitude measures would cause an invalid filter.

When connecting to a Google BigQuery data source, interacting with the connection dialog box when the BigQuery driver is not installed could cause the application to stop working.

Clicking View Data in a data connection dialog box sometimes caused Tableau Desktop to stop responding.

Copying a map view as an image would sometimes result in missing data in the resulting image.

The Forecast Options dialog box would sometimes resize incorrectly.

Improved responsiveness and interactivity when creating views and dashboards.

The Tableau Excel Add-In would install correctly but would display as inactive in the Add-Ins window.

In the Amazon Redshift Connection dialog box, the Single Table list filter showed indexes in addition to the expected tables and views.

Labels on bar charts were inconsistent. In some cases a label would display on very narrow bars. In addition, there were cases where a label would be white and others where it would be black despite the background color being the same.


Tableau Desktop would cease working when discrete or continuous calculated dimensions and calculated measures were added to the view.

The Unhide Sheet option would incorrectly display on all sheet tab context menus instead of just on hidden sheets.

When connected to SAP Hana data sources, converting between date fields and a FLOAT or INT value would return incorrect values that were inconsistent with other data sources. This type of conversion now consistently returns the correct value.

Empty dimensions were not excluded from extracts which could cause the extract to fail.


After publishing a workbook with a scheduled extract refresh and embedded password, closing the application, reopening the workbook, and re-publishing it resulted in the embedded password not being retained and no prompt being provided for the password. The scheduled extract refresh would subsequently fail.

Opening a view that contained Thai characters would cause the application to become unresponsive.

Calculated fields that use the LOWER() and UPPER() string functions could create very long queries when connected to an Extract data source.

Double-clicking a geographic field in the Data window would sometimes cause Tableau Desktop to stop responding.


Discontinued support for connecting to Greenplum 3.3.


Blending on a key with a one-to-one relationship returns incorrect results for fiscal dates from the secondary data source.

When Total() is used in an invalid way as part of a table calculation, an error message is displayed.

After scrolling in a worksheet, clicking and dragging a label would show the label slightly above the cursor making it difficult to see where you the moved label will be.

When viewing data for a mark based on a multidimensional (cube) data source, changing the number of rows to show on the Underlying tab would run the correct query but continue to show all rows.


The application would exit when opening particular packaged workbooks that contain a large number of categorical quick filters.

An invalid JSON error could occur when viewing a workbook on the web that uses ASCII control characters or Unicode characters.

Single Value (Dropdown) quick filters that contain a large number of members was significantly slower to load than in previous versions.

When using a table with column-specific privileges, where the user does not have permission to access all of the columns, the error message "table 'user' does not exist” is displayed when using any ODBC connectors (MySQL, Vertica, Netezza, Teradata, Hive, GreenPlum, Aster, generic ODBC).


Adding background images from a network location would incorrectly append several forward slashes to the beginning of the file path, causing the image to be broken.


Creating an extract from a CSV file that included Hebrew characters would result in the characters not displaying correctly.

Comments on measure fields would not word wrap correctly.

Scroll bars on floating dashboard objects would disappear after the object was moved. The scroll bars would return after the object was resized.

Tableau Desktop was not respecting a TDC command to switch to OLEDB from ODBC connections. This TDC would sometimes be used when there were issues using new ODBC connections.

In some cases, Quantitative filters on a word cloud view would sometimes not correctly remove values that did not match the filter.

Closing a connection that was used by a sheet would not correctly delete the sheet. Deleting the sheet manually after closing the connection would cause Tableau Desktop to stop responding.

Removed an unused cookie.

Tableau Desktop would stop responding when republishing a workbook that connected to a Tableau Server data source and another data source.

After cancellation of a connection request in Tableau Desktop, Tableau processes would remain in memory because some providers were not honoring the cancellation request. These processes are now terminated correctly.

On reference lines that compute Min or Max per cell, tooltips that show the value would only show for the first reference line in the view.

In Tableau Desktop, for workbooks with large domain quick filters, selecting Floating from the dropdown menu will cause the workbook to become unresponsive.

Changing encoding for a field on the Marks card by clicking the icon next to the field could cause the error message, "Error in parameters for command 'display encoding-type-menu' missing: workspace."

Closing a data connection whose fields are used in a calculation would cause Tableau Desktop to stop responding. These calculated fields now correctly become invalid when the connection is closed.

When connecting to a Salesforce data source, numbers were not always formatted correctly.

When connected to a DB2 database, calculated fields that reference both a field from a secondary data source and a non-aggregated date function such as NOW() or TODAY() could cause a "No such column error."


Made several corrections to built-in geocoding. Some of these corrections include adding a large number of missing cities in Brazil, placement of the M5A and other Toronto area Canadian postal codes, placement of US zip codes, and an incorrect country code for South Sudan.

The activation dialog boxes included a U.S. phone number without a country code.

When Tableau Desktop was connected to an SAP Hana data source, a calculated field that used the SQRT function on a FLOAT measure returned a data type INT rather than FLOAT.

Selecting a different database table in a connection dialog box would sometimes cause the list of tables below it to display several blank entries before showing the tables in the newly selected database.

The JavaScript API: getFiltersAsync() function was querying the domain values instead of just returning metadata.

The Edit Custom SQL dialog box was not localized correctly.

Editing a data connection in a workbook using a blended Microsoft Analysis Services cube and extracted from a relational data sources caused Tableau Desktop to stop responding.

Dragging the Forecast Indicator field to Color would cause the field to disappear from the view.


Adding drop lines on marks that have a null value would cause the application to stop working.

The Cloudera Hadoop connection dialog box would display table selection options even if a connection had not yet been established.

When working with a nested aggregate calculation, changing one of the calculation layers to a table calculation caused Tableau Desktop to stop responding.


Fixed an issue connecting to Amazon Redshift data sources.

Selecting Edit Filter on a quick filter menu on a dashboard could bring up multiple instances of the same dialog box.

When connected to Vertica databases, calculated fields that use the TRIM() function were being sent as LTRIM(RTRIM()) instead.

Using date truncation for the fiscal year value caused only the second part of the year to be displayed in a view.

Some buttons in specific connection dialog boxes were not resizing to accommodate localized text.

In some cases, adding a boxplot reference line on an axis based on a measure with the INT datatype would incorrectly compute the whiskers.

When a data source was replaced with a published version of the same data source, table calculations appeared blank in the Measure Values shelf or were marked invalid.

When adding a table calculation that uses the PREVIOUS_VALUE function to a view, a “No such column” error sometimes occurred.

In Tableau Desktop, when comparing parameters with an IF expression in a calculated field, both parameters must be of the same type. The current error for this scenario is misleading--for example, "Cannot use 'string' type in 'IF' expression'".

Several areas in the application were either not resizing to accommodate localized text or were not fully localized.


In some cases, optimizing an extract could cause calculated fields to show incorrect values.

Cancelling an Oracle database query no longer results in a syntax error.


Decreased the amount of time it takes to connect to an Essbase database.

In workbooks with labeled drop lines, dragging a dimension that contained null values off the Filters shelf caused Tableau Desktop to stop responding.

Salesforce.com table names were not correctly localized when connecting to a standard connection.


Restoring from a backup file from earlier versions would sometimes fail with a "duplicate key value violates unique constraint" error.


When using a workbook with table calculations and blended data, table calculations were incorrectly applied to additional aggregate measures in the view.

Creating an extract from a workbook that contains a dashboard with a filter action would take significantly longer than in previous versions.

Images unpacked from a packaged workbook (.twbx) are not removed on exit. To make it easy to identify these temporary files, they are now located in C:\TEMP\TableauTemp.


When creating an extract from a MySQL database, in some cases the Count Distinct function would return different results than the live connection.

In a worksheet using fields from multiple data source, using a division operator in a calculated field from the secondary data source caused the error “Cannot blend the secondary data source because one or more fields use the / function, which cannot be computed locally."

Added support to address a limitation in the Google BigQuery engine, which cannot handle a JOIN involving more than two tables.

When using tabs to switch between worksheets, the Quick Filters search box would stop responding.

Displaying a size legend on some dashboards using the dashboard view menu would cause Tableau Desktop to stop responding.

In some specific cases, replacing a data source could cause the application to stop working.

Tableau Server (Back to top)
Issue ID

The Show Activity action in the User Activity administrative view caused the error "Sorry, the view you were looking for does not exist, or you do not have permission to see that view."

Workbooks that connect to a Microsoft Analysis Services database and have a hierarchical quick filter took a long time to load on Server.


Opening the PDF version of a published workbook and appending “?:format=pdf” to the URL sometimes resulted in a blank view.


In a published workbook, the color that you set for the pane of a worksheet was also displayed in the column and row headers.

Trying to access an expired VizQL server session caused a 403 error instead of prompting you to sign in again.

Editing views sometimes caused a 403 error.


Opening particular workbooks that contained dashboards with multiple worksheets using the same blended data sources could cause Tableau Server to become unresponsive.


Workbooks sometimes appeared to have missing data after Tableau Server was upgraded from version 7.0 to version 8.0 and extract refreshes were performed.

Customized logo displayed incorrectly after the Server backup file was restored.


Interacting with some views on Tableau Server would sometimes result in a "Tableau Data Engine Error 4: no such schema (TableauTemp)" error. This error was caused when there was heavy load on the query cache and the cache had to be rebuilt.


Restoring a Tableau Server backup file (.tsbak) sometimes resulted in user groups being duplicated and renamed.


When exporting a dashboard image that contained Multiple Values (Dropdown) filters from Tableau Server (or Tableau Desktop), quick filter values of All or Multiple Values were blank.


Moving a "range slider" filter on a published view resulted in the view becoming inactive until a selection was made.

When editing a view on the web, opening a submenu from a field menu, then clicking the broser "back" button caused the field menu to stop responding.


Tableau Server data sources that contained live connections to multiple tables would not correctly cull joined tables from the query when appropriate. The same connections in Tableau Desktop would send queries without the join.


After upgrading to version 8.0.x from version 7.0.x, some workbooks were performing slower when making filter selections.


In a published workbook, row heading text overlapped row separator lines.

The number of admins displayed on the Sites page included the _system user and site administrators.

Editing and then saving workbooks on the web that were connected to Google BigQuery caused the error “RuntimeException: This workbook contains a Google BigQuery data source that requires embedded credentials.”


An “Unexpected Server Error” message can sometimes occur when selecting All in a quick filter.

When connected to either Microsoft Analysis Services or extract based data sources, filter actions, and tooltips that contained long dimension and measure values would be truncated when viewed in a browser.


Tableau Server users were not able to select All in a single value filter without first selecting another value.

Using the Measure Values and Measure Names fields caused the view to render slowly.

When editing a workbook in Google Chrome, Mozilla Firefox, or a newer version of Internet Explorer, clicking Show Me, and then selecting Treemap or Bubble Chart caused a 404 error.


NeXpose security software can sometimes display errors with Tableau Server. Upgrading to Apache HTTPD version 2.2.24 resolves this issue.


In Tableau Server, views sometimes failed to render due to a failure in a VizQL Server process.

Filter actions sometimes caused a "tuple id cannot be resolved" logic error.


Corrected a security vulnerability in the Tableau Server permission functionality.

The time it took to set the parameters via the JavaScript API was too long.

From the Analysis menu, you were able to edit the original published formula for calculated fields in Server data sources instead of editing a local copy of the calculation.


In a published workbook, moving the cursor over items in a Single Value (Dropdown) quick filter did not highlight the items.

Improved the user experience when there are no matching tags after performing a search by Tag is.


On Tableau Server, URL actions directed at a table row that contained null values would fail to execute.

Titles on some dashboards would be clipped on the bottom when viewing the dashboard on Tableau Server. These titles now display the same as in Tableau Desktop, without the clipping.


Resolved a privately reported blind SQL injection vulnerability in Tableau Server. The vulnerability could have allowed arbitrary SQL commands to be passed to the Tableau Server backend database for execution. An attacker who successfully exploited the vulnerability could have taken complete control of an instance of Tableau Server. An attacker would have needed valid credentials or the guest account would have had to have been enabled to exploit this vulnerability. This vulnerability is rated Critical for 8.0.x and 8.1.x versions of Tableau Server, and customers are urged to upgrade at their earliest opportunity. Tableau has not received any information to indicate that this vulnerability has been publicly used to attack customers at the time this update was released. Tableau would like to thank Tanya Secker and Christiaan Esterhuizen of Trustwave SpiderLabs for identifying and reporting this issue (CVE-2014-1204) and for working with us to help protect our customers.


A tooltip that was wider than the view caused scrollbars to display in the view.

Clearing the Enable subscriptions option on the Admin > Sites > Edit Site page, and then clicking OK did not save the setting and had no effect on the Server.

Version information for third-party components that are provided with Tableau Server displayed a large amount of information.

System administrators could not set the license level of all Server users simultaneously on a guest-enabled server.


Attempting to create a backup of a two-machine Tableau Server cluster in which the primary was running Windows Server 2008 (pre R2) would fail with the following error: "Skipping backup since is user maintained and distinct from ."


When running a filter action on a Server view, the spinner that indicates the action is in progress wasn't showing.


Changes made to a published data source would intermittently not be reflected when accessing the data source using Edit on Tableau Server. Opening the data source in Tableau Desktop would show the changes correctly.


Improved session safety when using trusted authentication.


Embedded Tableau Server views wouldn't render correctly when they used a fixed size and the HTML page in which they were embedded was designed to initially hide, then display the view.


When editing a workbook that contained more than one Single Value quick filter, selecting a value for the first filter, and then selecting a value for another filter caused an incorrect value to be displayed in the first filter.

Vertical text objects in published views displayed incorrectly.


If a cube data source is published to Tableau Server with no username credential and is configured to prompt for credentials, signing in to the data source would eventually fail with an error of this type: "Database error 0x80004005: Errors in the OLE DB provider. Could not connect to the redirector. Ensure that the SQLBrowser service is running on the server."


In the Customized Views administrative view, the customized view hyperlink would display in the tooltip and then disappear.


When Tableau Server was configured to perform SQL Server impersonation, a "Session ended by server" error message would sometimes display when a user attempted to open a workbook.

When working with a published dashboard that contained an unpublished underlying worksheet, saving the underlying worksheet caused the browser to navigate to the Views list instead of back to the dashboard.


On Tableau Server, users who have published or created workbooks or created projects retain publishing rights until they are no longer the project or workbook publisher. However, when a site or system administrator tries to deny such users publishing rights (which should not be possible), a message would appear saying "1 user denied publishing." The Permissions menu would continue to correctly show that these users as having publishing rights.


When using a core-based license, starting Tableau Server took a long time. This was due to a license registration check performed before the database started.


The data server process would sometimes join tables incorrectly.

Exporting a dashboard as a PNG image created an image truncated to the size of the browser window.


Mitigated a security risk in Tableau Server related to Apache.


An indefinite spinner would display when accessing a view that was embedded via an Iframe, used trusted tickets, had the embed parameter set to no, and which prompted the user to authenticate.

When opening a workbook that had a Single Value (drop-down) quick filter that contained only one value, the drop-down would show as blank.


The background task server process would sometimes stop working.


Running tabadmin cleanup with the server running caused the temp directory to be removed without a warning.


Hive Server 2 extracts published to Tableau Server would fail with an error of the following type: "Error occurred while initializing the Hive client." The problem would occur when Kerberos tickets were being used.

When viewing a workbook that had multiple worksheets, clicking a filter action that pointed to other worksheets loaded the worksheet but did not update the browser’s tab name.

Searching by workbook tags returned incorrect results.


Using a highlight action across multiple views in a dashboard would incorrectly highlight all of the target views.


Holding down the shift key and clicking did not select multiple items in filters, as expected.

Background tasks that weren’t able to run because the server was stopped would be run simultaneously, at Server startup, including when a Server backup file (.tsbak) was restored. If there were a large number of tasks to be executed, this would sometimes have an adverse effect.

Pausing automatic updates in a published workbook, making a change to a parameter, and then resuming automatic updates sometimes caused a browser processing error followed by a “session ended by server” error.

Tableau Server did not allow you to create tags with both uppercase and lowercase letters.

Published views and dashboards that were multi-page would not always display all rows.

Searching a Multiple Value List quick filter caused error 502 or 503.

Changes to the domain name used by the primary Server were incorrectly propagated out to workers in a distributed installation.


Firewall software would block the browser request when interacting with a view on Tableau Server. This was due to Tableau Server using MIME boundary delimiters longer than the allowed limit of 70 characters.

When Tableau Server is upgraded or when a .tsbak file is restored, the background task rebuilt the search index. The default timeout for this task was 30 minutes. The timeout has been changed to 60 minutes.

In workbooks that contain many sheets, scrolling to see the sheet name on the sheet drop-down menu on Tableau Server would make the last sheets in the list unselectable in Firefox and Internet Explorer 10 web browsers.


In a published workbook, selecting an item on a quick filter caused the filter scrollbar to return to scroll to the top.


In workbooks with multiple worksheets, deleting a worksheet from the Server did not update the page numbers.


Tableau Server would stop working if a user filtered on a view and that view contained a discrete exact date field.

Improved the functionality for selecting views or workbooks as favorites, and for indicating when the user has no favorites.

Tableau Reader (Back to top)
Issue ID

A more informative error message displays when a licensing issues prevents Tableau Reader from starting.

Tableau Mobile (Back to top)
Issue ID

When using the Tableau iPad application to access a workbook previously published on Tableau Server, horizontal scrolling on an embedded dashboard now works as expected.


Corrected a password security vulnerability in the Tableau Android application.


Corrected a data storage security vulnerability in the Tableau iPad application.


Corrected an intent spoofing security vulnerability in Tableau for Android.