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

En la versión 9.0 de Tableau, agregamos una cantidad de funcionalidades con las que logramos un producto más inteligente en relación con lo que está haciendo: desde la preparación automática de datos que lo ayuda a incorporar datos en su análisis hasta los mapas inteligentes con búsqueda geográfica. También realizamos una gran inversión en el rendimiento. Y reconstruimos Tableau Server y Tableau Online para ayudarlo a compartir sus descubrimientos y colaborar con datos.

Vea lo nuevo de Tableau 9.0

En la lista a continuación se incluyen algunos de los problemas clave solucionados en Tableau 9.0.

Fecha de la versión:
06 Abr, 2015
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 connecting to an IBM Netezza database, using incorrect case for a database name resulted in the error:
"ERROR: invalid database name '', does not exist
ODBCProtocolImpl::ReadForeignKeys: Error: Unable to read foreign key metadata.
ODBCProtocolImpl::ReadForeignKeys: Warning: Unable to read foreign key metadata using NULL qualifiers"
and Tableau Desktop was unable to assume referential integrity.


Using stored procedures to connect to a SQL Server Parallel Data Warehouse (PDW) database caused the error: “The stored procedure "" does not return a result set, or the result set columns do not have names."


Creating a full outer join using the generic ODBC connection to SQLite caused the error: “Unexpected error.” The full outer join type is no longer visible for general ODBC connections to SQLite.


Highlight actions failed in dashboards with tab names that contained multiple, sequential angle bracket characters or a single comma.


Using custom SQL to join tables in HIVE connections caused error: “FAILED: ParseException.”


When connecting to a data source, Tableau Desktop quit unexpectedly.


When connecting to Salesforce, joining tables resulted in the error: "Expression clause references too many tables".


When a URL parameter was used to change a table calculation sheet link action filter, a “LogicException” error would appear.


Editing a calculated member field in an MSAS data source caused the field to revert from a discrete field to a continuous field.


For SQL Server, case sensitivity in the Describe Field dialog box was incorrect when custom SQL was used.


When you replaced a published data source, quick filters would disappear from workbook views.


In Tableau Desktop, opening multiple instances of a workbook that is published to Tableau Server displayed incorrect workbook names, beginning with the second instance of the workbook.


When connected to an Oracle database, copying and pasting sheets between workbooks resulted in the "Oracle database error 1005: ORA-01005: null password given; logon denied" error.


On a Mac, when attempting to create an extract from an Excel file with a column name that included the Ñ character, the error "Tableau Data Engine Error 4: No such file or directory" would appear.


Quick filters in Polish listed the days of the week were listed alphabetically, rather than in calendar order.


When aliasing fields in the primary data source using the secondary data source, the "Edit Primary Aliases" command was not available. This command is now available if a dimension from the primary data source and another field from the secondary data source are being used in the view.


A global filter on a hierarchy field in Microsoft Analysis Services (MSAS) took changes made only in the most recent sheet included in the global filter. This sometimes caused sections of the view to display incorrectly.


Clicking on a mark in a view caused the error: "tuple id cannot be resolved."


When adding or editing a join clause, the Join dialog box did not accept supported Asian characters.


For languages that Tableau is not localized into, the days of the week were sorted alphabetically, instead of the order of occurrence.


Workbooks containing multiple nested table calculations that share common sub-calculations may render differently after upgrade to Tableau Desktop 8.3 or 9.0

If you encounter this issue, view the table calculation settings for the calculations that appear to render incorrectly. Verify that more than one table calculation is using an underlying calculation. Compare the settings between different instances of the calculation. Update any table calculations that reverted to default settings (for example, Table (Across)) to match calculations that retained the updated settings.


When connecting to Amazon EMR using Impala, creating an In/Out set, where the expectation is that all values would be in the Out set, instead results in a blank view. This is due to the way that Impala is optimizing the query.

Tableau Server (Back to top)
Issue ID

When Tableau Server was configured to use an external load balancer or proxy server, Kerberos authentication failed with the error: “No key table entry found matching [n].


Using a hyphen (–) in search caused inconsistent results.


When exporting a view to PDF, legends appeared in the PDF export even though the legend card was hidden in the view.


When using Internet Explorer browsers, tooltips would disappear too quickly, making it difficult to select links in the tooltip.


When using web authoring to edit a published workbook, if you deleted a sheet, then added a new sheet and saved it with the same name as the deleted sheet, an error displayed: "LogicException: Internal Error An unexpected error occurred".


The initial dashboard render for a workbook with relevant-value quick filters waited unnecessarily for acceleration view queries to complete and sometimes timed out.


Attempting to establish an impersonated database connection to a SQL database using a user name with an apostrophe caused an error: "TableauException: Microsoft SQL Server was unable to establish an impersonated database connection."


"Relative to Now" quick filters showed incorrect time when configured for Last N hours or Last N minutes.


When using a URL action to pass parameters from one dashboard to another, no data was displaying in the view because an ampersand in the data being passed in the action was not encoded.


When a URL parameter was used to change a table calculation sheet link action filter, a “LogicException” error would appear.


In map views published to Tableau Server, overlapping marks could not be individually selected.


Dashboard filter actions did not navigate to a worksheet unless you selected the object before the action.


After editing the data source name (i.e., the connection name) of a Tableau Server data source, the original name continued to appear when you re-edited the data source.


On Tableau Server, connecting to or using a published workbook that joins a table containing custom SQL with a parameter to another table resulted in the error: "Custom SQL relation refers to a non-existent parameter: [Parameters].[Parameter 1]
Unable to connect to the server ''. Check that the server is running and that you have access privileges to the requested database".


On occasion, when installing Tableau Server, the install would generate a "MoveFile failed;... Cannot create a file when that file already exists." error. Clicking Retry allowed the installation to complete successfully.


When row and column axes have different formats, Tableau Server displayed only one of the formats for both axes.


The "tabcmd export --png" command did not adjust the image width and height when you specified a width and height.


When workbooks with a horizontal scroll bar were published to Tableau Server, charts could be truncated at the bottom.


Multiple Values (custom list) quick filters would generate an "Unknown server error" when they were included in the first selected story point on a published workbook.


Embedded views would not display when accessing HTML files using the file:// protocol.


Refreshing the browser two or more times when working with a published view with a multiple value filter disabled the Revert All button.


With the REST API, using concurrent threads to create multiple sites and add users to those sites could cause the error: “user [username] was already added to the site [site id].”


Using client-side rendering caused the second line of text in some tooltips to become truncated.


A workbook publisher could sign in to Tableau Server and schedule an extract refresh for the workbook even when Tableau Server was not configured to allow scheduling.


When the browser window was shrunk to a very small size and then returned to the original size, filter names remained truncated instead of showing full text.


The "next run" time displayed for a schedule on the Schedules page could show a mismatch with the time range a schedule was supposed to run. This happened if the server was in a different timezone than the client computer.


Clearing All in a quick filter and then selecting All again caused a white space to appear at the top of the view where the caption was placed.

Tableau Online (Back to top)
Issue ID

When row and column axes have different formats, Tableau Server displayed only one of the formats for both axes.

Tableau Mobile (Back to top)
Issue ID

On a mobile device, the Apply Button in a multiple-value dropdown filter would return a blank view rather than applying the selected values.

This version is available from the Customer Account Center.

non-humans click here