Known Issues

Connecting to a local cube file (.cub) would fail inconsistently with various errors.

Column borders in workbooks created in Tableau 9.2, or prior, were not visible when the workbook was opened in Tableau 9.3 or newer. It was also not possible to add them.

When you explicitly set the geographic role of a field to None, the setting would not be retained after you edited the data source, refreshed an extract, or saved the workbook as a packaged workbook.

If a data connection is lost (e.g. timeout or disconnected network), adding a field into the view would error instead of prompting to reconnect.

Tableau Desktop sometimes became unresponsive when using multiple parameters with a data source based on a stored procedure.

Certain data blending scenarios, involving an SAP HANA data source as the primary data source, stopped working in Tableau 10.0 or higher when they worked in previous versions.

In some cases, colors assigned based on a calculated field did not persist when closing and reopening a workbook.

An intermittent crash would occur, when creating a connection to Google Analytics, if dimensions and measures were selected too quickly.

In some cases, extracting a published data source would unhide hidden fields in the data pane.

Published extracts based on Custom SQL could not be refreshed using the Data Extract Command Line Utility or the Online Sync Client (Tableau Bridge).

The drop down menu arrow in the Pages controls did not show as expected.

After upgrading to Tableau Server 10.2 or higher from a previous version, some views began timing out when you tried to load them.

When embedded credentials was disabled, non-admin publishers trying to save a workbook in web authoring would encounter an unexpected error.

When you refreshed data in a view using the toolbar button, performance when reloading the view would sometimes be very slow.

If a workbook contained a Multiple Values (Custom List) filter, and was published with Prompt User authentication, an error would occur when the workbook was viewed in Tableau Server.

Published data sources containing custom SQL with parameters joined to other tables would fail to load with an error: Custom SQL relation refers to a non-existent parameter

File Store process status was not available in distributed environments configured using hostnames containing capital letters. Please see http://kb.tableau.com/articles/issue/filestore-status-not-available-after-upgrading-to-10-3-0-in-distributed-environment for details.

Activating or refreshing a license key for Tableau Server would fail with a maximum activations error more often than expected.

In some cases, web authoring in Safari for iOS would fail to load with an error.

"TypeError" or "Script Error" or "Uncaught Error..." When Loading Tableau Online and Tableau Public Views. Please see http://kb.tableau.com/articles/Issue/unable-to-load-tableau-online-and-tableau-public-views for details and resolutions.

Formatting text in a sheet on dashboard would sometimes cause text in other sheets on the dashboard to shift unexpectedly.

Updated psqlODBC drivers to version 09.06.0200. This version includes an updated version of OpenSSL 1.0.2k.

Creating an extract of a data source containing a union of text files joined to another text file would fail with an error.

Updated Firebird components to version 2.5.6.

In some workbooks, refreshing the view would cause the view to go blank due to filter selections becoming deselected.

When you used a synchronized dual axis, and the secondary axis contained null values, the displayed marks would not line up correctly with the axes.

When Tableau Desktop was left open and idle for an extended period of time, you would would be prompted multiple times to reconnect to Tableau Server or Tableau Online upon returning.

Workbooks connected to published data sources, containing parameters with large numbers of selections, loaded considerably slower than equivalent workbooks using embedded data sources.

When connected to Exasol in Tableau Desktop, TIMESTAMP WITH LOCAL TIME ZONE fields were not visible.

Refreshing a published, Snowflake connection based extract, using the Tableau Data Extract Command Line utility, would fail with a There is no active connection to the data source error.

Exported summary data for some views appeared to be rounded incorrectly when compared to the values shown in Tableau Desktop.

When you attempted to join Google BigQuery tables containing identically named columns, but with different letter casing, a Duplicate column names in the result are not supported error would occur.

Some extracts, created using the Tableau SDK, would cause Tableau Desktop for Mac to crash when connecting to the extract.

When connected to Hortonworks Hadoop Hive, calculations containing the DATEADD function would return null values when they did not in prior versions.

Workbooks created in Tableau 10.1.3, 10.1.4, 10.1.5, and 10.1.6, that connected to Splunk, could not be opened in other newer versions of Tableau Desktop.

The Sheet Sorter navigation button would become unresponsive after the first use.

When using an Other Databases (ODBC) connection the list of available tables would disappear, and need to be reloaded, after any table was added to the join canvas.

Tableau Desktop would sometimes crash when utilizing geometry fields containing null values.

Restored the Microsoft Azure HDInsight Service authentication option to Hive-based connectors.

In some cases, data based on a pivoted field would return null where non-null values were returned prior to Tableau 10.2.

When editing an extracted file-based data source in a packaged workbook, a file not found error would occur and no option to locate the underlying data source file would be presented.

Workbooks connected to HANA via single sign on would incorrectly prompt for credentials when loaded.

If you disabled automatic updates for filters in a sheet, and then tried to copy the sheet to another workbook, an error would occur.

In some cases when a dimension is used as a filter, values from INCLUDE and EXCLUDE level of detail calculations did not sort or total correctly.

Using the Tableau Data Extract Command-Line Utility to refresh a published extract, based on a local text file, would fail with errors.

When you exported a very large crosstab to Excel in Tableau Server, a Session Ended by Server error could occur due to resource exhaustion. Tableau Server now warns that the export is too large and will not permit the export.

In the Open workbook from Tableau Server dialog, you could select a workbook to be opened but the selection sometimes would not be highlighted.

