Known Issues

When connected to Amazon Redshift, data displayed as null if the field name exceeded 20 double byte characters.

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

Opening Tableau Desktop with a Presto connection on Mac sometimes failed and Tableau Desktop closed unexpectedly.

The Query View PDF REST API request did not honor default page layout settings.

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

The tabcmd publish command with the --replace flag did not correctly clean up old extract files and frequent use could cause your Tableau Server machine to run out of disk space. Restarting Tableau Server would let the extract clean up job run as expected.

In Tableau Online, when you tried to refresh a published extract which was hosted on AWS, sometimes the refresh failed with a "Lost connection to MySQL server during query" error.

When you tried to publish a SAP HANA data source to Tableau Online using a live connection through Tableau Bridge, an unexpected error sometimes occurred, followed by "Data Source ... successfully published, but Tableau could not connect to the published data source."

Sometimes, refreshing an extract using Tableau Bridge consumed a large amount of RAM.

When attempting to view a workbook connected to published data sources, an ERROR: column ... is not available after aggregation error sometimes occurred.

When you connected to text files using a legacy connection and custom SQL, it was not possible to change the text file properties.

When attempting to insert a user filter in Tableau Desktop, if there were multiple Tableau Server groups with the same name, they all showed the user list from the first group created, and the filter selection would apply to all groups with the same name.

When connected to Sybase IQ, strings containing special characters were not rendered correctly.

Added query cancel notifications for PostgreSQL and Vertica connections.

Signing into Tableau Server or Tableau Online from a 32-bit version of Tableau Desktop would sometimes fail with an error: A libcurl function was given a bad argument

An internal error could occur in some cases when you had subtotals displayed in a view and then hid or filtered out a dimension value involved in the calculation of the subtotal.

Data sources published to Tableau Online, containing a live connection to a stored procedure maintained using Tableau Bridge, would fail with a syntax error.

Connecting to some Microsoft SQL Server stored procedures using Tableau Desktop 10.3.6, 10.4.2, or 10.5 and higher would fail to return data.

In some cases, when you opened a workbook based on a Hive data source on a Mac, Tableau Desktop quit unexpectedly.

Creating and saving an extract on a Mac would sometimes cause Tableau Desktop to crash.

In some cases, editing a set would show an unexpectedly large number of set members in the Edit Set dialog.

When connecting to the Campaigns standard Salesforce connection in a Chinese, Japanese, or Korean Tableau Desktop environment, a Table alias is not unique error would occur.

In environments requiring proxy authentication for internet access, Tableau Desktop would sometimes crash after entering proxy credentials.

Sometimes Tableau Desktop closed unexpectedly when performing a Save As on a Mac.

When performing a cross-database join involving a legacy Excel connection, and error would occur: collation mismatch, use COLLATE statements to resolve

When creating or using extracts on an Amazon EC2 m5 (4xlarge) or c5 (large) instance, Tableau's Hyper process sometimes quit unexpectedly with an error.

Dimension members containing the " < " character could cause viz in tooltips to fail to render, resulting in blank tooltips.

Changing the formatting of a continuous date field would cause vertical grid lines to disappear from the view.

Hyper processes could repeatedly go down in environments running on a CPU that did not support the SSE3 instruction set.

In Japanese language environments, filter selections could change when opening a pre-10.5 workbook in Tableau Desktop 10.5 or 10.5.1.

When connected to Google BigQuery, adding a level of detail calculation to the view would unexpectedly remove valid null values from the view.

Materialized calculated fields were removed from published extracts when refreshed using the Refresh from Source option in Tableau Desktop or when refreshed using Tableau Bridge.

Selecting a project when publishing a workbook to Tableau Server would sometimes cause Tableau Desktop to crash. Upgrading Tableau Desktop and Tableau Server is required to resolve this issue.

Level of detail calculations containing user references would disappear from a data source after it was published to Tableau Server.

After upgrading extracts to .hyper, some workbooks would load slower due to calculated fields triggering extremely large CASE expressions.

After upgrading an extract and navigating to a dashboard, sometimes Tableau Desktop closed unexpectedly.

Highlighters would be removed when replacing data sources.

If Tableau Server contained more than 201 projects, the Publish Workbook to Tableau Server dialog in Tableau Desktop would not display all the projects.

After upgrading a .tde file to .hyper, sometimes DATEPARSE calculations would return unexpected results.

Japanese and Korean characters sometimes could not be typed correctly into the calculated field dialog.

When viewing Full Data in Tableau Desktop or downloading Full Data in Tableau Server, sometimes a timeout error occurred.

It was not possible to synchronize groups from a secondary domain using the Tableau Server web UI. The same operation was successful using tabcmd.

Workbook level permissions could not be edited when the Tableau Server user language was set to German.

Updated OpenSSL for PostgreSQL to version 1.0.2n.

Date filter calendar controls would initially appear in the wrong place when the date filter was clicked.

The Query Views for Site REST API endpoint did not return project fields when requested.

Apply and Cancel buttons for filters were still displayed even when there were no items to select in the filter.

Unexpected scroll bars would sometimes appear in filter drop down menus when a view was loaded in Internet Explorer, Edge, or Firefox browsers.

When attempting to restore a backup or add a worker to a server with site SAML configured, a Restore error: Failed to convert SSL certificate to .der format error sometimes occurred.

When viewing workbooks in a thumbnail view on Tableau Server, the star icon to toggle a favorite would not be displayed for workbooks with long names that wrapped to a second line.

Dashboards with device layouts set to fit width did not update to fit when devices were rotated.

Publishing a Web Data Connector (WDC) data source or a workbook containing a WDC to Tableau Server could cause the Data Sources list to display no content if the WDC URL contained a space.

In environments with mixed SAML and non-SAML sites, you could not add a site-SAML user to a SAML site if you had first signed into a non-SAML site and then switched to the SAML site. The converse was also true if you first signed into a SAML site and then switched to a non-SAML site you were incorrectly presented the option of adding a SAML user.

Views connected to Amazon Redshift would fail to refresh with an Error occurred while trying to prepare a query message if the Redshift instance had been rebooted after the view was initially loaded.

Downloading some workbooks in a browser, or attempting to open a workbook from Tableau Server or Tableau Online in Tableau Desktop, would fail with an HTTP 500 error.

The Full Data tab, when downloading data from a view, was incorrectly shown for views connected to cube data sources.

Updating multiple gigabyte extracts from .tde to .hyper via incremental refresh would fail consistently.

Materialized calculated fields were removed from published extracts when refreshed using the Refresh Extracts option in the Tableau Server UI.

In Tableau Server environments where workbooks contain complex and nested calculations, sometimes performance issues and high CPU usage occurred when loading workbooks after extracts were converted to .hyper format.

In some workbooks with complex and nested calculations, when extracts were converted to .hyper format, Tableau Server experienced high CPU utilization and performance degradation.

.hyper extracts published via REST API had a .tde file extension. These extracts were still in .hyper file format and functioned the same way as other .hyper extracts.