Known issues

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

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.

When using ATR based virtual desktop licensing, activating Tableau Desktop 2019.4.3 resulted in the error "Your tableau product key was not recognized" and activating Tableau Prep Builder 2020.1.2 resulted in the error "The product is unable to activate due to an internal licensing error"

Using Custom SQL in Tableau Prep Builder, characters such as ">" are duplicated in Custom SQL when you revisit the input step.

Some users of Tableau Prep Builder 2019.3.1 - 2020.1.2 who opted out of sharing their usage data during installation may have unintentionally shared some usage data due to a defect in the Tableau Prep code. Tableau has deleted all usage data collected from Prep Builder versions 2019.3.1 - 2020.1.2. and taken steps to fully correct the issue with the release of Prep Builder 2020.1.5.

When using cleaning steps unable to change data type in input step when connecting to Box or OneDrive. Rows containing strings value remain displayed as "Null".

When attempting to output a Tableau Prep flow, a calculated column returns null values despite displaying them in the UI.

If a LOD calculation is used inside an "if" statement and then deleted, it leads to the following error "System error: com.tableau.loom.doc.exceptions.LoomIOException: Problem with IO: Failure parsing AQL: identifier."

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.

Running -tsm maintenance ziplogs sometimes failed with an error during the step "100% - Writing ziplogs archive to disk" and the resulting .zip file was missing files. For more information, see this KB.

Tableau Server would fail to connect to hyper extracts and the error "Hyper API: Could not connect to the Hyper server" would occur.

After enabling the Catalog feature or upgrading Tableau Server, existing prep flows with the lineage File > Published Data source > Flow > Second Published Data Source did not display the second data source or any associated workbooks.

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

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.

Loading an embedded view in Chrome 80 resulted in the message "An error occurred while processing the server response".

Some HyperException messages were not translated consistently across different languages.

When using HyperAPI version 0.0.10002, startup of hyperd sometimes fails and this error appears, "HyperException: Failed to start a new Hyper instance. Context: 0x86a93465".

A command prompt window displayed when running Hyper API.

When connecting to a CustomSQL table in Tableau Catalog, you would be redirected to an incorrect page.

Connections to CSV files using a separator other than comma (,) sometimes did not bring in all data.

When a reference line is scoped for "Entire table" and a dimension value is hidden, the reference line no longer shows.

When a reference line was scoped to "Entire table" and a dimension value was hidden, the reference line was no longer visible.

When using the button object to navigate between views in a published workbook that have different permissions, then the "Download" permissions are not transferred accordingly between those views.

Fill color below Reference line looks abnormal in published view and has changed from 2018.2 to 2018.3. View also displays differently on Tableau Desktop than in Tableau Server.

Views with tooltips disabled intermittently display tooltips in the top left corner of the view after upgrading to 2019.2.4.

When attempting to login to Tableau Online through Tableau Desktop using SAML, the login prompt redirects to a blank page, and does not allow the user to sign into Tableau Online, or select their site.

Label text horizontal alignment not displayed correctly, when different lines use different fonts.

Maps of Norway still showed 18 Norwegian counties rather than the current 11.

Tableau Desktop 2019.1 crashes every time after activation, if Virtual Desktop Support is enabled. It works well after being re-launched.

When loading a Geojson (Spatial connector), "unable to create unit vector from zero-length vector" error is returned.

Query using TIMESTAMP being sent from Tableau Desktop to DB2 has poor performance with large dataset.

When connected from Tableau Desktop 2019.2.7 to DB2 v11.1 data source, and changing a Discrete date field to a Continuous date, the field becomes invalid.

In Tableau 2019.2.6, when a group name contains non-alphanumeric characters, for example "+", the URL encoding of "+", which is "%2B", cannot be recognized in the ISMEMBEROF() function. "%2B" is working fine in version 2019.2.5 and older.

In Rest Api Schema, Public schemas missing attributes for viewType and siteType.

On MAC OS this error received: "Unable to connect to this Tableau Server data source. DataServiceFailure: There was an error with the data source ""."

OneDrive authentication intermittently fails with HTTP 400 Error: This site cannot be reached.

