Known Issues

Connecting to Tableau Server from Tableau Prep failed with a "Cannot connect to Tableau Server" error if a proxy exceptions list contained 1024 or more characters.

View containing Rank_Unique appeared different in Tableau Public than in Tableau Desktop.

Singapore postal code 388402 was not recognized.

An LOD calculation that references another calculation containing a constant would sometimes have a different result after a data source was published.

A "DataServiceFailure" error or "insufficient privileges to operate on schema" sometimes occurred when trying to refresh or open a workbook with a published Snowflake connection.

Refreshing a data source and viewing the visualization as the same user would sometimes lead to a data mismatch between the visualization and a parameter.

The function editor tooltip for RANK_DENSE would show "Ausdruck" instead of the expression if the language was previously set to German.

OData extract refreshes would fail after the update to version 2020.2 if the Odata server name contained a blank space.

A Manual sort would not work correctly after Auto Updates was paused.

Syntax errors occur when refreshing data using custom SQL where newlines are removed from the query.

Dynamic Parameters using aliases would sometimes display the warning message, "The 'calculation' value is not in this parameter's list of values" despite meeting the necessary criteria.

When a workbook uses a published data source along with other secondary data sources, and two parameters from different data sources have the same internal names, Tableau would sometimes return incorrect cached results

The Pages shelf date counters would sometimes not advance with animations enabled.

In some cases, Tableau would fail to create an extract when you extracted a data source with cross-database joins containing a spatial file.

Joining two data sources, performing a pivot, and then aggregating one of the resulting measure fields would sometimes result in an error, "Failure parsing: No such column [{name}]."

Error occurred when trying to open a workbook with a published Snowflake connection, "insufficient privileges to operate on schema".

Saving flow output sometimes failed unexpectedly due to an internal issue with field ordering.

Generating a random sample of Snowflake data failed with the error "System error: Unable to run input node"

Connecting to Oracle from Tableau Prep sometimes resulted in an "oci.dll not found" error.

Flows based on Athena data sometimes output incorrect dates when run via the Command Line Interface.

After a published data source was overwritten by Tableau Prep Builder, field names were sometimes garbled on the Lineage tab.

When changing column order at Clean step in Prep interface, the order is retained in output file, but, when executing the same flow file from Command Line interface, the column order is not retained and revert back to original order in the data source.

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

Tableau Prep Builder failed incremental refresh when the published extract is encrypted.

Using the Data Management Add-on with a large amount of content, performance and disk space issues could occur with the Repository.

Unexpected Server Error would sometimes occur when loading a dashboard with a date filter.

LBLM License Usage Dashboard would sometimes display the error, "Uncaught TypeError: Cannot read property 'domNode' of undefined".

When the TSM UI licensing page was refreshed, product keys would not display or an error would sometimes occur, "Server Error:
The server encountered an unexpected error processing the request. Look at the server logs for more information."

Sometimes when migrating data an error would occur in the Content Migration Tool, "Invalid data source file, Illegal characters in path".

In the Content Migration Tool an error would sometimes occur, "Failed to download workbook. Error downloading workbook [Workbook Name], The underlying connection was closed"

In the Content Migration Tool an error would sometimes occur, "Error joining projects".

With server-side rendering, a Show/Hide button containing a sheet would initially display blank.

Content Migration Tool would sometimes fail when migrating a full Site with an out-of-memory condition.

When migrating a workbook in the Migration Content Tool, and error would sometimes occur, "Error generating view metadata. Could not find thumbnail for workbook".

An email that contained a subscription PDF file sometimes displayed the original view instead of the subscribed custom view.

When attempting to download full data from a workbook, an error would sometimes occur, "Tableau Server encountered an error while working with this worksheet."

An intermittent error would occur when opening a view, "TableauException: ColumnTable: Schema/DataTable mismatch".

When loading a published view on Tableau Server an error would sometimes occur, "Unexpected token in JSON at position xxx".

When publishing extract files via the REST API including tabcmd, or other third-party tools, a data source would sometimes be created without field metadata. Ask Data would not display fields in the fields panel, except for "Number of Records"

When attempting to open a workbook the following error would sometimes occur,
"TableauException: TFilesystem::LastWriteTime() -- Cannot get modification time of non-existent path".

If any rule allowed a user project leader permission on an unlocked parent project, they could not be denied permissions on an unlocked sub-project.

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

The "rmtadmin" command line tool failed to execute and logged an exception when not run from an elevated permission command prompt.

The axes on the Resource Monitoring Tool 'Insights' chart was not aligned for average and maximum values.

During Agent registration in the Resource Monitoring Tool, the final 'Register Agent' button was enabled before the page redirect occurred.