Size legends would appear unexpectedly and show 'Null' when all values were filtered out in some views.

The order of parameters in the Edit Reference Line, Band, or Box dialog did not remain consistent.

Corrected map polygons for Florida zip codes 33556 and 33147.

When you filtered a view using a group, the view would sometimes become blank after modifying and applying the filter.

When using map small multiples, custom polygons could sometimes overlap between the separate map panes.

Opening older workbooks connected to SAS files would sometimes fail with Cannot get modification time of non-existent path errors.

When you used a calculated field, containing an INCLUDE or EXCLUDE level of detail expression, as a filter and selected All Values, the field would either become invalid or the view would not get filtered correctly.

Corrected the border for the province of Zeeland in the Netherlands.

In some scenarios, involving calculated fields or sets based on a user filter, changing the user did not refresh the view to show data based on the newly selected user.

In some cases, opening a workbook connected to Amazon Redshift would fail with a No such column error.

Appending data from a file to an extract created from a file-based data source would fail with an error.

When connected to Google BigQuery, custom SQL statements containing tab or carriage return characters would fail to execute with a parse error.

Excess Kurtosis summary data was not calculated correctly for some data sets.

When you show totals in the view and you want a table calculation filter to apply to the totals, you can now select Apply to totals in the drop-down menu for that filter (on the Filters shelf). This option lets you decide when a table calculation filter should be applied to totals.

When you use the Latest Date setting for a discrete date filter, the latest date setting applies only to data source filters in a workbook. If you are using additional filters in a view (including relative date filters and context filters), the Latest Date setting may result in an empty view with no data when those additional filters do not select data from the latest date in the database.

When connected to a Hive data source, converting a string field to date would return null values.

Editing aliases for discrete fields would sometimes result in an internal error.

Tableau Desktop would take an unreasonable amount of time to launch on some Mac systems. A workaround was to remove .local from the machine host name.

Certain custom WMS maps would be rendered with large white gaps in map tiles.

In some cases, when connected to an extracted data source, using a calculation involving the RANK function would result in a no such column error.

When you were connected to Microsoft Analysis Services, trying to use certain calculated fields as a filter would result in a No such column error.

Tabcmd export would fail if the URL to the view contained a dollar sign ($).

When you published a workbook via tabcmd, and it failed for a valid reason (e.g. incorrect data source information), subsequent attempts to republish the workbook would continue to fail even if the issue had been corrected.

Views would intermittently fail to load without any error and appear blank in Tableau Server due to underlying calculated fields being incorrectly evaluated as invalid.

Certain workbooks would encounter a Session ended by server error when you changed a parameter selection.

Data Server processes would sometimes crash when loading a dashboard with multiple sheets connected to a text file in a network shared folder.

In some cases, published views connected to a published data source would render with incorrect values due to fiscal year start being inadvertently ignored.

A Version mismatch error would intermittently occur when loading views, typically when Tableau Server was under high load.

If a dashboard had a name that was longer than 160 characters, an error would occur when you tried to download it as an image or PDF.

In some cases old extracts were not correctly cleaned up, potentially resulting in low disk space issues.

In workbooks containing a live file-based connection using a UNC path, and an extracted cross-database join connection that also included a UNC path based connection, refreshing the workbook extract would cause the standalone live file-based connection to fail to update.

In some cases when you used a fixed axis, not all marks would be displayed after publishing the workbook to Tableau Server.

When your Tableau Server language was set to a European language, or Japanese, it was not possible to add a user permissions rule to a published data source.

When certain font and font size combinations were used, axis labels would be truncated if the axis title was hidden.

The JavaScriptAPI getMarksAsync() function failed to return information for some larger, more complex crosstab views.

Loading certain dashboards would fail with a Cannot read property 'substr' of undefined error.

When you tried to load different revisions of a published workbook, the same revision version was always displayed.

Labels for heat map views, created using square marks, were not displayed past the first page when the view also utilized multiple pages.

Data Server processes would sometimes hang when you loaded a workbook connected to a published data source based on a text file located in a shared network folder.

When you enabled external SSL using a certificate key passphrase, the gateway process would sometimes fail to start.

Previously, turning off the Data Server global protocol pool (native_api.dataserver_single_protocol_pool) would also turn off the global query cache as a side-effect. Now, global query cache is controlled by a separate setting: native_api.dataserver_single_query_cache_service.

Depending on the browser, vertical or horizontal scroll bars would sometimes appear in legends after publishing a workbook to Tableau Server.

Workbooks with a large number of invalid field references would sometimes take a very long time to load.

When publishing workbooks with a mix of user specific and non-user specific views, preview thumbnails would be generated for user specific views.

For some views, if you subscribed to the view and selected the Don't send if view is empty option, the subscription would always fail with an error: Failed to perform data condition evaluation...java.lang.RuntimeException: Some subscriptions were not sent successfully

Hiding the navigation bar in Tableau Server worked inconsistently.

When you signed into Tableau Server using SAML, and only had access to the Default site, you would still be prompted to choose a site to sign into.

The download image and download crosstab dialogs in Tableau Server did not render correctly.

When viewing a viz in a mobile browser, a small banner encourages users to open Tableau Mobile, or to install the app if they don't have it.

Subscriptions for views based on published live data sources would sometimes fail with an error: view could not be rendered

In some cases, it was not possible to deselect filled map marks.