Known Issues

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

When using a relative date filter, the filter and Change list displayed the incorrect date range, although the data returned was correct and could be verified by examining the profile pane.

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

In Tableau Server 2018.1 after initial load, any interactions with an embedded view accessed using trusted authentication would result in a repeated error: "An error occurred communicating with the server (500)"

When attempting to open or web-edit a workbook connected to TabPy on Tableau Server, an "An unexpected error occurred. If you continue to receive this error please contact your Tableau Server Administrator" error sometimes occurred.

When selecting Download Data in Chrome with the Grammarly extension installed, an  Uncaught TypeError: Cannot read property 'parse' of undefined error occurred.

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.

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.

For users with the Creator role, an Integrated Authentication option appeared when connecting to data which failed with a Access denied error

In Tableau Online, sometimes viz-in-tooltips failed to load.

When viewing a story published to Tableau Online, Tableau Server 10.5.2, or Tableau Public using Safari on a Mac, text in the dashboard textboxes was being cut off with ellipses despite word wrap being set to On or Automatic.

32-bit versions of Tableau Desktop would receive an error when attempting to sign into Tableau Server: Internet communication error: A libcurl function was given a bad argument

When connected to a MapR distribution of Apache Drill, a Drill failed to execute the query errorwould occur when you tried to create groups with dimension members containing non-ASCII characters. The fix requires upgrading to the latest MapR Drill driver in addition to upgrading Tableau Desktop.

When formatting field labels, any corner shading applied would get applied to the top and bottom of the axis.

In some cases, refreshing the data source would cause all sheets in the workbook to be refreshed instead of only the active sheet.

On some computers running Symantec software, Tableau Desktop would become unresponsive when performing normal authoring work.

In some cases, filtering on a group containing at least 8 dimension members would result in a no such column error.

Users were allowed to publish an extract-only data source (e.g. Salesforce) from the Server menu in the Data Source page before the required extract was created.

Viewing full underlying data in a view connected to Oracle would either show the incorrect number of rows or no data at all.

Certain level of detail calculations returned incorrect results only in Tableau 10.4.x.

The layout of filters in a dashboard could be compressed if the dashboard was initially loaded when in presentation mode.

Changing the mark type to Map in a map view would cause the map to re-center.

The REMOVEINSTALLEDAPP installer property failed to remove previously installed versions of Tableau Desktop or Tableau Reader.

Views did not update with new data after performing an incremental extract refresh in Tableau Desktop.

The layout of filters in a dashboard could be compressed if the dashboard was initially loaded when in presentation mode.

Certain workbooks could result in a large number of CASE expressions when using a Hyper extract, resulting in poor performance.

Color palette assignments, based on combined fields with dimensions from different data sources, would be lost when the workbook was reopened.

An ambiguous table reference could occur when connecting to certain Cisco Information Server data sources.

In some cases, custom filter titles could revert to their original name upon opening a workbook.

When connecting to Excel files containing Japanese data, big and small Katakana characters were incorrectly recognized as equivalent. Deleting existing shadow extract files (.hhyper) may be required to see the correct behavior after upgrading Tableau Desktop. On Windows platforms the files are located in Users\\AppData\Local\Tableau\Caching\TemporaryExtracts and on Mac these files are located in ~/Library/Caches/com.tableau.caching/TemporaryExtracts.

Selecting a large number of marks (~100 or more) and then choosing to Keep Only or Exclude those marks would result in an internal error.

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

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

Editing custom SQL in a saved, packaged data source (.tdsx) containing a Firebird connection would fail with an error.

Type in date parameters with a specified step size would display the incorrect date for some input values.

No values would be returned when you connected to a Microsoft SQL Server stored procedure containing a nested stored procedure.

In some cases using a combined field, in combination with a table calculation, in a view with grand totals turned on would result in overlapping marks.

On Mac systems with switchable graphics, Tableau Desktop would default to discrete graphics instead of switching from integrated to discrete when needed.

Adding an aggregated calculated field to the Filters shelf in a view with Aggregate Measures disabled would cause unexpected behavior.

Saving an extract to a network folder, or opening a workbook containing an extract from a network folder, would regularly fail with a number of network related errors.

Connecting to an OData v4 data source could fail with an error: Bad OData Format. Make sure you are using a URL that points to a valid OData Source.

If you connected to a data source, hid fields, and then extracted the connection, changing the data type of a field and then returning to the Data Source tab would cause all the hidden fields to reappear.

Setting ATR duration, for virtual desktop support, to a value over 24 days would cause Tableau Desktop to become unlicensed after only 3 days.

When opening a Tableau Desktop workbook and viewing a worksheet, the Filters and Marks cards became excessively wide.

In some cases, changing a filter selection could cause the filter width to shrink with each successive change to the selection.

For Mac, using the keyboard shortcutCommand-A toselect all field values causes the Profile pane to close and selects all steps in the flow instead.

