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

Notas de la versión de Tableau 9.0.3

Fecha de la versión:
23 Jun, 2015
Número de versión de compilación de Tableau Desktop:
Número de versión de compilación de Tableau Server:

New Capabilities

This release adds connectivity to a Spark cluster on Azure HDInsight using the Spark SQL connector.

This release adds a new connector that gives you the ability to connect to a Google Cloud SQL database instance.

This release adds connectivity to Microsoft Azure SQL Data Warehouse data using the Microsoft SQL Server connector.

Tableau Desktop (Back to top)
Issue ID

Appending CSV file data to an extract sometimes produced an error like the following: "Tableau Data Engine Error: 4: SimpleDatabase::SelectMetadataName: expected found=1, actual found=0 (fk=18446744073709551615 name="Cache&"nameTable="SCHEMAS")"


No "Number of Records" value was generated when connecting to a database using ODBC.


With SAS Statistical File connections, numeric values were incorrectly rounded up by a count of 1.


On Windows, when Tableau Desktop stores credentials for accessing Tableau Server through a proxy, the proxy credentials are stored in trusted storage.


Data source filters sometimes filtered results incorrectly when a workbook was opened in Tableau Desktop 9.0.


When you created a relative date filter while connected to an analytic view in SAP HANA, an error appeared: "[SAP AG][LIBODBCHDB DLL][HDBODBC] Syntax error or access violation;257 sql syntax error: incorrect syntax near ",": line 4 col 72 (at pos 286)".


When you changed a parameter in a workbook that used custom SQL queries, multiple query batches (each with a single query) were issued instead of parallel queries.


When the user didn't have access to the Tableau temporary folder (for example, C:\Users\\AppData\Local\Temp\), Tableau sometimes stopped responding.


Aggregate filters were not showing updated results when you removed dimensions from a view.


Tableau was closing unexpectedly when creating, editing, or viewing calculated fields if you had 3rd party accessibility tools installed.


With Tableau Desktop set to Japanese, Chinese, or Korean, when you tried to connect to a Vertica database with custom SQL, an error sometimes appeared.


When you attempted to refresh or re-open a workbook with a SAP BW connection that used a Single Value, Mandatory, No Default variable, an error resulted and the view didn't appear.


Print to PDF on large workbooks was slow and omitted some columns of data from the output.


When you attempted to connect to an Excel workbook that contained a .gif image, an error resulted indicating communication with the Tableau Protocol Server had been lost.

Tableau Server (Back to top)
Issue ID

After an upgrade to Tableau Desktop 9.0, when you attempted to reconnect to published data sources, a TDE DATEPART query compilation error resulted.


With a reverse proxy, URL redirection using a URL from a version of Tableau Desktop prior to 9.0 would redirect to an HTTP port instead of the expected HTTPS. This would produce a browser error.


Dashboards that used many action filters sometimes appeared blank when they were published to Tableau Server.


You could not synchronize Active Directory groups when any one user in the group had an object type of "InetOrgPerson".


Tableau Server would stop responding and need to be restarted due to an excess of INFO messages being written to the zookeeper log file.


After you removed tags from workbooks and views, the tags still appeared in the tag filter.


Removing permissions from a dashboard didn’t stop subscriptions from sending.


When you used the tabcmd export command and the command timed out, the Vizqlserver process would not release the memory or CPU it was using. As a workaround, you could end the vizqlserver.exe process in Task Manager and let the process restart automatically


When you changed dashboard quick filters on an iOS device using Tableau Mobile or a Safari browser, dimension headers did not update.


Tableau Server returned the following error: "Tableau Exception: SQL Server does not exist or access denied" for a packaged workbook with an extract of a SQL database.


A user with the Interactor site role could not create a new workbook from a published data source for which they had Publisher permissions.


Content did not display after upgrading because the Search index did not build.


Published workbooks that used shape marks sometimes generated repeated errors: "Unexpected error: Uncaught IndexSizeError".


When you published a workbook that included R Scripts, a misleading error message appeared: "One or more of your views cannot be viewed on the platform to which you are publishing: - This worksheet contains R scripts, which cannot be viewed on the target platform until the administrator configures an Rserve connection." The workbook was published and all sheets could be viewed.


You could use the tabcmd editdomain command to change the local domain.


Intermittent DataSourceException errors (Invalid object name) sometimes occurred for published workbooks with a connection to Microsoft SQL Server Native Client 10 or 11.


Blank pages appeared when Tableau Server and Internet Explorer 11 or Firefox were configured for a Norwegian locale.


Labels on treemaps in views published to Tableau Server sometimes were incorrectly displayed. Some labels were incorrectly compressed.


When you switched between custom views using a parameter control, the view reloaded but the data in the view did not.


When connected to a Microsoft Analysis Services database, removing values from a multiple-value custom list sometimes didn't update the view.


After upgrade to Tableau Server 9.0, a permissions table error occurred. Content didn't appear because the Search index didn't build.


Under certain conditions, a user who accessed a workbook as a Guest user could view data as the publisher of the data. For more information, see the following Security Advisory article: Guest Users Can See Data As the Publisher User.


Users accessing Tableau Server using trusted authentication could still sign in to sites that had been suspended or locked. For more information, see the following Security Advisory article: On Locked or Suspended Sites, Customers Can Sign In Using Trusted Tickets.


Under certain conditions, a workbook viewed on Tableau Server could show data from a published data source on another site. For more information, see the following Security Advisory article: Workbook Shows Data From Different Site.

Tableau Online (Back to top)
Issue ID

After you removed tags from workbooks and views, the tags still appeared in the tag filter.

Tableau Mobile (Back to top)
Issue ID

A web page embedded in a dashboard sometimes rendered incorrectly.

This version is available from the Customer Account Center.

non-humans click here