지금 다운로드
This version is available from the Customer Account Center.

이 버전에는 Heartbleed 보안 문제를 해결하는 주요 보안 업데이트가 포함되어 있습니다.

Heartbleed는 OpenSSL 라이브러리(버전 1.0.1)의 주요 보안 취약성입니다. OpenSSL은 Tableau 제품을 포함하여 여러 웹 사이트와 소프트웨어 제품에서 사용되는 오픈 소스 소프트웨어입니다. Heartbleed 취약성은 공격자가 원격으로 클라이언트 또는 서버 응용 프로그램 메모리를 읽을 수 있도록 허용합니다. 이를 통해 암호화 키를 읽을 수 있으며 트래픽을 가로채기하여 획득한 데이터의 암호화를 해제할 수 있습니다. 이 문제와 관련된 Tableau의 업데이트, 해당되는 Tableau 제품 및 Tableau를 업데이트하는 방법에 대한 자세한 내용은 Heartbleed 문제 기술 자료 문서를 참조하세요.

출시 날짜:
Desktop 빌드 번호:
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

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


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


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


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.


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 #.


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.


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


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.


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.


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


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."


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.


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".


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


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.

Tableau Server (Back to top)
Issue ID

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.


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.


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.


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


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.


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.


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.


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.


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.


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


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.

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.)"

non-humans click here