When you created a text connection by opening or drag-and-dropping a non-text file, all the text files in the same directory showed in the left hand pane.

Creating multiple wildcard unions from the same directory sometimes led to errors when running the flow.To work around this issue, create only one wildcard union input step per directory.

In branched flows, changes didn't always update correctly. For example, if you created a filter on a step in a branch, and then switched to a step in the other branch, you might not see the unfiltered state for that step.To fix the issue, select a step that doesn't include the filter and then go back to your original step and the results should update appropriately.

Opening a flow by double clicking the .tfl file could create an errant _Repository folder in the path of the .tfl file.

Tableau Prep would fail to launch, with an error, if your Documents folder path was inaccessible: A Javascript error occurred in the main process

Opening a saved flow could, in some cases, cause your database credentials to become locked out.

When you created a calculated field on a node which contains a rename step, and there are transformations later in the flow, sometimes Tableau Prep quit unexpectedly.

Publishing a large workbook would fail with an HTTP 502 error if the publishing process took longer than the wgserver.session.idle_limit setting value.

When publishing a .TDE to Tableau Online or Tableau Server 2018.1.0 via the Tableau SDK, a BAD_PAYLOAD - Unknown response from the server. Make sure this version of the Tableau API is compatible with your server. error sometimes occurred.

After a repository failover event, users were unable to sign into Tableau Server if it was configured for site-specific SAML.

The radial selector tool would fail to select marks outside of the initial visible area for views set to an increased zoom level or filtered to a subset area.

If your server has a project with no owner, sorting the Projects view by an attribute other than Owner (e.g. Name, Created, etc.), and then subsequently trying to sort by Owner, would cause the view to display no projects.

When you signed into Tableau Server and then switched sites, clicking the Tableau logo would redirect you to the Projects view of the original site that you signed into.

Updated 7zip components to version 18.1.

Some older 9.x based workbooks would take a longer time to open in Tableau 10.x or higher than in prior versions.

Color legends for marks with partial opacity did not display with expected colors in Chrome.

Publishing a non-packaged workbook (.twb), that connected to a data source in a UNC path, via tabcmd would fail with an error: LastWriteTime: Cannot get modification time of non-existent path

An Uncaught TypeError: Cannot read property 'imageElement' of undefined error would occur when loading some views in a browser.

Using a relative date filter from a published SAP HANA data source could cause the Data Server process to crash.

Selecting and grouping marks in a view could result in a session ended by server error.

The tsm maintenance backup command could fail with an error: Backing up database failed: 'org.apache.thrift.TApplicationException: Internal error processing completeCreateRolesAndDatabases'

In a 3+ node Linux environment, if the initial node went down, moving the TSM controller to another node would fail.

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

Views connected live to Google Sheets would successfully refresh with new data the first time the refresh button was pressed but then fail to refresh with any subsequent presses of the refresh button.

When defining variables and input parameters for SAP HANA connections in web authoring, unexpected parameter values would appear in the dialog drop down menu.

In environments with large Active Directory groups (2000+ members), syncing groups would intermittently fail. The issue was caused by a large default retrieval size (1500). To mitigate the problem, the retrieval size is now configurable using the wgserver.domain.ldap.members.retrieval.page.size setting.

In some cases, double clicking on a mark would cause the view to become unresponsive.

When connected to certain extract-based published data sources, adding a filter to context would result in losing the connection and/or an error: MEASURE expressions must be aggregate or depend only on GROUPBY

Scrolling a filter with more than 5000 values could cause some unexpected behavior with certain web application filters/firewalls.

In multi-node environments, running the tabadmin ziplogs -p command would include the same workgroup.pg_dump file in each node's zipped logs.

Some workbooks performed much slower when upgraded from an earlier version.

When exporting Euro currency formatted numbers to CSV, the results differed between Tableau Server on Windows and Tableau Server on Linux.

The REST API method to query sites would fail with an Unauthorized error message if any site on the server happened to be locked for a task (e.g. exporting a site).

In some cases it was not possible to click the drill-up button in a header for a dimensional hierarchy because it would be obscured by the sort button for an adjacent dimension header.

Adding values to a Multiple Values (custom list) filter could cause extremely slow performance when updating the view.

The Manage link in the Subscribe dialog did not work in Internet Explorer 11 on Windows 7 systems.

In some cases, users were not able to sign into Tableau Server when it was configured to use OpenID Connect authentication with ADFS as the IdP.

Running the refreshextract command using tabcmd on a Linux machine would fail with an error: Workbook url Code could not be found. (errorCode=7)

Published workbooks connected live to a JSON file failed to refresh with updated data.

Some views failed to load with a column is not available after aggregation error.

Interacting with a view sometimes resulted in an error: Uncaught TypeError: Cannot read property 'zoneId' of null

Drill down buttons, in some views, would be incorrectly positioned over labels.