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.

In some European locales, double-precision numbers were returned as #ERROR or null.

Query execution errors would occur when you connected to Cloudera Impala using custom SQL with a date parameter.

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.

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.

Printing to PDF was noticeably slower in Tableau Desktop 10.0 and higher compared to prior versions.

Connections to Excel files saved in Excel version 1707 would fail with an error: Errors occurred while loading the data source

When you connected to MySQL, case-sensitive table collation was ignored when custom SQL was used. Custom SQL connections to MySQL now default to database collation.

When you were connected to Snowflake and cast a string dimension to an integer or float, a Numeric value is not recognized error would occur.

SAML authentication from Tableau Desktop to Tableau Server would fail in some environments.

With recent updates to the Amazon Redshift driver, connections could fail with a no pg_hba.conf entry for host error. A workaround was to republish workbooks or data sources with Require SSL checked in the data connection.

In some cases, aggregated calculated fields would return no data after an extract was created.

When you saved a workbook in presentation mode and then re-opened the workbook, the view would not be correctly centered.

In some cases, resetting the color palette in the Edit Colors dialog would not reset colors in the view.

When connected to a data source using custom SQL, if you changed the data type of a field and then created an extract or saved the workbook, extra line feed characters would be injected into the custom SQL query.

In some cases, when you joined multiple tables and performed a pivot, null values would incorrectly appear in Pivot Field Names.

In certain cases involving parameter-based calculated fields used as filters, incorrect or inefficient SQL queries would be generated when connected to Google BigQuery, Apache Drill, or Amazon Redshift, resulting in error or poor performance.

An internal error would occur when you renamed a sheet and then tried to use the controls on the Pages shelf in the sheet.

When the filmstrip was used to navigate between sheets in a workbook, interactions in sheets would cause Tableau Desktop to gradually consume more memory and eventually crash.

When source and target sheets were based on different data sources, filter actions failed to trigger sheet navigation when the action was set up to use selected fields.

An internal error would occur, in some cases, when you attempted to sort a calculated field containing conditional statements.

Extracts would unexpectedly refresh when you switched between the Data Source tab and a sheet tab.

Workbooks loaded using URL parameters would error or fail to respect the URL parameters if the workbook was set to prompt for data source credentials.

When you published a statistical file to Tableau Server as a data source, Name unavailable would be displayed in the Connects To column in the Data Sources view on Tableau Server. Republishing the data source is required to correct the problem.

Session Ended by Server errors would frequently occur when lazy connections were disabled.

Tableau Server VizQL Server processes would sometimes crash repeatedly when a large number of users were concurrently using web authoring.

Tabcmd response times would slowly degrade when the tabcmd export command was repeatedly executed.

Existing workbooks containing Hive or Impala connections with embedded passwords failed to load after upgrading to Tableau Server 10.2 or higher from a previous version.

An invalid JSON error would occur when loading certain dashboards that contained 1 pixel wide objects.

In some cases, complex queries sent from Data Server processes would cause Data Engine processes to consume excessive memory and eventually crash.

An internal error would sometimes occur when loading views after upgrading to Tableau Server 10.2.3 or 10.3.1 and higher.

Desktop license reporting would sometimes show duplicate entries with missing product keys.

Map search failed to return results.

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

If you added an image to a product description, the formatted URL would be displayed in the description instead of the image.

In web authoring, clicking to show all values in a date range filter, and then adjusting the slider, would sometimes fail to correctly update the view.

Subscription emails were not sent if you had the backgrounder.subscription_image_caching setting set to false.

The New Workbook option in the data source context menu would always be unavailable when you first expanded the menu. It would become available upon a second attempt.