Product release and download

Tableau Desktop 8.1.4

We recommend using the newest maintenance release of this version, 8.1.25, which contains additional fixes.

Download Tableau Desktop 8.1.25

Build number


Download Tableau Desktop 8.1.4

Release date

Tue, February 18, 2014

Product support

Read more

Installation Guide
Install Tableau Desktop

Planning to upgrade?
Tableau Desktop Upgrade Page

Resolved Issues

Issue ID Description

When connecting to SAP NetWeaver Business Warehouse databases, only the Key aliases were available for dimensions despite other properties being available in the BEx Analyzer.


When connected to multidimensional (cube) data sources, converting an attribute to a Date data type would cause queries to become significantly slower.

Tableau Desktop would stop responding if a parameter was changed that was used in a calculated field on the Filter shelf.


Opening a workbook in Tableau Desktop 8.1 that connected to an Oracle Essbase database would sometimes cause a “No such function” error. The issue was caused by aggregated calculated fields created in previous versions of Tableau Desktop that used the Compute Locally setting for totals.


Added an SSL Required checkbox to the Amazon Redshift connection dialog box. Select this option to connect to SSL servers. Previously, a Tableau data-connection Customization (TDC) file was required for these types of connections. A TDC file can still be used to override the SSL Required checkbox.


Scheduled extracts would sometimes fail to run with a “datetime zone id is not recognized error” shown in the log files. Changing the time zone on the computer corrects this issue.


With multidimensional data source connections, Apply and Cancel buttons could be configured to display on quick filters. Apply and Cancel buttons should not be available with multidimensional data source connections. The buttons were not selectable. These buttons can no longer be configured to appear on quick filters.


Multi-selecting quick filters in Internet Explorer 8.0 would not display an Apply button if the width of the quick filter was less than 120 pixels.


Clicking Add Table in the Amazon Redshift connection dialog box would sometimes result in multiple query errors, including a permission denied and table does not exist error.


Editing a calculated field on the Filters shelf by selecting Compute Using would cause the Filter dialog box to become unresponsive.

Creating an extract from a data source that contains integer columns would result in some values (ranging from -127 to 128) being converted to NULL values in the extract.


Connecting to a Sybase ASE database that uses non-UTF8 characters and has character set conversion disabled would fail. The character set attribute can now be specified using a TDC file to allow these connections.


For connections to Oracle databases, queries using the GLOBAL_CONTEXT_MEMORY variable would return an ORA-03113 error.


When creating calculated fields that used the DAY(), MONTH(), or YEAR() functions while connected to Essbase database, Tableau Desktop would generate an internal error and sometimes stop responding.


Tableau Desktop would not connect to more than one table when connecting to Amazon Redshift databases. A "table does not exist" error occurred, even though the table existed, and the user had permission to access the table.


Workbooks with calculated fields that used two data sources would sometimes stop functioning.


Added and corrected Canadian postal code Forward Sortation Areas (FSA) in the built-in geocoding.


When connected to Essbase databases, some quick filter queries were taking longer than expected because Tableau Desktop was unnecessarily creating sets in the query.


Added many city equivalents to the Tokyo area in the built-in geocoding. These include large towns, large villages, special wards, etc.


Corrected the built-in geocoding and mapping data to accommodate border changes and mergers in Russia, Surinam, and Libya.


In built-in geocoding, California zip code 92350, Loma Linda, was mapped to Mojave National Preserve, instead of to its actual location 177 miles away.


Made several corrections to the built-in geocoding and map data. These corrections include separating the Muchinga province from the Northern province in Zambia, correcting the Thai provinces of Nakhon Pathom and Nakhon Phanom locations, which were incorrectly associated with each other's true locations, removing duplicate point geography for 10 Turkish cities, and separating the North Kalimantan province of Indonesia from the East Kalimantan province.


Data on cities in Puerto Rico with population greater than 15,000 was not available in the Tableau built-in geocoding.

Download Files