Known Issues

When using the NOW() function with a live connection to Snowflake, Tableau followed the data source location time instead of the time configured on the data source server.

When trying to create an extract of Sybase ASE using a MAX() or Top N extract filter, the extract would fail.

Sometimes, nested level of detail calculations in a workbook produced an "Error occurred communicating with the data source. No such column [Calculation_]." error message.

Updated German county data.

Updated German postcode data.

Updated Australian postcode data.

After you refreshed an extract, saving the workbook would silently fail to retain the extract location if the extract was also open in another instance of Tableau Desktop, resulting in an "Extract not found" error upon reopening the workbook. There is now a warning for the failure and you are prompted to specify an alternate location to save the new extract data.

Many Thai vowel characters were not rendered correctly in Tableau Desktop.

Updated Turkish postcode data.

Updated province data for the Democratic Republic of the Congo.

Using a calculated field containing a spatial geometry field and an failed conditional statement could result in an error: "unable to deduce expression type, use 'NULL::' to specify the type"

When you added description text to a story point, and then deselected the text object, you could not format the description again.

When doing a wildcard search on a pivoted field based on a .csv data source, a "collation mismatch" error sometimes occurred.

When you connected to an Odata feed from a non-default namespace, an "Odata: Cannot find corresponding ComplexType" error occurred.

When using Tableau Desktop with Microsoft Office IME 2010 Japanese, re-entering Japanese words do not convert them properly in the field name search. It looks like incremental auto-search is interrupting the IME character conversion and resulting in unintended characters appearing in search string.

int64 field in OData sometimes rounded incorrectly.

When using a cluster in a workbook, extract refreshes sometimes failed with the error "Unable to complete action Internal Error - An unexpected error occurred and the operation could not be completed."

When you changed a "Multiple Values (dropdown)" filter to select no values, then a single value, an "Unable to Complete Action: Table Arrays Must be of the Same Size" error occurred.

Creating an extract in a remote shared folder using Tableau Desktop 2018.2 on a Mac failed with an "fcntl(): Operation not supported" error.

Selecting Total Using > Server with an ASO cube resulted in a “value 'Server' not in enumeration” error.

When you used a filter on a data source with a non-January fiscal year start, sometimes an "Unable to complete action Internal Error - An unexpected error occurred and the operation could not be completed" error occurred.

In some cases, valid calculations returned an "Invalid datetime error" error message.

When running certain kinds of queries against data stored in Google BigQuery, you can connect to tables and run queries that return small amounts of data, but if you try to return a larger amount of data or create an extract you will encounter this message, "An error occurred while communicating with the Google BigQuery data source (table name)".

In Tableau Desktop maps, two states in Malaysia (Sepang & Patrajaya) show incorrect boundaries.

Sometimes, Tableau Prep output preview data was different from the actual output data.

Using a "keep only" filter resulted in fewer rows in the output than seen in the preview pane.

When port number is not specified in the tfl flow file, command line refresh is not able to match the connection. Error will read: “could not find match for [server name]”

When running a backup, the following error sometimes occurred, "Did not parse exactly one backup result, got 0."

In Tableau Server on Linux environments, Microsoft Azure SQL based published data sources failed to connect to the database when you published them with prompt user authentication.

Workbook size was inconsistently reported between the Stats for Space Usage administrator view and the Workbooks content view.

When you called the REST API method "Query Datasources", the field "createdAt" showed the same value as "updatedAt".

When using Rest API 3.0 code to access user information, only old Site Role names were returned.

In some multi-node Tableau Server clusters, it was not possible to generate log snapshots via the UI.

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 running manual or scheduled Snowflake extract refreshes on Tableau Online and Tableau Server 2018.2, the refresh task fails with "Missing Password" error.

After upgrading to Tableau Server 2018.2, the application would sometimes hang after entering a username/password for non-default run as user. Additionnaly, this issue sometimes occurred after entering the wrong username or password.

When publishing a workbook connecting to multiple Google Sheets, the Google Sheets’ authentication screen repeats itself multiple times before the workbook publishes and appearing as if each Google Sheet needs to authenticate individually.

Upgrading Tableau Server to version 2018.2.1 fails at 10-14%, if service.backup.pgonly is set to "true".

Tableau Server 2018.2 install fails, when using a domain account starting with the letter U for the Run As Service account.

When trying to change the Run As Service Account name in TSMUI with a netbios name that contains a period, an error occurs: "The username must be specified as 'domain\user' with the domain being in the short (NetBIOS) format."

