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.

When publishing from Desktop 2020.3.6, 2020.3.7, 2020.4.2 or 2020.4.3, the error, "Internal server error. NumberFormatException", could display when an attempt was made to publish a workbook with a data source set to "publish separately".

When signing into Tableau Online from Tableau Desktop 2021.1 and picking a site, the error would display, "Site needed".

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

When an alert is created on a MySQL data source, an error could result when using web authoring stating , "Unable to create alert because there was an error connecting to the data source."

When an additional data source is added using web edit, there is no prompt for credentials.

East Asian characters have the wrong orientation for rotated header labels and axis tick labels.

The text wrap does not display correctly including words being truncated and moved to the next line.

In version 2021.1, the background color of some tables changed causing the text to become unreadable.

In 2021.1, the ability to add or modify a site logo is no longer available.

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.

Tableau Server would sometimes not display the licenses on the Manage All Sites > Settings > Licenses page. TSM does show the correct product keys activated and the user seat count on Tableau Server is correct.

In the TSM user interface starting with version 2019.1.26, if a change was made to the SMTP password or the External SSL setting, not all pending changes would be discarded.

A published workbook with tabs that contains one live SAP HANA connection configured to prompt for a variable or parameter, would incorrectly prompt in a dashboard not requiring the prompt.

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.

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.

Slow performance and "deadline exceeded" errors could occur for queries or extracts using the Postgres JDBC connector in Tableau products starting with 2020.4.1.

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."

An upgrade to 2020.4+ from 2020.3.x with the Server Management Add-On and with the external file store enabled, could fail at the BackupRepositoryOperation step. The solution will be to upgrade from 2020.3.x to 2020.3.8 then upgrade to 2020.4 or higher.

With a core-based and role-based license activated together on Tableau Server, an error could display when adjusting the Site Role Limit for Creators or Viewers. The error would display for a Creator user adjustment, "Set a limit larger than the current number of Creator users".

When date fields used on a published view have been formatted for the ISO calendar and then a new selection was made on a relative date filter on this published view, the following error would display, "Uncaught TypeError: Cannot read property 'last' of undefined."

Queries could sometimes return incorrect results after tuples at the end of a table were deleted.

When a trial had started, it was not possible to use Login-base License Management (LBLM) to activate.

When running a Prep flow through the Prep Command Line Interface (CLI) that included extraneous characters in the credentials JSON file, the flow would fail with a "null" error.

In version 2020.4.1, it was not possible to open a flow containing an input step that used a wildcard union and where the original input file was missing.

Error, "Connection exception" could occur when running a flow.

When the "ACTIVATIONSERVER" was configured during installation, Tableau Prep would not display the URL in the LBLM activation window.

When a flow is published to Tableau Online with the same input connections names, the flow output would result in the wrong data.

With CMT, there was not an option to select or switch sites after entering the password during sign in.

Errors that occurred when connecting to SharePoint Lists would not display in the user interface.

The filled map with zip code polygons would not line up correctly with the background map layer for the state of New Mexico.

Exporting or printing a dashboard as a PDF could cause missing data lines on a map.

An error could display when loading a view stating, "The server could not respond due to a malformed request. In the logs, the error would state, "Tableau cannot evaluate the query that results from this calculation."

Error "TableauException: Reference to undefined field" would sometimes display in a published dashboard when there was a menu action with an invalid field in the action name.

The error "Missing password" could occur when refreshing an Odata extract.

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

With Salesforce data, a field would not load when added to a "rows to columns" pivot.

A Flow timeout error could occur when running the Flow from the command line via Crontab. The error would display, "Read timed out executing POST."

When a Flow was run from the command line interface that had multiple input files using a wild card union, the Flow could fail using 2020.4

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*).

A VizQL Server process could point to the wrong passive repository after new nodes added to build a three node HA installation.

The TSM user interface would resolve any port beginning with 25, such as 2525, to just 25.

A Prep Flow could fail on Tableau Server when the input file(s) used for a Union were removed from a shared drive.

The TSM UI was adjusted to more correctly represent the feature flag and display "Enable Desktop Licensing Reporting" under Notification and Events.

An attempt to connect to a published data source using JDBC with a Tableau Server installed on Linux would give an error with just a timestamp and session ID. The vizqlserver log would display, "Error starting Java Protocol Server, process exited. Exit code: 1. Exit status: 0. Exit code: 5."

A dashboard error would sometimes occur, "No pixel dimensions were received."

In the Resource Monitoring Tool, filter dialogues could show behind other page elements when expanded.

On IE11, some icons in the Resource Monitoring Tool would not render in the expected colors.

Some column sorts on 'Content' spaces of the Tableau Resource monitoring Tool were only applied to the current table page, rather than the full scope of data available.

When a workbook used a percentile in the custom sort of a table calculation, the workbook save would fail. The save would produce the error "Save workbook failed. Error Code: CA8336D0."

A crosstab to PDF export sometimes had duplicated row dividers.

Extracted data could show incorrect when using SQL Server table collation Japanese_90_CI_AS.

It would sometimes not be possible to create an empty extract using a calculated field with aggregate data. The error would display as follows, "Internal Error - An unexpected error occurred and the operation could not be completed. Error Code: 6EA18A9E. Unable to create extract."

Dimensions and Measures could be missing when a workbook was opened that was created with a custom SQL Salesforce data connection.

An error could occur when an attempt was made to connect to a .tds file and an Oracle schema was selected. The error would display as follows: "Internal Error - An unexpected error occurred and the operation could not be completed. Error Code: 6EA18A9E."

An error would sometimes occur when creating a PostgreSQL extract that reported, "An error occurred while communicating with the PostgreSQL data source 'influencer_v4 (ALL)'. Error Code: 1A7DD10C. ERROR: function min(json) does not exist. Error while executing the query. Unable to create extract."

In the TSM user interface, when the External SSL configuration setting was disabled or reset and "Pending changes" was selected, the error, "TypeError (2) Cannot read property 'toString' of null" would display.

The installer message that requested a reboot of the Windows OS had some translation errors in Japanese and Korean.

When a worker node was installed and the bootstrap file location contained a non-English character, the Tableau Server would not start properly and produce an "error code: 10."

Data alerts would sometimes not use the same logic as subscriptions with regards to user permissions on a data source with an embedded password.

After an upgrade to Tableau Server was completed from 2020.1.2 to 2020.2.1 or 2020.2.2, the output of a Prep Flow run on the new version would sometimes be incorrect.

The TSM command, "TSM security regenerate-internal-tokens" would not work in 2020.3.6.

A "Missing password" error could occur when a published Sharepoint List extract was refreshed.

It would not be possible to change the contact for a file asset and the error would display, "Error: Unable to change the Contact on ASSET."

When Tableau Server was started or when the configuration was changed, vizportal would fail to start within six minutes and the Tableau Server would remain degraded.

Mobile Content Provisioning - Tableau Mobile users can now have a dedicated start page set with relevant content when the app is launched.

App configuration support without an enrollment scenario was added (iOS).