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

Notes de version pour Tableau 9.0.1

Date de publication:
05 mai, 2015
Numéro de version Tableau Desktop:
Numéro de version Tableau Server:

New Capabilities

This release adds support for Teradata OLAP 14.10.

This release adds MapR Hadoop Hive connectivity for the Mac.

Known Issues: Fixed
The issue found in the original build of Tableau Desktop 9.0.1 (9000.15.0427.2036) that resulted in Tableau closing when you performed a worksheet action like Hide or Delete has been fixed. A new build (9000.15.0506.1800) is available from the Customer Account Center.

To make sure you are using the updated version, download the currently available version of Tableau Desktop and go to Help > About Tableau. The version should be 9000.15.0506.1800. For details on the original issue, see “When performing a worksheet action like Hide or Delete...” below.

An unrelated issue in the installer for Tableau Desktop on the Mac was also fixed. This issue resulted in Tableau not installing if it had not previously been installed.

These issues did not affect Tableau Server 9.0.1.

Tableau Desktop (Back to top)
Issue ID

With several data sources (for example, Microsoft SQL Server, Oracle, and Google BigQuery), when you opened a workbook that uses groups, an error appeared.


Attempting to print a Tableau sheet or workbook from a command line using the /pt function caused the Print dialog box to open.


When importing from an Excel file that contained a null or blank text field, Tableau assigned the Excel column header name to the fields, rather than assigning null.


When you changed the dashboard font to white, the radio button center and background for the parameter filters were also white, so you could not see which filter was selected.


When connected to an extract in Tableau Desktop, copying and pasting a sheet within a packaged workbook caused a duplicate data source to appear in the Data pane.


When republishing a workbook with embedded credentials, you were not prompted for user credentials and subsequent attempts to refresh the extract on Tableau Server would fail because user credentials had not been entered.


When you selected a file on SharePoint for use in Tableau Desktop or Tableau Reader, sometimes the file would not open.


When editing a calculated field using a formula that included English text and Arabic or Hebrew characters, the formula punctuation and text displayed incorrectly.


Using Automatic Proxy Configuration on a Mac sometimes caused Tableau Desktop to stop responding

When performing a worksheet action like Hide or Delete, Tableau Desktop could close unexpectedly.


When you edited a worksheet title in the Edit Title dialog box while using a right-to-left language (such as Arabic or Hebrew), clicking the Left alignment button showed the text as right aligned.


When creating bins on a measure with a name that includes the percent (%) character, the first bin was created successfully, but a subsequent attempt to create a bin would result in an error: "Internal Error An unexpected error occurred and the operation could not be completed" or Tableau would close unexpectedly.


When a user filter referenced a field that was added to the filters shelf, and you included the user filter field in a dynamic title, the title did not display properly.

Tableau Server (Back to top)
Issue ID

Version 9: If the Search & Browse index was not fully indexed, alerts could be inconsistent or erroneously reporting problems (for example, failed extract refresh on a workbook that does not include an extract). Workaround: Restart Tableau Server to allow the index to be rebuilt. The index is automatically rebuild when Tableau Server starts. For more information, see the Tableau Knowledge Base.


The "tabadmin warmup" command only worked if the primary server was configured with a gateway process.


Dashboard colors intermittently reverted to a default color palette.


Some non-alphanumeric characters in the Run As User account password resulted in errors when the Kerberos configuration script was run. This prevented a successful Kerberos configuration. As a workaround, the administrator could manually add quotes around the password in the Kerberos script.


After an administrator changed Tableau Server to use SAML for authentication, if a Tableau Desktop user opened a workbook from Tableau Server by clicking a thumbnail, the user was shown a sign-in dialog box in which the Server field was unavailable. Entering credentials resulted in a "Username/password incorrect" error.


When you attempted to access a workbook view that was published with embedded credentials from a Teradata OLAP connector, you were sometimes prompted for credentials and the view might never load.


Version 9.0: If you reused a computer from one Tableau Server installation in a new installation of Tableau Server without fully uninstalling the software, old configuration data could cause connection problems between server nodes and and generate "NoAuth" error messages in the clustercontroller.log file. For more information, see the Tableau Knowledge Base.


Version 9.0: When you did a "restore" on a Tableau Server installation with multiple repositories, the backup files were not getting removed. This was an issue with upgrading because the upgrade process uses a restore. To free up the extra disk space used by the unnecessary backup file, after the restore was complete manually delete the \ProgramData\Tableau Server\data\tabsvc\pgsql\data.bak-*. folders. For more information, see the Tableau Knowledge Base.


Version 9.0: The Query Project method in the REST API required system administrator permissions. As a result, non-administrator users could not query projects.


Version 9.0: You could not add an Active Directory user unless you used a fully qualified domain name. For example, adding the user "myco\jsmith" would not add the user, but "myco.com\jsmith" would add the user successfully. For more information, see the Tableau Knowledge Base.


After you upgraded Tableau Server, the subscription icon for published views no longer appeared.


Version 9.0: When a port is dynamically remapped at server startup, the entry for the host was not getting updated with the new port information. If this happened a message displayed when Tableau Server started:
"*** Changed filestore.port port(s) from to .
*** Changed filestore.status-port(s) from to .
===== Unable to determine if all compoonents of the service started properly. See "tabadmin.log" for more information"
and some functionality in server was not available (for example, you could not publish a workbook or data source).
For more information, see the Tableau Knowledge Base.


When exporting a dashboard from Tableau Server to a PDF or image file, extra lines appeared near the top of the view.


Version 9.0: The Publish Workbook REST API method did not support publishing with tabs.


Version 9.0: Attempting to edit a published view when the view name included special characters (like a space) resulted in the error: "VizPortal Error: {"code":80039}".


Version 9.0: When a site administrator ran a schedule (clicked on Run Now on the Schedules tab), all subscriptions on that schedule were run, including those for other sites on the server. This could cause extra email notifications and extra load on the server due to running multiple subscriptions.


When you exported a published workbook as PDF, the page size didn’t use the value specified in the Server PDF Export dialog box. Multiple exports sometimes had different page sizes or orientations.


Version 9.0: When you upgraded a distributed installation with a data engine on more than one node, the upgrade process left original (unmigrated) extracts on the second data engine node after the upgrade was complete. For more information, see the Tableau Knowledge Base.

Tableau Mobile (Back to top)
Issue ID

A web page embedded in a dashboard would not render properly.

This version is available from the Customer Account Center.