Known Issues

When publishing or accessing a Tableau Online view that used the TableauServerUser variable with Tableau Bridge, a "Cannot evaluate user filter" or "Unable to connect to the server" error occurred.

Starting with version 2020.4.0, the second page of an exported landscape PDF could be zoomed in to not match the scale of the first page.

After selecting Ask Data, an error would sometimes occur when connected to a large data source, "Encountered the following error and now waiting to retrying indexing: Can't index data due to a system error."

Published workbooks with a NOW() calculation would sometimes not display the correct "Site Time Zone for Extracts" setting.

Tableau Online would sometimes attempt to create indexes on Snowflake temp tables.

With some versions of Tableau Prep Builder, the registration prompt would occur with every launch of Tableau Prep Builder even when Tableau Desktop registration had already been completed.

The 2020.4.1 installer will show a new option in the "Install customizations" to select the option for the ability to "check for product updates". This option is for future functionality and currently does not work.

When loading a step, a message would sometimes display to report, "No fields to display", before displaying the fields or data grid.

After an upgrade to 2020.3, loading a view containing a published extract could fail to load with the error, "Could not find Hyper hosts to connect to. Unable to connect to the Tableau Data Extract server. Check that the server is running and that you have access privileges to the requested database."

Non-current content downloads using the REST API could fail periodically.

Tableau Server enabled with Azure Database as the external repository could fail to initialize if Postgres 12.4 on Azure Postgres Flexible Server public preview was used. The error would display with "Error: Must be superuser to create superusers" or "Error: Must be superuser to change bypassrls attribute."

With Tableau Server 2020.4.0 on Linux Debian 9 (.deb installer), the initialization fails while finalizing the topology after a successful activation and registration. The initialization is terminated at step 31 of 35 with the error "Finalizing the topology failed."

The Debian version does not correctly install on Debian 9. Ubuntu is unaffected

The message "Cannot read property 'get_toolbarCommands' of null", could be received starting in 2020.4.0 when switching to a tab that contains a text object.

With version 2020.4 on Linux, the pre-built Administrative Views would not be available due to the Postgres JDBC driver not being installed by default.

Multiple crash dump folders could be created per day for VizQL or Backgrounder where all call stacks would contain the method DataValue::SetString(Collation const&, char16_t const*).

While executing a query in Impala the error "The table .... does not exist" may occur when refreshing view or setting filters.

Tableau Online admin views sometimes took a long time to load, or eventually timed out.

Connecting to Postgres via Tableau Online was successful, but error "syntax error at or near "ta"" was seen in the PostgreSQL logs.

When a scheduled extract refresh of a Quickbooks Online data source runs on Tableau Online, the following error occurs intermittently: "Intuit API Authentication error: Invalid authentication tokens. Login again and retry."

In Tableau Prep Builder, sometimes bigint data was rounded incorrectly.

String values with capital letters are treated inconsistently in out-of-sample values.

In the new feature for 2020.3.1 called Write to Database, if the database or schema does not have any tables (it is empty), navigating to the schema or database will not be possible. The schema needs to have at least one table created to be visible for selection.

Node became unlicensed when moving the license service to another node in multi-node server environment

Customers who manage the Tableau Mobile app using MDM (e.g. Citrix, AirWatch) on iOS 13+ can now access links to dashboards and metrics on their internal servers seamlessly inside the Tableau Mobile app. This can be done by provisioning those servers through mobile device management software. As of this time, however, we are unable to provide additional guidance for any MDM vendors on how to set up universal linking.

The OffsetTimestamp::toString() would return an incorrect value.

The command line option to refresh an extract would fail when LBLM or Virtual Desktop was the activation method of Tableau Desktop.

A previous sort order would not be retained when changing another sort order using drag and drop.

An incorrect number of rows could be returned when filtering on values that contain tabbed spaces (\t).

Repeatedly pressing Command + v in a calculated field editor to paste text caused unexpected behavior on Macintosh.

When a calculated field related to row level security was added to the data source filter, an error could display that stated "No such function $IN_SET$ that takes arguments of type (null, str, str, str)."

An Oracle extract could fail to refresh that used JDBC and had unicode characters in the column name.

It would not be possible to access the non-default Athena Catalog data with Athena JDBC.

A dynamic parameter action would sometimes behave differently in Tableau Desktop as compared to Tableau Server.

After a workbook was published, the custom SQL query would contain extra line feed characters.

The VizQL Server could hang due to out of memory errors from the Java Heap Space.

A change made to the setting to let users run jobs manually using "Run Now" would interfere with the "Enable Metrics" setting.

After a Prep flow was published, the flow would fail if the data in the text file was tab separated.

When logs were uploaded to a Technical Support case, the TSM web user interface would display "step 0 of 0" incorrectly.

When there was nothing listed in tooltips, a visualization would hang running a dashboard action.

The Tabcmd "runschedule" would not trigger a data source refresh of a published workbook when running a disabled schedule.

Tableau Bridge was not always able to recover after a network failure

The Bridge client could repeatedly become disconnected where a restart was needed.

When an extract refresh was run manually, the Path field could change from English to Spanish when Spanish was selected as the system language.

When network issues occurred, there would be a problem with the connection token which resulted in the Bridge client unable to stay logged in.

