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

Tableau 8.2 introduces many new capabilities that expand your ability to access and analyze data. The release includes the first-ever Mac OS version of Tableau Desktop, Story Points for interactive, data-driven storytelling, a more visual connection experience with data previews and improved experience in defining data table joins, and updated maps, in addition to enhancements to simplify administration and support of Tableau Server.

See what's new in Tableau 8.2

18 Jun, 2014
Tableau Desktop (Back to top)
Issue ID

Darker Circle and Shape marks were using dark labels that were difficult to read against the dark marks.


Upgraded the version of Firebird provided in Tableau Desktop to 2.5.


Including the previous_value() function in a table calculation was causing an error when refreshing a data extract.


Abbreviated dates were inconsistently formatted when a workbook's language locale was set to French (Canada). The abbreviations for months would end with a period for discrete dates but not for continuous dates.


Closing a workbook without saving changes after you refreshed an extract caused an "Ignoring calculated field '[Number of Records]', field is already defined by data source" error.


When formatting a week date or a fiscal week date to show as the truncated fiscal week (for example, Week 10 formatted as W10), the week numbers could be shifted so they did not match the actual week (for example, Week 11 could show as W10).


Depending on the calendar being used in a given locale, the first week of the year may fall into the previous year. For example, in ISO-8601 calendar, the first week of the year is the week containing January 4th. As a result, even December 29th of the previous year could be the start of the first week of the next calendar year. Prior to this fix in certain years, date fields using the format yyyy Www in iso-8601 or Urdu locales would appear incorrectly as week 1 of the previous year instead of the current year. This fix does not affect standard Gregorian calendars where first day of the year is January 1st.


Using aggregations on a poorly written parameter-based calculation caused an "ambiguous function call" error. Example: a spelling or case mismatch of parameter options, or parameter options missing from the view.


An exported PDF or PNG did not accurately reflect filter-based highlighting on the dashboard. Sheets that should not have had any highlighting had highlighted marks in exported files, while the highlighting displayed correctly on the dashboard.


Uganda districts have been updated in maps.


Parameter controls for numeric or date fields did not behave as expected for non-US locales.


When blending data, selecting in the secondary data source a field that contained geographic information mistakenly enabled the map view in Show Me.


In packed bubble charts, when a null value existed in the data, bubble marks were placed on top of one another.


REPLACE() is now supported for legacy Jet connections to Microsoft Excel, Access and plain text (CSV) data sources.


Views that included maps with dual axes would not resize correctly.


With a Microsoft Analysis Services data source, filtering with a time dimension that had a string data type could cause a view to stop responding.


This release contains a critical security fix to Tableau Desktop, Tableau Server, and Tableau Reader that reduces exposure to man-in-the-middle and denial of service vulnerabilities. To address these vulnerabilities, the OpenSSL library used by the affected Tableau products has been upgraded to 1.0.1h.


Dimensions included in a filter were automatically added to the Rows shelf when you updated a table calculation on the Filters shelf.


Editing a set that was based on a continuous dimension would sometimes result in an error stating that the Edit Set dialog could not be displayed. Meanwhile, the set could still be used.


Subtotals were disabled or enabled based on whether grand totals were shown instead of remaining independent.


Tableau Desktop was not always respecting the Show Empty Rows/Show Empty Columns options. This resulted in views that included rows or columns for empty or missing data. This behavior can be toggled (empty rows or columns can be shown or hidden) by selecting Analysis > Table Layout > Show Empty Rows or Show Empty Columns as described in the Tableau Desktop Help topic Missing Values.


If a join field for a Teradata connection was deleted or renamed, the connection could not be edited without losing other valid tables and joins in the connection.


When a view using a reference line was copied and pasted into Word or Excel as an EMF image file, the reference line label would be incorrectly aligned.

Tableau Server (Back to top)
Issue ID

Changing the date with a date range parameter slider would correctly update the view, but sometimes incorrectly update the slider itself (for example, it might show an End Date of January 2013 when it should show December 2012).


Tooltips were taking a long time to display.


The tabadmin backup command options --unsafe and --stop-server are obsolete in Tableau Server 8.1 and have now been removed completely from Tableau Server 8.2. Attempts to use these options will result in an error and failed operation. Any automated scripts that use these options should be updated.


When a published workbook included a dashboard with a fixed size and worksheets shown as tabs, the worksheets would display in the fixed size of the dashboard rather than expanding to the available space in the browser window.


The following components were upgraded in response to the Heartbleed OpenSSL security vulnerability: Apache was upgraded to 2.4.9, OpenSSL was upgraded to 1.0.1g, the psglODBC driver for PostgreSQL was upgraded to 09.03.0300, and PostgreSQL was upgraded to 9.3.4-3. Note: A subsequent, unrelated fix further upgraded OpenSSL to 1.0.1h.


Added the tabadmin set option wgserver.clickjack_defense.enabled to prevent security attacks on Tableau Server users via "clickjacking." For details, see the Tableau Server Help.


A tooltip would initially show values for the correct mark but would sometimes switch to displaying values for nearby marks.


When a view that included an exclusive, all-mode filter was exported, the resulting image or PDF would show each individual filter item as selected instead of just the (All) filter.


The version of PostgreSQL used by Tableau Server was upgraded to 9.3.4. This upgrade resolves a PostgreSQL issue that, for some customers, resulted in increased database size and decreased performance. This problem resulted in many repetitions of "WARNING: pgstat wait timeout" in the PostgreSQL log files. Customers that worked around this issue using” tabadmin set pgsql.use_vacuum_job=true” need to reset this value to the default using "tabadmin set pgsql.use_vacuum_job -d". Tableau recommends you do the reset before upgrading, but you can do so immediately after installing the new version if needed. For details, see the Pre-Upgrade Checklist Knowledge Base article.


The command-line tools tabadmin and tabcmd now return a 1 (one) if a command fails and a 0 (zero) if a command succeeds. Previously, a 0 was always returned.


Using the web browser Back button while navigating dashboards did not give expected results.


When using client-side rendering, tooltips would sometimes be truncated if tooltips of different sizes were adjacent to one another.


Workbooks created from published data sources did not reflect changes in the published data source until the workbook was republished.


If tabcmd was used to export a published workbook that had a caption in a language other than English, the caption would appear in English instead of retaining the intended language.


Using the JavaScript API, event.getParameterName() now correctly returns the field name even when the parameter title is changed in the UI. Previously the title was returned.


Updated Apache and server configuration settings to address an SSL/TLS security vulnerability.


When using client-side rendering, marks on maps would sometimes not display if the client web browser was Internet Explorer 9.


The date format in calendar quick filters was displayed according to the operating system settings on the computer running Tableau Server, instead of the language and locale specified in the workbook, browser, and in Tableau Server.


This release contains a critical security fix to Tableau Desktop, Tableau Server, and Tableau Reader that reduces exposure to man-in-the-middle and denial of service vulnerabilities. To address these vulnerabilities, the OpenSSL library used by the affected Tableau products has been upgraded to 1.0.1h.


When using Internet Explorer 9, quick filter fonts were hard to read on views published to Tableau Server and embedded in SharePoint 2010.

Tableau Mobile (Back to top)
Issue ID

Accessing Tableau Server dashboards through a proxy server using Tableau Mobile would sometimes result in connection errors.