Known issues

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

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.

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.

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

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

On Tableau Server version 2020.2.2 and 2020.2.3 using the Data Management Add-on with a large amount of content, performance and disk space issues would occur with the Repository.

Starting with Tableau Server 2020.1.0, performance of connections to dataserver would degrade over time.

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.

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

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

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

Some of the regions of Ghana were not recognized.

SAP BW extract refresh would sometimes fail due to a timeout limit.

Nested calculation execution time increased with some visualizations.

Using a published Spatial file and an action filter from one dashboard to another dashboard, the resulting map displayed no data when the secondary dashboard used a different primary data source.

When publishing to a Tableau Server Site with more than 3,000 projects, not all projects displayed.

Sometimes when using Explain Data, the error, "unable to poll port number of Yaxcatd" would occur.

An unknown type being read from Presto JDBC was returned as an integer instead of a string.

Selecting "Update Now" with a grouped Dimension when using Quickbooks Online resulted in the error: 6EA18A9E.

The RANK_DENSE function tooltip would sometimes show "Ausdruck" instead of the correct expression when the German language was previously set.

With "My Tableau Repository" configured on a network drive the error, "Error Code: 37CE01A3. There was a problem and the data engine could not start properly." occurred when connecting to data.

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

SAML SSO sometimes failed with the following error "ERROR 6: SSL handshake failed".

Using Tableau Desktop command line tool to refresh extracts "tableau refreshextract" sometimes resulted with "Internal error"

When an English workbook with Union Data is opened in Non-English Tableau Desktop versions 2020.1 and over, there are added Non-English translation of 'Sheet' and 'Table Name' fields added to the Union resulting in "Unknown Column Error".

Key already activated error would sometimes display during activation when the product key had expired.

"Group and Replace" sometimes resulted in the following error "System error: com.tableau.loom.doc.exceptions.LoomIOException: Problem with IO:Failure evaluating to database hyper_execute_query: 0 collation mismatch, use COLLATE statements to resolve"

When connected to Snowflake, selecting a database sometimes reset the selected warehouse.

The incorrect schema displayed when switching from "Create table" to "Add data to table" with an existing table.

Filtering 750 or more rows in a Clean step sometimes resulted in the error "System error: java.lang.StackOverflowError"

Tableau Prep did not always return the expected number of custom split columns when the number of splits needed varied greatly across rows.

Tableau Prep logs rotated based only on timestamp, not size limit.

After launching Tableau Prep on a Mac, the zoom shortcuts "command and +" or "command and -" did not respond for other applications.

Searching for RANK() or ROW_NUMBER() in the calculation editor did not provide enough information to help with writing a full calculation.

Publishing a flow created when Tableau Online was auto signed in on launch sometimes resulted in one of the following errors "All publish steps must publish to the currently connected server "tableau_online_instance" and site "site_name". Update the publish sets then re-publish the flow. Or All published data source inputs must be from the same server or site where you publish the flow. Either publish the flow to that server or site or connect to published data sources from the currently connected server "tableau_online_instance" and site "site_name"."

When connected to a published data source, invalid calculated fields did not show an error.

Performance problem resulted starting in 2019.4.2 for some flows with Union.

Flow execution error occurred, "Failure evaluating to database: "hyper_execute_query". Could not execute the given query. The result status code is 7." when multiple data sources unioned to include a live Teradata data source.

CSV output did not match the result displayed in Tableau Prep Builder.

"Direct Connection" and "Publish Data Source" options were missing when a flow was published from 2020.2.1.

Initialize-TSM sometimes failed on a new installation after an obliterate was performed on the previous installation.

Tableau Server backup creation sometimes failed with a read timeout error.

When Tabcmd export was used for both png and pdf, the exported image showed the "ALL" filter option in an unexpected language.

When web editing, the last extract time of a published data source sometimes showed the incorrect time zone.

When a worksheet is download as a crosstab or other format using the Safari browser, the file name was set to "Download Crosstab.csv" instead of the sheet name.

With "Force Password update" set on Tableau Server and a username contained a space, the password reset failed.

When the locale is Bulgaria, the date parameter did not display the selected date.

In some cases, Tableau Server was in a degraded state and Data Engine in an error state after upgrading to 2020.2, with several "No internal setting" errors present in the Hyper configuration file.

Some published views based on Google BigQuery failed to load with the message "The Google BigQuery Service was Unable to Compile the Query" after upgrading to 2020.2

Attempting to create a performance recording in Tableau Server 2020.2 resulted in an error message with a timestamp and a random string of characters, such as "2020-06-10 10:22:09:416 (XnSwDTMMx6YXaenWwS@v3wAAAko, 0:0)

The new "export crosstab" dialog will now default the selection to the active sheet. It is not required to select a sheet prior to selecting "export crosstab".

When using locked content permissions, Data Acceleration or Active Directory sync, content migration failed with a deserialization error.

When using the Content Migration Tool to migrate content produced by Tableau Prep Builder or Prep Conductor, the following error occurred "Unsupported published data source document version. Published data source document version is 10.5 and must be upgraded to at least 18.1 to be migrated."

In some cases, the query page of the Resource Monitoring Tool encountered exceptions when queries that were still being processed were sorted.

Logic has been improved for the Agent component of the Resource Monitoring Tool to limit log file size by eliminating duplicate error messages in cases where the Agent is not able to communicate with the Master.

The edit icon disappeared from Tableau Bridge after the Edit and Save Changes option was selected the first time only.

New Feature - Enterprise-wide Private Network Data Access We have modified how Tableau Online connects to private network data - whether the data resides on-premise or within a virtual private cloud. There is centralized management for Bridges that can now process multiple extract refreshes in parallel and pool them together for better resource utilization. Easily connect to AWS, Redshift, Snowflake, and other cloud data stores even within a VPC through Bridge. Manage everything on the web without logging into the Bridge client.

Added a new feature - Metrics, allowing you to track your key business data and compare values over time.

Improved sign-in screens for the mobile app.

You can now open links to your dashboards and metrics in Tableau Mobile when using Tableau Server 2020.2 and newer versions or Tableau Online.