Interactor or Explorer site role using seat-based license key unable to connect to published data source via Web edit after upgrade to 2018.1.

When viewing the Site Status "Background Tasks for Extracts" administrative view in Tableau Online and Tableau Server, red "Error" marks are not shown for failed refreshes when client language is set to a non-English language.

Date filters with "only relevant values" selected did not respond when viewing in Safari on iOS.

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

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.

Upon opening views on Tableau Online, users might intermittently encounter an Unknown Server Error stating “TableauException: Cannot find a total needed to compute a percentage. The database may have changed or a calculation cannot be completed. Try refreshing your connection or editing the calculation.”

An "Uncaught Invariant Violation: Minified React error #40" error occurred intermittently while loading certain workbooks in Tableau Online.

When appending data to a .hyper extract that uses a SAS data source, the errors "Cannot find file, Replace with another?" and "Unable to append" occurred.

Japanese words did not convert properly when entered in the field name search box using Microsoft IME.

When connected to OData, the values for fields with the same name were not differentiated.

After creating a SAP BW extract in Tableau Desktop 10.5.4 and earlier versions, and then refreshing this extract in 10.5.5 or later versions, the date fields in the extract break: all dates are either showing as NULL, "30/12/1899" or similar. The date fields in SAP BW are of type "DATS".

In workbooks connected to a Sharepoint List, calculated fields would be removed from the data source after you edited the data source and had to re-authenticate the data connection.

Calculated fields would appear to be invalid when you edited an OData data source.

In some cases, decimal data would not be properly aggregated and result in unexpected or missing marks.

When you clicked "Describe" on a calculated field, sometimes an "A query error occurred. No description available" error occurred.

When using a high resolution image as a background image in Tableau Desktop on a MacBook Pro with a Retina Display, the text on background image was distorted.

In some cases, when connecting to Tableau Server via mutual SSL, Tableau Desktop displayed an "error 6 SSL handshake failed" error message.

When you set a fiscal year start for a date field used in blending, an "Invalid datetime value" error occurred.

In some cases, it was not possible to clear the text from a string parameter.

You could not group fields by data source table in the data pane when connected to a published data source containing an extract and a data source filter.

In some environments, the Edit Axis dialog would appear blank or as a black box.

"tableau.exe -register" command fails when the previous GUI registration was configured with a Country different than US in the Country Section. 

When trying to connect to Hortonworks Hadoop Hive, sometimes an "[Hortonworks][Hardy] (34) Error from server: SSL_connect: certificate verify failed" error occurred.

When you opened a flow in Prep 2018.2.2 containing a null or wildcard filter created in 2018.2.1, a "This flow was created with a newer version of Tableau" error occurred.

When connecting to a file with a carriage return in some field names, an "Unable to run input note: Async operation failed" error message occurred.

When connecting to Presto with LDAP from Tableau Prep, the sign in button was grayed out if you did not include a password.

In Tableau Prep 2018.2.1 and 2018.2.2, it was not possible to remove a double quote " using "Edit Value".

After changing the data source for an input step, saving a .tflx, then opening a .tflx in Tableau Prep 2018.2.3, sometimes fields were missing starting from the first Clean step in the flow and errors appeared throughout the flow.

In flows with multiple joins and self joins, sometimes there was no data shown in the Profile pane, and an "IllegalStateException" error occurred when clicking a step.

When you tried to publish a flow to an SSL-enabled Tableau Server, a blank start up page displayed and the flow failed to publish.

Flow file fails to run in Tableau using "tableau-prep-cli.bat" command, when a .hyper file is used as data source and Tableau Server is destination for the published output.

Sometimes, Tableau Prep quit unexpectedly while joining tables.

Flow file connects to an Oracle database, creates local extract for output, and executes successfully in Tableau prep, but it fails to run in command.

After performing different pivot steps on the same dataset as well as multiple joins, the "group and replace" function is not working on a subset of the field values within the same column. Red dots next to those field values indicate that those values are not contained in the dataset, when in fact they are. 

Sometimes, Tableau Prep stopped responding while adding a step.

When using custom SQL in Tableau Prep, having any text between a less than sign resulted in the error "Error in input "Custom SQL". Can't connect to datasource . An error occurred while communicating with the data source. Custom SQL relation refers to a non-existent parameter..."

When you used a regular expression containing a backslash (\) in a calculation in Tableau Prep 2018.2.3, the calculation returned incorrect results.

When viewing a dashboard in IE 11 which used Javascript embed code, check boxes and radio buttons intermittently failed to display.

