Known issues

In a dashboard action, settings were not corrected saved when a worksheet name ended with a "\" character.

When opening a worksheet with multiple filters, an error would sometimes occur, "Tableau was unable to generate a query to perform this operation".

Calculations that use RAWSQL are not included in the GROUP BY clause when used as a Dimension with AWS Athena and Amazon Redshift.

Table names beginning with a number were displayed as a letter on the data source pane when connected to Google BigQuery.

The dialog, "Search for Data" would show blank after Tableau Desktop had been idle and the server session timeout had occurred.

When the Tableau Server idle timeout had expired, Tableau Desktop would not display a helpful error message to reconnect.

Error 6EA18A93 would sometimes occur when joining unioned tables.

Some workbooks created pre-Hyper would have poor performance in versions 2019.4 and 2020.1 when Context Filters were used.

In a logical join with a flat file, dragging measures from the CSV table to the view could cause a collation mismatch error.

The error, "Type doesn't match expected type" would sometimes occur when changing a quick filter using Animations.

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

The auto field improvement to remove underscores would sometimes not work.

Connecting to some Web Data Connectors from Tableau Desktop 2019.4 resulted in an error "The web data connector returned invalid data. Error Code: 95BE3012"

Workbooks using Oauth connections published with "prompt credentials" sometimes failed to publish with an "Internal Server Error TableauException" error.

Starting with 2020.3 when a Set is placed on the filter shelf, it no longer affects the displayed list of values for all other Quick filters on the sheet.

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

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.

New option to Preview data based on refresh type (Full or Incremental) to accommodate new, potentially different, write options users can specify, is non-functional in Tableau Prep 2020.2.1.

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.

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.

A text file based workbook would sometimes cause the VizQL Server to spike and not release the CPU on Linux.

Tsm pending-changes list command would sometimes not provide output in the correct language starting in 2019.4.

Changing the data source refresh from incremental to full was not being implemented by Tableau Server.

Active Directory group synchronization would sometimes fail with "com.tableausoftware.domain.ldap.LdapSearchException:javax.naming.InvalidNameException" when special characters were used in the CN attribute.

Importing a configuration topology file with no "tdsservice" or "tdsnativeservice" would fail with an unclear error.

In Web Edit, a quick filter item with an empty (0 byte text) string value in a single value drop-down list, would not display.

Excessive 4096 Vizportal DataQualityService and WebClientDatasourceAppService errors would sometimes occur in Administrative views after an upgrade of Tableau Server.

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

Starting with 2020.3.0, the ‘nlp.exe’ or the Natural Language Process would take approximately 800 MB of memory where normally up to 250 MB of memory would be allocated. The increase may contribute to system instability on a new installation. A Tableau Server restart can resolve the issue until the product is updated.

On Windows Server 2012 R2 and Tableau Server 2020.3, degraded Viz load performance can occur when the New Relic Infrastructure Agent or other third-party monitoring software that uses WMI counters are running on the same node as Hyper and the Filestore.

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.

Worksheets containing a Boolean filter from a Snowflake data source change after publishing and show incorrect data.

Sometimes, temp files generated by Tableau Bridge continued to increase over time and were not cleared out as expected.

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

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.

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

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

The edit button was missing for some WDC data sources.

Upgrading Bridge to 2020.3 would sometimes cause the client to freeze on "Loading Data sources".

The Bridge job process would sometimes be stuck when a network communication error was received getting the data source information from the Tableau Online server before updating the extract.

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

Removed the following settings for the `HyperProcess` class that were deprecated since version 0.0.10309: * `log-dir`: Use `log_dir` instead. * `:restrict_database_directory`: Not required since Hyper no longer creates database files in the working directory. * `:database_directory`: Not required since Hyper no longer creates database files in the working directory. * `:log_file_size_limit`: Use `log_file_size_limit` instead. * `:log_file_max_count`: Use `log_file_max_count` instead.

Flow performance history would not display correctly when run before 00:00 UTC when relative date filter set for "Today" and Tableau Server set to non-UTC.

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.

Nested calculation execution would sometimes have degraded performance after upgrading.

Auto field improvement with friendly names would sometimes not remove the underscore.

Connecting to Google BigQuery could take a significant amount of time.

Changes made to a table name with a Cloudera Hadoop Hive Connection would sometimes not be saved after the data source was moved to the canvas.

