Descargar ahora
This version is available from the Customer Account Center.

Fecha de la versión:
18 Feb, 2014
Número de versión de compilación de Tableau Desktop:
Número de versión de compilación de Tableau Server:
Número de versión de compilación de Tableau Public:
Número de versión de compilación de Tableau Reader:

New Capabilities

Added support to Tableau Server for multiple network interface cards (NICs). Learn how to upgrade and use this feature in the following Knowledge Base article: Using Tableau Server’s Support for Multiple Network Interface Cards

Added support for connecting to Teradata OLAP Connector 14.10.

Added support for connecting to Splunk 6 Enterprise.

Added support for the Cloudera V2.5 ODBC driver for Impala.

Tableau Desktop (Back to top)
Issue ID

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.


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.


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


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.


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.


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.


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.


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


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

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.


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.


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


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

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


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.


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


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


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.


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


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.


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.


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.


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

Tableau Server (Back to top)
Issue ID

Subscription emails would sometimes not include the image of the subscribed view; however, the links to those views on Tableau Server would work.


Date parameter slider controls in Tableau Server required you to click forward twice for the view to update when the system locale of the primary computer was set to a European locale.


Workbooks based on certain MySQL data sources showed infinite spinners and never completed loading. The error "The protocol is disconnected" was logged.


Internet Explorer 8 would return an "Object doesn't support this property or method" error when displaying a Tableau Server view.


In the JavaScript API, calling the getParametersAsync() method would prevent later calls to changeParameterValueAsync() from working. The program would return the error: "Failed: Invalid parameter: value".


Clicking a crosstab header caused the header to disappear.


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


Views published to Tableau Server would not render correctly after the view was republished following a change to the underlying data source.


Editing or deleting a comment on a published dashboard or view would sometimes result in the change not being made and Tableau Server displaying an infinite spinner.


In custom views, making a filter selection on a sheet would sometimes take you to another sheet in the dashboard, instead of updating your filter selection, resulting in an infinite spinner.


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


Because of a .NET incompatibility, the sample SharePoint C# code provided with Tableau Server 8.1 won’t work with SharePoint 2010. To work around this, you can either upgrade to SharePoint 2013, which uses .NET v4.5, or you can continue to use SharePoint 2010, which uses .NET v3.5, but change the SharePoint example code to use SSL 3 by adding the following line before the call to HttpWebRequest.GetRequestStream(),:

ServicePointManager.SecurityProtocol = SecurityProtocolType.Ssl3;


Accessing the System Info URL for monitoring Tableau Server would incorrectly prompt for a username and password even when the IP address for the computer used to access the system info was specifically allowed using the wgserver.systeminfo.allow_referrer_ips setting. See Monitoring the Status of Tableau Server to learn more about monitoring the status of Tableau Server.

Tableau Server sometimes created too many folders in its temporary directory, in some cases using disk space to the point where the server would stop functioning.


Date quick filters had additional characters in workbooks published to Tableau Server using the Spanish and Portuguese locales.


Scrolling in a view using the up and down arrows on your keyboard would not work when using Internet Explorer 11.


Two-fingered scrolling for nested panes in Safari 6.1.1 and 7.0 would not work for Tableau Server views, views embedded via an Iframe, or views that were part of custom web applications created with Tableau's JavaScript API. See Tableau Knowledge Base Article for details on Iframe embedding.


Subscription tasks would intermittently stall and block any other tasks until the server was restarted.


Downloading a workbook that connects to a Tableau Server data source from a server that is configured to use an Apache load balancer would expose worker server IP addresses in the Tableau Server Sign In dialog box in Tableau Desktop.

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


It wasn’t possible to view scheduled refresh tasks for a workbook if Tableau Server’s configuration included a load balancer.


Installing Tableau Server on a machine with dual network interface cards (NIC) and configuring it for Active Directory (AD) user authentication would result in the Machine column displaying as blank on the server’s Maintenance page.


Overwriting a Tableau Server data source would require you to set up refresh schedules and other data source settings during publish rather than remembering the originally published settings.


After upgrades to version 8.1.3, extract refreshes for Greenplum data sources in Tableau Server would fail with an incorrect driver error.


Right-clicking or holding the CTRL key while clicking the Admin tab in the navigation area did not offer an "Open in New Tab" option.

non-humans click here