When you tried to Save As when web authoring a workbook that used Google BigQuery with embedded credentials, a "This workbook contains a Google Big Query data source which requires embedded credentials. To save as another workbook, select "Embed password for data source"." error occurred.

Subscribe button was sometimes missing from workbooks with embedded Google BigQuery connections.

The Tableau Server Licenses page could sometimes show one additional unlicensed user than expected.

Clicking the vertical browser scrollbar sometimes cleared filter action selections on a dashboard.

An internal error could occur when loading some views.

When web editing an embedded view using trusted ticket authentication, the Save As dialog would not appear when you attempted to save your work.

Scheduled extract refreshes would fail for workbooks containing an extract of a published extract data source and a Viz in Tooltip in one of its views.

In some cases, Tableau Server memory usage could steadily grow and result in poor performance when loading views. A server restart was usually required to restore expected performance.

In some cases, background images would intermittently disappear when reloading a dashboard.

When you edited a published Salesforce data source in Tableau Server, to update the password, the change would not be correctly saved even though the operation appeared to complete successfully. As a result, any scheduled extract refreshes for the data source would fail with an error: "INVALID_LOGIN: Invalid username, password, security token; or user locked out."

In Tableau Server environments installed on German localized Windows operating systems, the data update time inserted in text objects always showed the current time instead of when the data source extract was last refreshed.

When using a monitoring software on the computer running Tableau Server, sometimes users were unable to login, services were down, and vizportal process threads increased rapidly due to the monitoring software continuously sending requests to systeminfo.xml.

In published views with continuous date filters, sometimes a thousands separator comma was inserted in the year (For example, 1995 became 1,995).

Sometimes, performance degraded while exporting a full PDF using tabcmd.

A "Cannot read property 'x' of undefined" error would occur when loading some map views with a large number of marks.

Configuring Tableau Server to allow data repository access would fail if the server was still running.

An unexpected error could sometimes occur, due to VizQL Server processes crashing, when loading some workbooks.

Tableau Bold and Tableau Semibold fonts did not render correctly in published views.

Data source passwords were not remembered even after you checked the Remember Password box when prompted for data source credentials.

After adjusting zoom levels, some column and header borders were missing.

If the time zone on the host system is set to a time zone that is not identified as a named java time zone (Examples: -11:00, -12:00, -3 with 'adjust daylight savings automatically' disabled), TSM fails to initialize at step 13. These uncommonly used time zones in the Pacific makes java default to a generic value for the key Cfg.config.logging.time.zone_id.

In Tableau Server 2018.2, a DataServiceFailure error would occur when using published extracts if the operating system locale did not match one of the languages in which Tableau's UI is available.

Performing a TSM backup could fail if a TSM controller node did not also have a File Store process configured on the same node.

When embedding views using the Javascript API, container div element dimensions in HTML embed code were not respected.

Changing your Tableau Server name to a name containing a Unicode character, using the 'tsm customize --server-name' command, would fail with an error and leave Tableau Server in an unrecoverable degraded state.

Installation of Tableau Server would fail if the specified Run As service account name contained a "\u" character sequence (e.g. DOMAIN\uxxxx).

TSM Controller processes consumed CPU cycles even when Tableau Server was stopped. On lower-spec systems, this could result in continuous high CPU activity.

The Run As Service account cannot be set to use an account from an Active Directory domain that is different from the server’s AD domain.

When running tsm upgrade script with a path containing parenthesis, the install fails with "\Tableau\Tableau was unexpected at this time." during upgrade from 2018.1 to 2018.2.1.

2018.2 TSM Maintenance Backup stops with this error "61% Uninstalling backup services. An error occurred on the server generating the backup."

When you added a node to a cluster using an incorrect Run As User password in Tableau Server 2018.2, the Run As User account became locked due to multiple incorrect password attempts.

Tableau Bridge 2018.2 is not refreshing extracts or maintaining "On" Service mode when logged off.

Upgrade from 2018.2.0 RTO build to 2018-2-0-18-0821-0818 fails with "Error 0x80070666: Cannot install a product when a newer version is installed."

"PQstatus: 1, select() failed: unrecognized socket error: 0x000000E9/233" and "There was problem and the data engine could not start properly.
Unable to create extract" error messages sometimes occurred when refreshing extracts in Tableau Bridge when the OS language was not one of the languages Tableau is available in.

When adding a data source with "不" in the title, an "Unable to finish reading data source" message occurred.

This is a test release note with no real significance please pay no attention to this text.