Known Issues

Extracts created via the Anaplan connector were sometimes missing rows of data.

When running certain kinds of queries against data stored in Google BigQuery, you can connect to tables and run queries that return small amounts of data, but if you try to return a larger amount of data or create an extract you will encounter this message, "An error occurred while communicating with the Google BigQuery data source (table name)".

When adjusting the major axis tick marks to show the last day of the month, you get the last day of the first month in the view. This is not a problem if you start with January, but if you start with other months, it is showing wrong tick mark intervals for months.

When using a filter, sorting on a MSAS dimension resulted in an "Internal error - An unexpected error occurred and the operation could not be completed" message.

When you tried to modify or remove an existing SQL Server input from a complex flow, Tableau Prep became unresponsive.

When using a relative date filter with no explicit anchor against a live Presto connection in 10.4.5, all the data disappears.

Tableau Desktop publishing window cuts off the external files option and/or pushes down the rest of the publishing dialog when zoomed to 125%.

Upgrading Tableau Server to version 2018.2.1 fails at 10-14%, if service.backup.pgonly is set to "true".

When publishing a workbook connecting to multiple Google Sheets, the Google Sheets’ authentication screen repeats itself multiple times before the workbook publishes and appearing as if each Google Sheet needs to authenticate individually.

When refreshing an extracts with joins using Teradata/Vertica, the following error occurs, "Keychain authentication does not work because either the required TDC file is missing from Tableau Desktop or the TDC file differs from the TDC file on Tableau Server."

Upon opening views on Tableau Online, users might intermittently encounter an Unknown Server Error stating “TableauException: Cannot find a total needed to compute a percentage. The database may have changed or a calculation cannot be completed. Try refreshing your connection or editing the calculation.”

An "Uncaught Invariant Violation: Minified React error #40" error occurred intermittently while loading certain workbooks in Tableau Online.

After upgrading Tableau Server from 10.4 to 10.5.3, PDF downloads started taking 2 times as long on certain workbooks.

When two fields are placed on the Labels shelf and their order is then switched in the Label edit dialog so that a space is added between them, the last character of the field entered first disappears. This happens when the label ends in white-space, is vertical text, or has wrapping turned off.

Continuous Bin shows incorrect Axis values, when set to 'Independent axis ranges for each row or column'.

After saving and re-opening a workbook utilizing a filter and live connection to Firebird, the following error occurs: "Errors for 'Sheet 1': Field which is included for filtering does not exist." 

When opening a workbook in Tableau Desktop 2018.2 that was created in Tableau Desktop 10.5 or earlier, "The workbook will be upgraded" message did not display.

Published workbooks with copied dashboards are encountering an unexpected error "Unable to get property '(property value)' of undefined" on Tableau Server, when Filter is changed. The '(property value)' encountered varies between 'zoneType', 'zoneCommon', 'dataColumns', or 'columnIndices'.

When using the NOW() function with a live connection to Snowflake, Tableau followed the data source location time instead of the time configured on the data source server.

When trying to create an extract of Sybase ASE using a MAX() or Top N extract filter, the extract would fail.

Sometimes, nested level of detail calculations in a workbook produced an "Error occurred communicating with the data source. No such column [Calculation_]." error message.

Updated German county data.

Updated German postcode data.

Updated Australian postcode data.

After you refreshed an extract, saving the workbook would silently fail to retain the extract location if the extract was also open in another instance of Tableau Desktop, resulting in an "Extract not found" error upon reopening the workbook. There is now a warning for the failure and you are prompted to specify an alternate location to save the new extract data.

Many Thai vowel characters were not rendered correctly in Tableau Desktop.

Updated Turkish postcode data.

Updated province data for the Democratic Republic of the Congo.

Using a calculated field containing a spatial geometry field and an failed conditional statement could result in an error: "unable to deduce expression type, use 'NULL::' to specify the type"

