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

Date de publication:
29 Sep, 2014
Numéro de version Tableau Desktop:
Numéro de version Tableau Server:

New Capabilities

A MarkLogic connection type was added to Tableau Desktop.

Tableau Desktop (Back to top)
Issue ID

When creating a calculated field, Japanese characters being typed in the Formula text field only displayed after pressing ENTER.


Interactive filters (for example, a quick filter with a slider) were significantly slower than in previous versions.


Saving a .tde file with the same name as an existing .tde caused the error, “Tableau Data Engine Error: 4 … Path does not exist,” and deleted the existing .tde file.


When using a Date filter, you needed to drag a measure field to the view twice before the values appeared.


When you typed Hebrew or Arabic text in a text dialog and clicked OK, the first character was removed. If you reedited the text, the first character was missing. Saving and reloading the workbook added "\x0;" in place of the missing character.


You could not type in a custom formatting text box if a quick filter that accepted text was showing in the view.


Tableau Desktop stopped responding when a web zone on a dashboard displayed certain SVG (Scalable Vector Graphics) fonts.


When using a Multiple Values (Dropdown) quick filter, typing Japanese or Chinese characters either did not display or matching characters were not recognized as values in the data.


Opening Tableau Desktop resulted in a proxy server prompt for username and password and if you did not enter your credentials, maps in workbooks did not display.


On Tableau on the Mac, date literals generated a "not a valid date" error.


Tableau Desktop would generate a "Firebird database error 335544984: Database is probably already opened by another engine instance in another Windows session" error when used in multi-user virtual environments such as Citrix and VMWare.


Tableau Desktop (Japanese version) would stop working when using a workbook that was upgraded from 8.1 to 8.2. The issue occurred when doing a variety of tasks including connecting to a live data source, changing filters, switching between workbook sheets and adding fields to a view.


When creating an extract from a Google BigQuery data source, the operation failed, causing the error, “The Google BigQuery service experienced an unknown internal error. Please report this problem to Google.”


When selecting multiple measures and dragging them to the view, only one of the measures was added.


In Tableau Desktop, when making a connection with a workbook that had a locale different from the UI language, that locale did not immediately take effect, leading to unexpected results in custom geocoding.


When creating an extract, if you added a date field as a filter and then selected a date range, an unexpected error occurred when you tried to save the extract.


Performance recordings of Japanese and Chinese workbooks displayed incorrect characters in the workbook and sheet names.


If you used the localized word for "Value", "Computation", "FieldName" or "FieldLabel" as a custom label on a reference line, that word was translated to English. For example, the Japanese Character '値' was translated to 'Value'. (desktop)


When connected to an OData data source, datetime fields displayed null values.


When working with text in a text object, caption or annotation, if you changed the font from the default and then deleted the current text, the font formatting reverted to the default (Arial 9pt).


Copying a worksheet and pasting it to a new workbook did not persist the connection information. Instead of prompting for the appropriate password, a "problem connecting to the ... data source" error displayed.

Tableau Server (Back to top)
Issue ID

When you clicked Publish for an extract or workbook that uses an OData connection, nothing was published and an OData auth error appeared in the logs.


Working with a relative date filter caused a "tagName is null or not an object" error in Internet Explorer 8.


When using filter on a published dashboard, the filter selection remains after exiting to the workbook selection screen and then going back to the same dashboard.


When you made a connection to a Pivotal Greenplum database, Tableau Server would use a 64-bit Postgres driver rather than an installed 32-bit Data Direct driver.


Views that include a page card were displaying significantly more slowly in a browser than in Tableau Desktop.


Some JavaScript API asynchronous commands resulted in a "SyntaxException" error due to NaN values for some dates.


Dashboards containing parameter and filter drop-down controls were unaligned after being published to Tableau Server.


After running tabadmin ziplogs, the file buildversion.txt did not contain the version. The file now contains the version and other useful information in an easy to read format.


When connecting to Google BigQuery, if users were granted access to a BigQuery dataset but not the project being used for the connection, they were unable to share a workbook or re-publish it to Tableau Server.


Using a set as a filter caused some quick filter values to display “no value.”


After a user's license status was changed to Unlicensed, the user continued to receive subscription email.


A workbook that uses at least one extract data source and a TDE data source caused the workbook to be unusable after a scheduled extract refresh.


When publishing an Oracle connection, the calculation for the Number of Records field was rewritten to use additional functions. Consequently, query optimizations were invalidated, causing workbook performance to degrade significantly.


When using Internet Explorer 7 or Internet Explorer 8, accessing an administrative view that contains a quantitative quick filter with a range of zero caused an “Error: Invalid Argument.” error.


Attempting to load views from Tableau Server through Windows Server 2012 Web Application Proxy resulted in a "Failed to re-initialize session" error.


After upgrading Tableau Server, accessing the User Preferences page caused the following 404 error: “The requested URL was not found on this server."


The REST API allowed you to set userQuota or storageQuota but you could not remove the quota values using the REST API.

Tableau Mobile (Back to top)
Issue ID

Tableau Mobile iPad app downloaded data only in plain text format, which could not be worked with in spreadsheet apps, such as Numbers.

This version is available from the Customer Account Center.

non-humans click here