Errors could occur with the connection token when the client failed to connect to the Online server.

In some circumstances, when the SMTP host value was set and saved in the Tableau Resource Monitoring Tool, the user interface would change the value listed to 'undefined'. This did not affect the underlying configuration but was an issue in the UI.

It was not possible to edit an axis range of a continuous bin when the range is fixed to set either the fixed start or fixed end to a decimal number.

An error would occur stating, "Invalid SET statement in the triggered action," when an attempt to connect to Teradata with a username that contained an apostrophe was performed.

When a workbook contained a file union, any subsequent workbook open attempts could fail because the column name would not exist in the data source due to a language translation.

The calculated field set in a title of a Viz is displayed as "All" when using a discrete date dimension for a table across or table down calculation.

The Data Quality Warnings would not refresh for a workbook if the data source connection is opened or a workbook with the connection is opened before signed into Tableau Server.

In the Relationship dialog, when a linking field was changed from an integer to a string, the dialog displayed the correct type but the query used the original data type which could result in a "type mismatch" error.

A table calculation could disappear from the view after the data source was published to Tableau Server.

"Error code: 6EA18A9E. Unable to create extract" could occur with text files when selecting a merged mismatched field as a matching field between two logical tables.

Creating an extract from an OData connection could fail after navigating to a worksheet.

CEILING() function could return incorrect results when using a scalar or a constant as the argument.

When a live data source is published over an encrypted extract and the live data source is then converted to an extract, the error could occur stating that "hyper already exists".

Beginning with 2020.3.3, any existing rich discrete value filtering in the users flow or a new flow created in grouped steps, the annotation would not show on the profile card as expected to see the change or to edit it. The work around is the use the changes pane on the left or from the flow pane in the top to access the rich discrete value filtering annotation/change they had made.

An error would sometimes display when a pivot is performed, "Query Text Limit of 67108864 Bytes Exceeded."

The output step after a Left Only join could produce more rows than expected.

A flow execution error could occur after joining an extract and an Excel file, "No such column [Item Name-1]."

When running a flow using an incremental refresh of Salesforce data, an error could occur stating "No such function ISNULL that takes arguments of type (datetime)."

On Macintosh OS, a CSV file with a Japanese file name could not be read.

The user interface could become unresponsive when trying to copy and paste steps by "Ctrl+c" and "Ctrl+v".

When the command line is used to run a flow, an "errorlevel" of 0 would return even if the command failed in some versions.

It would not be possible to complete the Analytics Extensions Connection sign-in when the "Require SSL" checkbox was also marked and a valid SSL certificate was designated trying to access TabPy or RServe.

When using the command line option in 2020.3, Java warning messages could occur when publishing output.

A "collation mismatch" error could occur when running a flow with Microsoft Sql Server that contained a union and a join.

Published data sources would sometimes not be displayed in the Connections pane to search for data. The message would display, "Error: The server encountered an error. Try again."

The command line option to run a flow containing a TabPy script would sometimes display an error, "The Tableau Python (TabPy) server configuration is required. Enter a valid server configuration, then try again."

When running a flow that contains a pivot step, an error would sometimes display, "Failure parsing AQL: No such column {[field]}."

The CEILING() function would sometimes return inconsistent results and also varied from Tableau Desktop.

A system error would sometimes occur when running the sample flow.

"Flow execution error: Failure parsing AQL - LogicAssert itrColumns != inputQueryColumns.end()" could occur when running a flow.

During a new installation if the core key activated was not sufficient to handle the cores on the machine or VM, the installation would fail.

TSM Web UI did not show Japanese when the browser is set to prefer Japanese over English starting in version 2019.2+.

When using a live embedded SAP HANA data source, any non-owner could not view and edit the workbook using web authoring.

Zero grid lines on a graph would disappear after selecting a dashboard filter action with animations.

The REST API previously did not allow for "+" to represent a space character in a filter parameter input.

Broken license fulfillments could display in TSM and be counted by Tableau Server if at least one good product key was activated.

When a URL had the "tabs=yes" specified, all tabs in the workbook appear and the active view was duplicated.

When a workbook or data source was published, the "viewer credentials" authentication option was translated incorrectly in Japanese.

When an attempt to log in with Site SAML using Internet Explorer 11, login would fail with invalid username and password due to duplicate SAML assertions.

When the Resource Monitoring Tool agent cannot read a Tableau Server log folder due to permissions, the agent would stop processing all log information. Agents will now continue to process information from logs that do not have permissions issues.

When an external service was being leveraged on Tableau Server, the Tableau Resource Monitoring Tool could show "unknown" as the status for the Tableau Server Processes.

When an attempt to refresh an Amazon RedShift data source or workbook or to run a subscription containing an Amazon Redshift data source, an error would sometimes occur, "Error trying to execute a query:[SQLState 22PO2] Error: invalid input syntax for integer."

Extract refresh failure notifications could be received in French when the user's language was set to English.

When an attempt to download a workbook was performed, "Error producing PDF!" would sometimes occur.

It was not possible to edit the connection of a JDBC data source.

Refreshing extracts to Salesforce data could fail.

Using special UTF-8 characters in the database name would lead to a parsing error on certain operating system configurations.