Download Now

This version is available from the alternative download site.

Release Notes for Tableau 9.3.1

If you use the Tableau Online Sync client from Tableau Desktop on Windows to refresh extracts on Tableau Online, please upgrade Tableau Desktop from 9.3.1 to 9.3.2. For more information, see the Release Notes for 9.3.2.

Note: Tableau Desktop customers in environments with Product Updates enabled will be prompted to upgrade a few days after a maintenance release is made available. For more information, see the Tableau Knowledge Base.

Release Date:
May 17, 2016
Desktop Build Number:
Server Build Number:

New Capabilities

This release adds a new connector that gives you the ability to connect to Cisco Information Server.

This release adds support for Oracle 12c In-Memory.

This release adds a new connector that gives you the ability to connect to Kognito 8.1.

Tableau Desktop (Back to top)
Issue ID

Connections to some databases from Tableau Desktop would fail to drop some temporary tables upon connection close.


When connected to HP Vertica in Tableau Desktop using a version 7.1.x driver, Unicode characters were not displayed correctly.


In Tableau Desktop, when publishing a workbook or data source utilizing an Other Databases (ODBC) connection, there was no option to publish with embedded password authentication.


In Tableau Desktop, when you used multiple SAP BW extract data sources in a workbook, refreshing any one extract overwrote the other extract data sources with the same data.


In some cases in Tableau Desktop, changing the scope for mark labels from Table to Pane had no effect.


When connected to Sybase ASE in Tableau Desktop, the Sort by Field option was not available in the Sort dialog when sorting a dimension.


When connected to a cube data source, sheet titles that dynamically changed with filter selections would sometimes fail to display the correct values.


In Tableau Desktop, when you clicked "Yes" in the warning dialog box to embed data source credentials when publishing, credentials were still embedded even when "Allow publishers to embed credentials in a workbook or data source" was unchecked in Tableau Server general settings.


Extracts in workbooks published to Tableau Server fail to refresh with a "cannot evaluate user filter; no current user or group" error when the extract was part of a data source containing a user filter.


Changing a workbook parameter that was tied to a Microsoft SQL Server stored procedure parameter would sometimes cause Tableau Desktop to become unresponsive.


When connected to SybaseIQ in Tableau Desktop, attempting to edit a Top N set filter would fail with an error.


Borders between filled map shapes would unexpectedly appear when exporting the view to an image or publishing to Tableau Server.


In Tableau Desktop, using an Microsoft SQL Server datetime2 field would sometimes result in an error: "The conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value.


When signing into Tableau Server from Tableau Desktop, the remembered user name would drop the domain prefix if it had been previously entered.


Color palette changes were sometimes not saved in Tableau Desktop. The issue may still occur but it is now possible to reset color assignments and reapply a color palette to correct the issue.


In Tableau Desktop, filters containing table calculations would sometimes cause row and column grand totals/sub-totals to disappear.


Hidden or invalid fields in a data source, that were not visible in Tableau Desktop, would sometimes appear when using web authoring in Tableau Server.


In Tableau Desktop, when connected to a Salesforce data source, if you changed the data type of a field and then edited the data source it was possible to end up with a broken data source.


When joining tables, the default join relationships were often not the expected ones.


In Tableau Desktop, when you opened a workbook connected to a published SAP HANA data source containing prompts, a blank worksheet without prompts appeared until you refreshed (F5) the data source.


In Tableau Desktop, connecting to an OData data source utilizing digest authentication was not supported and attempts to connect would fail.

Tableau Server (Back to top)
Issue ID

When you tried to delete a Tableau Server project containing a period in its name using the 'tabcmd deleteproject' command, an error occurred and the delete failed.


When upgrading Tableau Server in a distributed environment the error message "Worker initialization failed" would sometimes occur due to certain tasks failing to run in an expected amount of time.


When you published from a non-English Tableau Desktop to either the default or "Tableau Samples" project on an English-locale Tableau Server, a fatal error occurred: "Unable to get default permissions for publishing."


When exporting a PDF from Tableau Server, the "The PDF file has been generated" confirmation dialog was centered in the visualization rather than the browser window.


Tableau Server log files would consume excessive disk space in environments utilizing a large number of cube data sources.


When you used a Microsoft Analysis Services data source in web authoring on Tableau Server, fields were not organized correctly and were sometimes missing in the data pane.


In Tableau Server, changing certain filters would sometimes cause one or more sheets in a dashboard to grey out and not update as expected.


In Tableau Server, initial database errors that occurred when executing multi-statement initial SQL weren't reported correctly.


In some cases in Tableau Server, involving workbooks connected to published data sources, loading a workbook that had been previously loaded would result in a missing attributes error.


In Tableau Server 9.1 or later, if there were multiple subscription schedules for the same workbook, they didn't run in parallel as they did in prior versions.


Upgraded Xalan to version 2.7.2.


When connected to a cube data source, sheet titles that dynamically changed with filter selections would sometimes fail to display the correct values.


In Tableau Server, temporary files related to incremental extract refreshes were not being removed in a timely manner. This resulted in excessive consumption of temporary disk space.


In Tableau Server environments configured with only a single data engine process on a worker machine, the worker would repeatedly become unlicensed over time.


Tableau Server group membership would sometimes fail to update until Tableau Server was restarted.


In Tableau Server configured with multiple nodes but no Data Engine process on the primary node, restoring a backup would fail to clean up the original data engine folder from the backup resulting in wasted disk space.


Tableau Server group membership would sometimes fail to update until Tableau Server was restarted.


In some environments, upgrading to Tableau Server 9.3 from a prior version would fail with an error in tabadmin.log: "NativeException 'java.lang.IllegalArgumentException: Processor number (##) must be less than the number of CPUs: ##."


Tableau Mobile was unable to connect to Tableau Server via SAML when ADFS was used as the IdP and it was configured to use forms-based authentication.


Loading live connection-based views in Tableau Server would show an infinite spinner and fail to load under certain conditions.


When selecting multiple data sources at a time for updating in Tableau Server, saving any changes would appear to be successful even if you did not have permissions to update one or more of the data sources. Despite the appearance of success, changes were not actually saved.


In workbooks containing multiple data sources, and published to Tableau Server with embedded credentials, editing one or some of the connections in Tableau Server would fail with an error.


In Tableau Server general settings, the "Synchronize All Groups" action only synchronized a group on one site if the same group existed in multiple sites.

This version is available from the Customer Portal or Alternate Download Site.