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

Fecha de la versión:
21 Ago, 2014
Número de versión de compilación de Tableau Desktop:
Número de versión de compilación de Tableau Server:
Tableau Desktop (Back to top)
Issue ID

When you deleted a sheet name and clicked OK in the error "An empty name is not allowed", Tableau Desktop exited.


When working with an extracted data source, if the structure of the file to append is different than that of the original file, selecting Append Data from File causes an “extract not found” error. If you are working with an extract of a single-table Excel file, and Excel file to append has only one sheet, using Append Data from File completes successfully.

In either case, when the file structure has changed, the correct action is to use the Append from Data Source command. For more information, see Adding Data to Extracts in the Tableau Desktop Help. http://onlinehelp.tableau.com/current/pro/online/windows/en-us/help.html...


When making a live connection to Parallel Data Warehouse (PDW) using the native SQL Server connection, dragging an aggregated measure to a view caused an error like: "[Microsoft][SQL Server Native Client 11.0][SQL Server]Parse error at line: 3, column: 10: Incorrect syntax near '('."


With Microsoft SQL Server connections, Tableau Desktop displayed a "The SELECT permission was denied" error and failed to connect when SQL Server denied permission for the stored procedures.


With Tableau Desktop 32-bit, connections to large Excel files would cause Tableau to close. Now when you attempt to connect to an Excel spreadsheet that is too large to load, a message displays telling you this.


Tableau Desktop on the Mac could not connect to SQL Server when SQL Server was using a non-standard port, and a "[Simba][SqlServerODBC] (10) Failed to connect to the SQL Server instance" error displayed.


When sharing Tableau workbooks in Microsoft Lync, interacting with the views sometimes did not work as expected.


Removing a field from a view sometimes caused an "Internal Error An unexpected error occurred and the operation could not be completed" warning. After you clicked OK in the message, Tableau Desktop became unresponsive.


When adding a field to a group, the drop-down menu in which you select the group showed fewer items than in previous versions. If you had more than 10 groups, this increased the need to scroll to select the correct group.


The Vertica and PostgreSQL driver installers did not properly update the odbcinst.ini file on the Mac if there was already a [PostgreSQL Unicode] section found.


Story points printed or saved to PDF with a black background if Dashboard Shading was set to None.


When editing a group in Tableau Desktop, items in the Add to list were not listed alphabetically.


Adobe Open Type fonts were not embedded in PDF output, causing a "Cannot extract the embedded font" error.


In maps, the names for the Polish cities Łódź and Lidzbark Warmiński were out of date.


When printing a view, Tableau Desktop terminated unexpectedly if the Repeat headers and legends on every page option in the Page Setup dialog box was not selected.


When signed in as the Guest user on a Mac, starting Tableau Desktop caused a “Got 0 identities when expecting 1” error that required you to a force Tableau Desktop to quit. Tableau Desktop ran as expected when you signed in under a defined user account.


Custom colors applied to a parameter that is used to toggle measures would revert to the default colors after a workbook was saved or published.


You could not install the Simba SQL Server driver by double-clicking the install file because the file was not signed. A signed install file has been added to the drivers page, replacing the existing file.


The Japanese “totals” heading in the Format window was incorrectly translated. The correct translation of the “totals” heading is 合計.


Exporting a view to an Excel crosstab sometimes produced three worksheets that contained data and other worksheets that were blank. The blank worksheets appeared in the file before those that contained data.


When connecting to Tableau Server from Tableau Desktop, changing the server name and clicking the Connect button caused the Sign In option to disappear from the Server menu.


When connecting to a Vertica data source that used double-precision floating-point number as the data type, Tableau displayed “#error” instead of the value.


Tooltips for the Edit Colors dialog box were hidden by the dialog box.


On Windows, and when using the Japanese (Japan) - Microsoft IME keyboard input setting, typing into the Calculated Field dialog box did not show the typed characters until you pressed Enter.


When the center value of a diverging color palette was set to a higher value than the end value, the entire color range displayed as the end color, rather than as a gradation.


When printing views to a custom paper size, Tableau Desktop closed unexpectedly, logging an unhandled exception with an “updateCustomPaperSize” error message.


On the Mac, the Tableau Desktop dock icon sometimes bounced when no user action was required. Some example tasks caused this include publishing a workbook or data source to a server, or switching applications while a drop-down menu is open in a dialog box.


Upgrading to Tableau Desktop 8.2 caused alignment setting changes in sheet titles that use a mix of left, right, and center alignments.


With PDF output from Tableau for the Mac, text was sized differently than on Windows or Tableau Server and so appeared to be justified differently. This was especially evident in headers and axes.


When working in the Tableau Server authoring environment on Internet Explorer 8, calendar date parameter selections were not retained.

Tableau Server (Back to top)
Issue ID

When upgrading from Tableau Server 8.1.x to 8.2,1, the upgrade would fail with a migration error in the tabadmin.log file:

"rake aborted! An error has occurred, this and all later migrations canceled:
ActiveRecord::JDBCError: ERROR: could not create unique index "datasources_luid_unique"".


Tableau Server did not honor text formatting options, like alignment, in published dashboards and wrapped text unnecessarily.


When running an incremental refresh on a Google Analytics data extract, Tableau Desktop duplicated data instead of retrieving the refreshed data.


When you used Tableau Desktop 8.2 to connect to a data source on Tableau Server 8.1, and the data source included a calc whose definition included a parameter, changes to that parameter were ignored.


A published workbook that included a live data connection to an Excel file would not update when refreshed, even if the Excel file had changed.


Tableau Server now runs ANALYZE on the PostgreSQL database after significant PostgreSQL version changes.


Custom ports that are specified during connections to Tableau Server from Tableau Desktop were not being saved.


In the Tableau Data Extract API, the INTEGER type did not support 64-bit integers.


Using the REST API, adding an existing user to a new site on Tableau Server configured for local authentication overwrote the user’s full name with the user’s user name.


Custom colors applied to a parameter that is used to toggle measures would revert to the default colors after a workbook was saved or published.


When you created a workbook with a Vertica connection using Tableau Desktop on Windows, the connection expected a specific driver version based on the driver version on the client computer. If Tableau Server did not have a matching version of the driver, a "DataSourceException: to connect to the database server '' are not properly installed on Tableau Server" error displayed.


During Tableau Server installation, a “psqlODBC_x64 -- Error 1918” message appeared in Windows Event Viewer. The error indicated that two driver files were missing, even though the files were installed successfully.

Tableau Mobile (Back to top)
Issue ID

On the iPad, panning or zooming on a map view caused circle marks to display in the incorrect location.


On the iPad, selecting the “All” value from a single value drop-down quick filter in a view connected to a Microsoft Analysis Services data source prevented other values in the quick filter from being selected.

This version is available from the Customer Account Center.