Known Issues

Opening older workbooks containing the MAKEDATETIME() function in calculations could result in an error: Mismatched case result types

In workbooks connected to multiple published data sources, it was not possible to correctly reference parameters from secondary data sources in a calculated field due to internal parameter naming collisions.

Colors assigned to an ad-hoc calculated field would often fail to persist after saving and re-opening a workbook, publishing to Tableau Server, or sometimes even after refreshing a view.

Edited size legend titles in bar chart views would revert to the default title when the sheet was printed or exported to PDF.

Dimension member aliases containing a line break character could not be used to filter the view.

Added support for DATETIME fields when connected to Google BigQuery.

When you selected multiple forecast marks from multiple measures and viewed the underlying data, only values from one measure would be displayed in the summary tab.

Updated some postcodes in the Netherlands (9939, 9629, 1114, 1115).

Totals for a calculated field containing a sub-expression that matches the formula for another calculated field could incorrectly inherit Total Using settings.

When connected to a large Excel file, and viewing Data Interpreter results, an error could sometimes occur: We found a problem with some content

When you connected to SAP HANA attribute views, technical column names would be displayed instead of friendly column labels.

When a combined field was used in a view with colors and grand totals, the colors would apply to the totals even when Include Totals was unchecked in the Edit Colors dialog.

When you were connected to a cube data source, adding values to a string parameter using the Add from Field button did not correctly add the values.

In some cases, actions used to navigate between dashboards stopped working after upgrading to Tableau 10.3 or higher.

Some Marketo DATETIME fields were brought into Tableau Desktop as DATE fields and you could not properly convert it to a Date & Time type.

Connecting to some shapefiles would fail in Tableau 10.3 or higher, when they used to work in previous versions.

SAP BW extract refreshes could sometimes fail with a no such table error.

Color palette assignments for ad-hoc clusters were not retained when saving and re-opening a workbook.

The Tableau connector for Google Analytics relies on the Google Analytics API. This API has been experiencing an intermittent issues for some customers where data is duplicated or omitted. Tableau is actively supporting Google's investigation into this issue. At this time, any Google Analytics data retrieved using Tableau Desktop, Tableau Server, or Tableau Online is suspect. There is no reliable way to detect when this issue occurs, though an extract may sometimes fail with a Google Analytics returned empty page message. After Google resolves this issue, a full refresh of any Google Analytics data in Tableau will be required to ensure data consistency. For more information from Google on details and status, see https://issuetracker.google.com/issues/63320055

It was not possible to connect to some Google Sheets with special characters in the document name.

When you hovered over a hyperlink using Tableau Online or Tableau Server and IE11, the hyperlink did not immediately become active. 

Map search failed to return results.

Workbooks connected to spatial files would fail to load with an unknown server error.

Views loaded with the tabs=no parameter in the URL often did not render correctly (e.g. views cut off, random scroll bars, etc.).

Filter titles, that were previously hidden, would be displayed when changing filter selections on mobile devices.

When you viewed a scrollable view in full screen mode, tooltips and filter drop down menus could become misaligned when you scrolled the view.

URL parameters would be intermittently dropped when loading workbooks containing data source filters.

You could not enter special characters into filters, parameters, etc., using the ALT/option key, when interacting with Tableau Server from a browser on a Mac.

An internal error would occur when calling the getSummaryDataAsync() Javascript API function on a view that contained no data.

Subscription email images would be incorrectly generated using tablet layout if your dashboard contained a device specific tablet layout.

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

Aggregated boolean calculations would return False for totals even when only True records existed and the aggregate form was also True.

When you extracted a data source with string fields containing nulls, and converted to an integer, the nulls would be changed to zeros.

Performing a union of Excel sheets could sometimes result in incorrect measure values.

A typically benign error, Failed to load proxy credentials: 'The parameter is incorrect.' showed up excessively in log files, making troubleshooting difficult.

When connected to Oracle Essbase, changing a filter applied to selected worksheets would result in an internal error in some cases.

When copying aggregated decimal values (with 5 or more decimal places) from Tableau Desktop to Excel, the pasted value would sometimes have incorrect decimal placement.

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

An internal error would sometimes occur when the Force y-intercept to zero trend line option was used.

Tableau Desktop for Mac would sometimes quit unexpectedly when publishing a data source to Tableau Online.

When connected to Microsoft Analysis Services, if you had a dimension in the view with a Top N condition applied and then attempted to add a named set as a context filter, an internal error would occur.

In some cases, previously working connections to SAP HANA began failing with a Communication with the Tableau Protocol Server process was lost. error after upgrading to Tableau 10.2 or higher.

When connected to Presto, using a calculated field containing Chinese, Japanese, or Korean characters would sometimes result in an error: There must be two or more concatenation arguments.

The Sort by Field option was not available when you were connected to Apache Drill.

When attempting to connect to Spark SQL, an internal error would sometimes occur.

Extracts on Tableau Server with hidden columns could sometimes be unhidden during an extract refresh.

In some cases, when Hebrew text was used in a parameter and the parameter values were displayed in a dashboard, the word Parameter would be displayed instead of the parameter value.

At smaller display resolutions, the publish workbook dialog could be cut off and you would not be able to click the Publish button.

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).

Views in dashboards, in workbooks created prior to Tableau 10.0, could appear collapsed when the workbook was opened in Tableau Desktop 10.0 or higher.

Backgrounder processes would sometime crash during periodic process restarts. Crash dump files were generated during these periodic events and eventually resulted in excessive disk space consumption.

The Export to PDF dialog would be truncated when you rotated an iPad Mini to landscape orientation and attempted to export a view to PDF using an iOS compatible browser.

In some cases, Tableau Server would become unlicensed after performing a system reboot via the operating system.

A session ended by server error would occur when loading certain workbooks.

Published live connection data sources, containing a larger number of joined tables, could often perform very slowly with noticeable delays after every action taken in Tableau Desktop.

The Get Users on Site REST API call would sometimes return duplicate values.

Auto-complete for calculated fields did not work in web authoring when copying and pasting text into the calculation dialog.

When you published a workbook to a project, and then the workbook was moved to a different project by a server administrator, attempting to publish a workbook with the same name to the original project would result in an error: Workbook name is already in use. Publishing will overwrite the existing workbook.

The New User dialog, when All Sites was selected, incorrectly listed Add users for single sign-on (SSO) authentication with site-specific SAML as an option.

Date filter slider labels were not displayed in the expected date format on mobile devices.

Scheduled extract refreshes could sometimes fail with an error: Bin depends on non-existent field, ignoring bin.

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

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-t... for details and resolutions.

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.

When you embedded a view with the Guest account disabled, after signing in, Tableau Server did not display the view but instead continued to show the sign in button.