When connecting to Tableau Server on Linux from Tableau Desktop running on a Mac, the following error appears: "Cannot connect to Tableau Server. Please select the server name and port and try again. Internet communication error: SSL connect error".

When adding a data source to an existing workbook in Tableau Desktop 2019.3, "Connect" menu is cut off and selecting Tableau Server to publish data source is not possible.

When connecting to Excel and Google BigQuery in a same connection, then using the ROUND function, the following error occurs, "ROUND is being called with (float, integer), did you mean (float)?"

When connecting to Excel and Google BigQuery in a same connection, using a ROUND function will result in the following error: "ROUND is being called with (float, integer), did you mean (float)?"

When trying to create a set, it gives an option to skip "Retrieving filter list", if followed this action is generating the following error: "Internal error - An unexpected error occurred and the operation could not be completed."

When there are fields with the same names in an existing data source, then adding another data source to canvas and selecting "Create Join Calculation", will result in the following error, "Internal Error - An unexpected error occurred and the operation could not be completed."

Joining an extract and Excel file sometimes resulted in the error "extract 0 collation mismatch, use COLLATE statements to resolve" when using Japanese OS locale.

Shapes in maps have changed since upgrading from version Tableau 10.3 to 2019.2 in both desktop and server.

NULLS remained at the top of the viz when using a nested sort, whether ascending or descending sort was selected.

Error Code 8B31AE48 sometimes occurred when attempting to enable Show Empty Columns.

Tableau Desktop Data Interpreter does not work on CSV files with file length of 26 Character or more.

Workbooks using a cross joined data source sometimes failed to load with the error "Semantic Error - JOIN requires equality comparison between table columns".

From Tableau Desktop, when selecting Tableau Server on the data source page to connect to a published data source, one or more published data sources were missing and/or could not be used.

Switzerland postal codes 01011, 03010, 03801, 04031, 04101, 0504, 06039 and several postcodes starting with 09 were not recognized by Tableau Desktop.

Menaka and Taoudenit regions were missing from maps of Mali.

The error "There is no active connection to the data source" occurred intermittently when refreshing data sources using JDBC.

Logarithmic axis with an automatic minimum and fixed maximum sometimes displayed marks in an unexpected position.

Parameter Action did not trigger when clicking dimension value that has NULL measure value.

Attempting to connect to QuickBooks Online would fail and users would be redirected to a QuickBooks Online Blog post.

Actian Vector connector did not support creating temp tables.

The Linkedin Sales Navigator connector failed to connect when Tableau Desktop was set to English (UK), Italian, or Traditional Chinese.

"Export to Excel" did not preserver number formatting when a percentage format was used.

District boundaries for Hong Kong did not render as expected.

Opening the Box connector showed the following prompt: "Do you want the application "java" to accept incoming network connections?"

When connecting to TabPy or RServe with "require SSL" selected, Tableau Prep Builder closed unexpectedly with the error "Something went wrong and the application needs to restart".

Cloudera Hadoop sign in was disabled when only Cloudera Impala drivers were installed.

Adding a pivot step sometimes resulted in a "Failure parsing AQL" error.

Flows with a large number of changes in a single clean step sometimes failed to complete.

Changing the color of an aggregate step had no effect.

Clicking a "clean" step after clicking another step sometimes resulted in the error "System error: System error".

Tableau Prep Builder sometimes exported a 1 for an if-else calculation when a 0 was expected.

While trying to run a .tfl flow as input node, the following error "System Error: Unable to run input node: Failure evaluating database: [66] hyper_execute_query:0 "db1003"."TableauTemp"."Sheet1$" does not exist." occurs. When running the same flow as .tflx, it works fine.

After upgrading to Tableau Prep 2019.4.2 flows stopped working correctly and performance regression was observed, but no error messages appeared, just spins running infinitely without actually processing the data. Downgrading to 2019.4.1 made flows work again.

When adding several sheets to a Union in Tableau Prep, interacting with flow steps stalls and takes several minutes to load. Additionally, the flow ran in 1 second on 2019.4.1 but does not complete after one hour in both 2019.4.2 and 2020.1.1.