A SQL syntax error would sometimes occur when an initial SQL statement contained a parameter using the "TableauServerUser".

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 筑紫郡那珂川町.

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

When a workbook was opened with an OData connection, sometimes a crash would occur in 2020.2.

A SAP HANA data source would sometimes error on refresh when input parameters were used. The error displayed, "Connectionless Failure: column store error: search table error: Instantiation of calculation model failed."

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.

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

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

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

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.

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.

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

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

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

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

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.

Selecting a join node sometimes resulted in the error "System error: java.lang.RuntimeException: java.lang.IllegalStateException: MUST have a valid name for a relation"

When open for an extensive amount of time and logged in to Tableau Server, the product would sometimes become unresponsive.

Tableau Prep Builder could show the wrong schema belonging to another data source.

A "Failure parsing AQL: No such column" error could occur after joining, pivoting, and then aggregating one of the resulting measure fields.

Unable to save new and existing files in Tableau Prep 2020.3.1 when connecting to MS SQL Server.

When attempting to save a file that was created in an older version of Tableau Prep, an error occurs and the file cannot be saved.

When running a flow connecting to a SAS server via the generic ODBC connection, the following error would sometimes occur, "ERROR 22-322: Syntax error, expecting one of the following: !, !!, &, *, **, +, ',', -, /, , =, >, >=, ?, AND, AS, CONTAINS, EQ, EQT, FROM, GE, GET, GT, GTT, LE, LET, LIKE, LT, LTT, NE, NET, OR, ^=, |, ||, ~=."

Calculations could appear as a mismatched field when performing a Union of the same published data source.

Running a flow from the command line would fail when no Site was specified in the ".tfl" file.

Column order can be incorrectly changed when running an output file from the Prep command line interface.

An embedded dashboard in Internet Explorer 11 connected via SAML would sometimes fail to load with "An attempt to navigate to foreign origin".

A "script error" would sometimes occur when an embedded view using Microsoft Edge was accessed on an iPhone.

A port conflict would sometimes occur when adding the Elastic Server process to a multi-node environment.

Excessive Vizportal 4096 errors would show in the DataQualityService and WebClientDatasourceAppService.

Internet Communication Error would sometimes occur when a workbook was published via Tabcmd and the initial node of an HA installation was not available.

Workbook refresh sometimes failed when one data source was embedded and one published separately.

Stale extracts would sometimes not get reaped causing a disk space increase.

The URL generated for sharing an unsaved custom view in a non-default site would sometimes be incorrect when a non-default gateway port is used.

On some Linux platforms, the "shareProductUsageDataSettings" installation setting entered into the JSON configuration file did not import correctly.

A logic exception error would sometimes occur when any Analysis Services field formatted for wildcard matching was placed on the filters shelf.

Excessive Vizportal 4096 errors would show in the DataQualityService and WebClientDatasourceAppService.

A restore backup would sometimes fail due to a GC space limit with the error, "java.lang.OutOfMemoryError: GC overhead limit exceeded in control-filestore".

When a workbook using the playback feature was published to Tableau Server and the option to show playback controls were removed, the play button continued to display.

When the iOS Mail App is used, the Tableau Server subscription PDF attachment was not available.

Tableau Server Prep flows connected to a Presto data source would sometimes fail.

On upgrade to 2019.4, excessive 4096 errors showed on VizQl nodes which could cause larger log files.

After an upgrade to 2020.2, an error would sometimes occur when connecting to published data sources, "%1 is not a valid Win32 application".

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, "Error joining projects".

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

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.

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

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

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

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

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

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

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 a large dataset was download, sometimes not all data was available in the output file.

The VizQL Server process would sometimes hang due to out of memory errors with the Java Heap Space.

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.

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

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

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

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

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.

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

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

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.

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.

When using a dynamic parameter in a dashboard published to Tableau Online, updated data did not appear after extract refresh.

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

When attempting to authenticate using Salesforce as the SAML IDP an error would sometimes occur, "rsa-sha1 is blacklisted".

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

The recommended scheduled extract refresh job failed to support plugin connectors.

The "Edit" button was missing in the data source extract list in the user interface.

When an Internet communication problem occurred, the Bridge client sometimes failed to recover and would be in a hung status.

Launching the refresh job sometimes failed due to the long response of the machine.

Home tab was added.

Some users with ADFS/NTLM login were not able to sign-in.

Viz recommendations now available on the Home tab.