The Resource Monitoring Tool failed the initial setup when a fully qualified domain name was provided in the host field. The default security certificate now accepts fully qualified domain names for the host.

In the Resource Monitoring Tool, the 'Site' filter on the 'Insights' page did not properly filter the extract refresh list.

The Chargeback report of the Resource Monitoring Tool would not populate with data when multiple environments were configured and one of the Tableau Server environments had no data.

In some scenarios, the Resource Monitoring Tool showed null values in the 'Last Executed' field for data queries.

The Resource Monitoring Tool listened over port 9001 by default rather than port 80 after initial setup was complete.

During the initial setup, the wording for the 'Host' field requirements of the Resource Monitoring Tool has been updated to reflect that this field should rarely be changed.

Resource Monitoring Tool upgrades will now apply a configuration change that will allow Postgres connections on FIPS-enabled servers.

In some cases, the Resource Monitoring Tool would allow a new environment to be created that had the same name of an environment pending deletion.

The Export and Toggle buttons on Stories with embedded dashboards and device specific layouts were unresponsive when using a mobile browser.

When attempting to change the value of a dynamic parameter list in Tableau Online, the value did not update.

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 using a dynamic parameter in a dashboard published to Tableau Online, updated data did not appear after extract refresh.

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

The error "Communication with the Tableau Protocol Server process was lost" occurred when refreshing an extract, refreshing a Prep flow or when a subscription failed.

OAuth data sources published to Tableau Online such as Salesforce and Google Analytics would fail to refresh due to being routed to the Bridge client instead of running server-side.

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

In some cases, it was not possible to refresh subscription keys before the expiration date occurred.

An LOD calculation that references another calculation containing a constant would sometimes have a different result after a data source was published.

Sometimes an error would occur when a federated connection of two text files in the same directory were extracted or refreshed.
Error Code: 3834CEBA
Could not execute the given query. The result status code is 7. a database with alias name 'db#' is not attached

When using a fixed precision decimal column, creating an equality comparison calculation using a parameter resulted in incorrect results.

Schema name list was not in order when connected to Amazon Redshift.

User calculations and parameters with fixed precision numbers would sometimes not return the correct results from the database.

The create extract and preview join data window would sometimes be unresponsive with the 'loading' status when a spatial file was joined with a CSV file.

When the Teradata driver was loading, a possible crash was experienced due to a race condition with the driver.

View filters disappeared after renaming a field in a database and replace references was performed.

When a join with Salesforce tables was created using one of the tables twice, fields hidden in the first instance of the table were also hidden in the second table after creating an extract.

The date and time of 1899/12/30 12:00:00 AM was not handled correctly as a fixed start of the axis range.

Tableau Desktop 2019.4.0 does not recognize the following 3 Japanese cities: 1. 丹波篠山市 (Tamba-Sasayama, Hyōgo)- city changed its name from 篠山市 to 丹波篠山市 in May 2019. 2. 標津町 (Shibetsu-chō, Hokkaido) 3. 那珂川市 (Nakagawa, Fukuoka)- city founded on October 2018, from 筑紫郡那珂川町.

The following error would sometimes occur when importing custom geocoding: "Unable to complete action. Internal Error - an unexpected error occurred and the operation could not be completed. Error code: 6EA18A9E"

It would sometimes not be possible to publish or create an extract when making a Relationship on a pivoted value. Error: "Unable to complete action. An error occurred when publishing the workbook. Error Code: 6EA18A9E Internal Error - An unexpected error occurred and the operation could not be completed."

When connecting to Tableau Online or Tableau Server, "Error Code: 9F4C5638
Internet communication error: SSL connect error" would occur using Tableau Desktop 2020.2.2.

The use of Double Precision with a SharePoint List caused a "Malformed SQL Statement" error.

Map services on Linux would not respect the network forward proxy settings which caused map rendering to not complete.

The 'Traffic to Views' would sometimes not load or have slow load times when on a specific Site Admin View.

Performance of connections to Data Server would degrade over time.

Command "tabcmd publish --thumbnail-group" produced unexpected RuntimeException.

Some extract refresh jobs for Google BigQuery failed due to a timeout error or took an excessive amount of time to complete.

A filter based on a dynamic parameter populated from a secondary data source would display a blank filter in a published view.

Table lost column sort order after publishing to Tableau Server on Linux.

Face ID and Iris scan did not work for App lock on Android.

Custom start date can be set to the metric Adjust and Compare option screen.

Split screen mode would crash on Android.

Welcome screen added for first time users to highlight the capabilities of Tableau Mobile.

Screen rotation would sometimes crash on Android.