Publishing a flow containing an initial SQL parameter from Prep Builder 2020.1.3 to Tableau Server 2020.1 resulted in an error "The flow can't be scheduled or run because Tableau Server is running an older version than your copy of Tableau Prep Builder and doesn't support some of the features in this flow".

When attempted to connect to MS SQL Server using Tableau Prep Builder 2019.4.2, unable to get prompt for username and password when using Windows authentication.

Error appears: "Unable to run input node: Failure evaluating to database......collation mismatch, use COLLATE statements to resolve", when executing a given query.

Pivot [Rows to Columns] Does NOT Return All Columns. The sample field has 350 distinct values, but Pivot [Rows to Columns] returns only 320 columns.

Tableau Prep fails to automatically trim trailing whitespace in the Table/Schema Search, whereas Desktop always trims whitespaces.

Tableau Prep Flow Output data changes to incorrect values if flow contains Right Outer Join and "IFNULL" calculation.

Unable to change data type in Input step when connecting to PDF.

Tableau Prep hangs on splash screen and will not launch due to Prepservice component not starting properly.

Running a flow, created in an older version, does not complete after upgrading to Tableau Prep Builder 2019.4.2. No issues running the same flow in 2019.3 and 2019.4.1.

Flow execution error when using Windows Excel: "Error in outputting: Failure evaluating to database tableau temp does not exist when using a UNC path in the input connection."

Flow built on pivoted left joined on itself data set does not output the expected number of rows.

Union of wildcard does not work in Prep Builder 2019.4.2, the flow fails with the following error: "Unable to run input node: Failure evaluating to database: [db number] hyper_execute_query: 0 "db number"".

Tableau Prep is converting date values improperly, showing 1000-01-01 as 12/31/0999.

When trying to open flows containing LOD calculations in Prep Builder 2020.1.2, no error is encountered, but if the same flow is opened in Prep Builder 2020.1.3, the following error occurs: "This flow was created in a newer version of Tableau Prep Builder and includes functionality that isn't supported in this version. To open the flow, either upgrade to the latest version or open the flow in Tableau Prep Builder 2020.1.1 and disable the following functionality: Level of Detail Calculations".

Incorrect data from unrelated fields appear in "Join Clauses" panel, after editing a join condition.

Only the first change that you apply from the "Expression" editor will actually be applied. If you use "Apply" to change a calculation, no subsequent uses of "Apply" will work, and "Save" will not work either. Closing and re-opening the editor will allow you to make one other change, however.

The generic error "System error : System error" occurs in Tableau Prep 2020.1 after creating a union of text files, if the field [timestamp] in the input step is not changed from "Date time" to "Text" type.

Signing into Tableau Server and loading embedded views sometimes failed on Safari 12 after upgrading Tableau Server to 2019.4.2, 2019.3.4, 2019.2.8, 2019.1.12, 2019.3.14, 2018.2.17, 2018.1.20, 10.5.23, or 10.4.24.

Error "[Internet communication error: Couldn't connect to server]" when publishing a workbook via tabcmd or REST API. Publishing from Tableau Desktop works.

Live wildcard union of CSV files will not show or refresh on Tableau Server when refreshed using the button or the refresh=y parameter.

Users on Tableau Server with SiteSAML were sometimes unable to login after a database failover

Refreshing a published extract from Tableau Desktop sometimes results in the error "Unable to parse XML response from website".

Axis titles were sometimes duplicated on published dashboards.

The column headers' image tiles in a dashboard are incorrectly rendered, when columns overflow their borders and cause overlap.

After Server OS reboot, Tableau Server is unlicensed until an lmreread is performed.

Refreshes for extracts based on multiple databases intermittently failed with the error "Internal Error - an unexpected error occurred and the operation could not be completed".

Error occurs, "Object does not support property or method 'closest'", when dragging and dropping excel file to data source pane in web edit mode using IE11 browser.

When failing a sign-in (bad password) from Tableau Server to an Oracle data source, the failed sign-in counts towards the total tries for that user on the Oracle side, and at the same time seems to be incrementing the number of VizQL processes in the Tableau Server environment. This issue results in users getting locked out of the database after fewer tries than expected.

