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

Fecha de la versión:
13 Mayo, 2014
Número de versión de compilación de Tableau Desktop:
Número de versión de compilación de Tableau Server:
All Products (Back to top)
Issue ID

Refreshing a large extract using the Tableau Data Extract Command-Line Utility caused a session timeout. Eventually, an "Invalid User Name or Password" error message was displayed.


Time filters that displayed only time on Tableau Desktop sometimes displayed dates and a calendar on Tableau Server.

Tableau Desktop (Back to top)
Issue ID

When opening a Tableau Desktop 8.0.x workbook in Tableau Desktop 8.1.x, an error "ColumnTable: Schema/DataTable Mismatch" occurred if the workbook contained a calculated field that used the modulo (%) operator.


After connecting to a SQL Server database with a period in the name, Tableau Desktop could not initiate bulk inserts into SQL Server temp tables and was unable to connect to a stored procedure.


When connecting to multiple tables in a Cloudera Hadoop Impala database, querying for the tables did not allow selecting the schema. Only tables from the default schema were shown.


When connected to IBM DB2 databases, database passwords appeared in Tableau logs.


Incremental extract refreshes, with a data source filter applied, did not update the value in titles, captions, or annotations. Full extract refreshes with the same data source filter applied successfully updated the value.


Publishing a workbook with an Amazon Redshift data source and table names more than 64-character long, resulted in an error.


When refreshing dashboard views, Tableau Desktop sometimes stopped responding.


When publishing a workbook to Tableau Server, selecting the Name drop-down menu to show existing workbooks did not display the workbooks in alphabetical order.


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.


With a cube data source connection, typing in the search box on a quick filter displayed a matching string, but after it was selected, nothing would appear in the view.


Switching between customized views sometimes resulted in the wrong view displaying, especially if they were part of the same dashboard.


When connected to a DataStax data source, dragging a field with a name of 128 or more characters to the view resulted in the error: "Query returned non-zero code" appeared when you.


A data extract would be deleted from the computer after that data extract replaced another data source in a workbook.


When working in a proxy environment with NTLM authentication, map tiles did not load.


Using MySQL in calculations sometimes resulted in an “illegal mix of collations” error.


Tableau Desktop did not recognize synonyms in a SQL Server database.


Selecting values from a multiple value list in a workbook published to Tableau Server and connected to an extract of an EMC Greenplum data source sometimes resulted in the error: "unexpected error".


When connecting to an Amazon Redshift data source, the tabprotosrv process stopped responding, logging a "collision with existing protocol when creating new protocol" error.


If a worksheet contained no dimension from a primary data source and a dimension from a secondary data source on the Filters shelf, or if it contained only a dimension from a secondary data source and a measure from a primary data source on the Filters shelf, clicking View Underlying Data resulted in an "Invalid set function" error.


Duplicating a dashboard produced an "Invalid numberless marker in format string" error message. The error occurred if there was a percent (%) symbol in the name of a dashboard action.


Tableau Desktop was not deleting temporary tables created during an Amazon Redshift connection after the Redshift session ended. Logs showed “drop table failed” messages.


Subtotals did not appear in crosstabs exported to Excel if dimension members associated with subtotals were hidden.


Refreshing an SAP BW extract caused workbooks to lose color, shape, and sort assignments for instances of columns.

Tableau Server (Back to top)
Issue ID

When hovering over a field in the view, drill-down and sort icons disappeared.


Check marks in quick filters disappeared when a workbook created from a Microsoft Analysis Services data source was published to Tableau Server.


Parameter drop-down lists opened slowly.


Trying to restore the default name (that is, " Tableau Server") for an instance of Tableau Server using the command "tabadmin customize name -d" returned the error: "can't convert false into Hash".


When exporting a view to image or PDF, with the caption not enabled, the resulting file showed the caption.


When a Tableau Desktop 8.0 workbook using an SAP BW data source was published to Tableau Server 8.1, aliases changed from Name values to Key values.


Selecting an item in a parameter drop-down list in a view did not change the visual appearance of the item to indicate that it was selected.


When editing views on Tableau Server, adding a dimension to the view or using Show Me caused intermittent errors: “An unexpected error occurred on the server”.


After exporting a view to a CSV file, any columns that were created from a calculated field in the table were displayed in random order, and other columns were displayed in alphabetical order. The exported sheet should retain the order of columns originally specified in the Tableau Desktop view.


Improved the stability and performance of the synchronization component used for data extracts in highly available server clusters.


The tabadmin failoverprimary command did not work if the value of the --primary option had a space between the IP addresses or computer names.


Using SAML authentication with Tableau sometimes created a security issue.


Typing a letter to jump to the entries beginning with that letter in a parameter list was not working. Repeatedly pressing a letter key now scrolls through items in a parameter list beginning with that letter. After the last such item, selection returns to the first item (wraps around).


If the SSL certificate file specified in the Tableau Server configuration was missing, Apache did not start. The tabadmin start command did not provide any error message. The error message in the Apache logs was not relayed.


When accessing Tableau Server over HTTP with SSL enabled, users are automatically redirected to HTTPS. However, this redirect was not happening when Tableau Server had multiple gateways and an "?:embed=y" URL parameter was used in a view.


Custom logos sometimes overlapped the Display Options link in the Share View dialog box. This dialog box no longer supports custom logos.


A full extract refresh from an Amazon Redshift data source sometimes failed with the following error: “Communication error while getting a tuple; Error fetching next row”.


During Tableau Server installation, when the Tableau Server primary used a custom logo that resided on a mapped drive letter that did not exist on the worker machines, an "Invalid values" error occurred.


Data source filters could prevent join culling on published data sources, leading to performance issues.


For a filter action that targets a hidden sheet, Tableau Server sometimes displayed the hidden sheet rather than the dashboard that includes the sheet.


Dashboards on Internet Explorer 8.0 or 9.0, appeared to be sliding down and to the right.

non-humans click here