When you added description text to a story point, and then deselected the text object, you could not format the description again.

When doing a wildcard search on a pivoted field based on a .csv data source, a "collation mismatch" error sometimes occurred.

When you connected to an Odata feed from a non-default namespace, an "Odata: Cannot find corresponding ComplexType" error occurred.

When using Tableau Desktop with Microsoft Office IME 2010 Japanese, re-entering Japanese words do not convert them properly in the field name search. It looks like incremental auto-search is interrupting the IME character conversion and resulting in unintended characters appearing in search string.

int64 field in OData sometimes rounded incorrectly.

When using a cluster in a workbook, extract refreshes sometimes failed with the error "Unable to complete action Internal Error - An unexpected error occurred and the operation could not be completed."

Creating an extract in a remote shared folder using Tableau Desktop 2018.2 on a Mac failed with an "fcntl(): Operation not supported" error.

Selecting Total Using > Server with an ASO cube resulted in a “value 'Server' not in enumeration” error.

When you used a filter on a data source with a non-January fiscal year start, sometimes an "Unable to complete action Internal Error - An unexpected error occurred and the operation could not be completed" error occurred.

Maps using custom polygons were blank, distorted, or rendered as a single color box.

Some Japanese prefectures (三重 Mie, 京都 Kyoto, 和歌山 Wakayama, 埼玉 Saitama, 大分 Oita, 奈良 Nara, 富山 Toyama, 山口 Yamaguchi, 山梨 Yamanashi, 岐阜 Gifu, 岩手 Iwate, 新潟 Niigata, 熊本 Kumamoto, 神奈川 Kanagawa, 福井 Fukui, 秋田 Akita, 茨城 Ibaraki, 青森 Aomori, 香川 Kagawa, 高知 Kochi, 佐賀 Saga) were not recognized as geographic roles without the the suffix appended ( like "県” or "府”)

When you changed a "Multiple Values (dropdown)" filter to select no values, then a single value, an "Unable to Complete Action: Table Arrays Must be of the Same Size" error occurred.

When adding a data source filter to an extract with multiple tables storage, the following error will occur: "Unable to create extract." This error message is incorrect and should be disregarded; the extract can now be created correctly.

In Tableau 2018.3, sometimes maps using custom polygons appeared distorted, inverted, or rendered as a single color box.

The sign-in dialog for creating connections on a dashboard is garbled/overlapped when viewing in IE 11.

Workbooks with heatmaps become unable to be opened after switching a density mark color to a non-default color palette, then switching off density mark type.

With a table calc an reference line in the view, nested sorting failed with a "No such column" error.

Selecting a mark to highlight and changing filter selections sometimes resulted in the wrong measures being highlighted.

When port number is not specified in the tfl flow file, command line refresh is not able to match the connection. Error will read: “could not find match for [server name]”

Sometimes, Tableau Prep output preview data was different from the actual output data.

Using a "keep only" filter resulted in fewer rows in the output than seen in the preview pane.

Inserting variables into the calculation editor improperly wipes out or replaces multiple lines of calculation text up through the subsequent variables in the calculation.

When creating a union that has at least two mismatched fields you cannot drag and drop last fields and an error appears "Something went wrong and the application needs to restart."

Publishing a flow from the Command Prompt rather than from the Tableau Prep interface produces an error, “You don't have credentials for Tableau Server to publish extract for one or more output nodes in tfl/tflx file”, though publishing from the Tableau Prep interface using the same credentials works fine. 

Tableau Prep sometimes failed to launch with an "Uncaught Exception: Error: ENOENT: no such file or directory, mkdir" error when the repository was located in a shared drive.

If the pivot action is selected in the super-node, the pivoted fields cannot be renamed. Other fields seem fine.

Data contained in Output is different from data contained when previewing Final Step, specifically, Output has some null values for fields that previewing Final Step does not.