Unable to view Ziplogs in TSM Web UI after using 'startdate' and 'enddate' in Tableau Server 2019.3 and 2019.4.

In Tableau Sever 2019.4.3 using mutual SSL, logging into the server via the browser failed with a blank page after selecting the certificate, while loggin in from Tableau Desktop failed with error code 9F4C5638.

When installing Tableau Server 2019.4 into a root drive without a folder path defined (for example: C:\ or D:\), the installation will continue but eventually fail providing error, "The server may not have started properly. Part of the installer existed with error code: 1. Check the logs: D:\\logs\app-install.log for more information."

When changing the value of idpEmailAttribute using the TSM authentication SAML map-assertions command, it changes the idpDisplayNameAttribute value instead.

When upgrading Tableau Server on Windows from 2018.1.x and earlier versions (all pre-TSM) to 2019.4 through a non-default location, the installer does not present the 'Upgrade Tableau Server...' option, as it does not recognize the non-default install location, but instead does a clean install.

Wrong icons used for "Workbook" site role list in "Site Roles and their maximum capabilities".

When upgrading or restoring a backup from earlier versions of Tableau Server to version 2019.3 or later, Tableau Server sometimes failed to restore database content. The error "-U, tblwgadmin, -h, localhost, -p, 8060, -F, , -A, -q, --pset=footer]' timed out after 5 MINUTES" appeared in the databasemaintenance.log.

Subscription error occurring for users when subscribing to a custom view.

Spurious failover during cluster shutdown could directly lead to maintenance issues

After changing a site URL, the following error occured when using Tableau Desktop to open a workbook that connected to a data source published before the site URL change was made: "Item Not Found (Error Code 12)"

When using Run Now to run an extract, the job creator ID displayed was for the user who created the extract task, not the user who ran the task.

Refreshes scheduled via Tableau Desktop had a creator ID of 0, rather than the ID of the user who scheduled the refresh.

Subscriptions created between 10/23 and 11/05 may not run on Tableau Online and instead the error "NullPointerException" is received.

In published views, the tooltip sometimes showed a different value than the mark.

Running a published flow that used Cloudera Hive with Kerberos failed with the error "Bad format in credentials cache".

You noticed database disk space and elevated CPU/latency spikes in Tableau Server.

The error"An error occurred. [...] Uncaught SecurityError: Blocked a frame with origin "" from accessing a cross-origin frame."would occur when interacting with an embedded view and attempting to save a custom view.

Centered mark labels sometimes displayed as off-center when using client side rendering.

Right-click context menu on parameter search box sometimes failed to appear.

Published workbooks with blended data sometimes showed some unexpected values.

Custom sign-in logos looked different on the sign-in page and site selection page.

CSV files with uppercase extensions stored in a Windows shared directory were not found by Tableau Server on Linux using wildcard union.

Creating or opening a workbook based on a Google BigQuery data source sometimes resulted in the error "IllegalArgumentException contentIds must be non-null and non-empty"

When subscribing to PDFs of an entire workbook that included custom views, all views defaulted to original.

"Download Workbook" events sometimes displayed in admin views when users had not downloaded workbooks.

Changing the height or width of a dashboard button caused the button image to offset.

"Download Workbook" events sometimes displayed in admin views when users had not downloaded workbooks.

Image icons for Lineage were sometimes missing when using published data sources.

Dual axis visualizations sometimes rendered incorrectly when using client-side rendering.

Opening a published workbook that used a cross-database join sometimes resulted in the error "Hyper API: Could not connect to the Hyper server. error opening database …"

It was not possible to add Snowflake saved credentials in Tableau Server on Linux 2020.1.

When connecting to Salesforce the error "Connectionless Failure (status code = 10000)" sometimes occurred if the user did not have View Setup and Configuration permissions in Salesforce.

When configuring the Tableau Resource Monitoring Tool on Tableau Server, the error "Web Service Restarting" would occur and the page loads indefinitely.

When Tableau Bridge client is not running, sometimes no email notifications are sent to the data source owner that the next scheduled refresh is going to fail.

Improved error messaging when Tableau Online is down or the client was logged out by site admin during data refresh.

Tableau Mobile's Recent list now displays only views and metrics, the same as on Tableau Server.