After joining a .csv file with a MySQL table, the following error occurred, when publishing the .hyper file to Tableau Online/Tableau Server:
"Collation mismatch, use COLLATE statements to resolve."

When you double-clicked a .tfl or .tflx, Tableau Prep opened, but the actual flow did not open.

Tableau Prep output files (All formats: CSV, TDE, HYPER) show different data than inside the Tableau Prep Data Profile UI.

When you tried to view data for a worksheet that had a percent (%) symbol in the name, an "java.lang.IllegalArgumentException: URLDecoder: Illegal hex characters in escape (%) pattern" error occurred.

Hyper crashes due to invalid expression extraction.

When using Mutual SSL, fallback to password authentication does not work in these scenarios: 1. When signing in to Tableau Server from Tableau Desktop without the client certificate installed on the client machine. 2. When sharing views using the "embed=yes" URL parameter with the Guest Account disabled in Tableau Server.

When using a Chinese, Japanese, or Korean locale in Tableau Server on Linux, after you changed a date and time parameter value, the parameter reverted back to the previous value.

The time part in the datetime type is not displayed properly, when user locale is set to Japanese or Korean on Linux server (Tableau Server on Linux).

Tooltip fails to disappear in workbooks published to Tableau Server, when the workbook is published with the "Show sheets as tabs" option checked.

Upgrading from Tableau Server 2018.1 and earlier versions to 2018.2 and newer versions failed with an "InstallerException: Unable to login" error when the TSM admin password contained an exclamation point (!).

When creating a backup on Tableau Server 2018.2.1, extracts are being deleted if a junction is used instead of a sym link.

Tableau Server coordination worker shows as 'Down' in systeminfo.xml after a clean install.

Sometimes, installing Tableau Server 2018.2 failed with an "Initialization terminated at step 5 of 40: An error occurred while waiting for services to reconfigure." message.

After upgrading to or installing Tableau Server 2018.2, sometimes logs grew quickly and filled available disk space.

DomainMapperForGroups fails to give AD domain access to group on site import.

MSAS datasources published with "Prompt User" credentials continually prompted for credentials when accessed from an non-Administrator account.

Filters with no shading had a grey background after publishing.

Changing the default layout from list to thumbnail or vice versa did not save when using "Make This my Start Page".

Custom geocoding was not always applied when published from a computer using a Japanese language operating system.

When running a backup, the following error sometimes occurred, "Did not parse exactly one backup result, got 0."

In Tableau Server on Linux environments, Microsoft Azure SQL based published data sources failed to connect to the database when you published them with prompt user authentication.

Workbook size was inconsistently reported between the Stats for Space Usage administrator view and the Workbooks content view.

When you called the REST API method "Query Datasources", the field "createdAt" showed the same value as "updatedAt".

When using Rest API 3.0 code to access user information, only old Site Role names were returned.

In some multi-node Tableau Server clusters, it was not possible to generate log snapshots via the UI.

Amazon Athena data sources published with "Prompt User" were inaccessible and a "Missing credentials error: Either UID/PWD or AwsCredentialsProviderClass must be provided." error occurred when you tried to access them.

When attempting to load a workbook, the following error would appear: "Unexpected Error: An unexpected error occurred. If you continue to receive this error please contact your Tableau Server Administrator. Session ID: ###### Maximum call stack size exceeded."

Dashboards with "automatic" layout size, nested layout containers and subtotals displayed as blank in maximized browser windows.

Custom fonts with a condensed font style were not correctly displayed when using server-side rendering in Tableau Server on Linux.

Date filters with "only relevant values" selected did not respond when viewing in Safari on iOS.

After entering credentials for a data source, the warning symbol (!) remained, preventing extract refresh.

When using a parameter in a join with Custom SQL, sometimes a "Tableau Data Engine Error: 10000: Path does not exist" error occurred during refresh.

When an error dialog displayed, the grey background was sometimes larger than the size of the underlying window.

This is a test release note with no real significance please pay no attention to this text.