When connected to Exasol, filtering on null or blank string values would produce unexpected results.
Updated the SQL Server ODBC driver for Tableau Desktop for Mac to resolve an issue of some tables not being listed when creating an initial data source connection.
In workbooks where actions are used to navigate between sheets, story points based on multiple data sources would sometimes fail to load with a null pointer error.
Using level of detail calculations could, in some cases, generate slow-running SQL queries when connected to Teradata.
In some workbooks, hiding or deleting a sheet would result in an internal error.
Color assignments for calculated fields based on sets would change when an older workbook was opened in Tableau Desktop 10.3 or higher.
When joining two or more SAP HANA tables containing variables to a non-SAP HANA table, you could not specify variable values after joining the first SAP HANA table.
When connecting to Sybase ASE, stored procedures were not listed for users who did not have SELECT permissions on tables even though they had explicit permissions to execute stored procedures.
When connected to Snowflake, if you tried to change the aggregation of a boolean calculated field, an error would occur: Invalid identifiers BOOL_OR, BOOL_OR
In some cases, dashboard layout could be misaligned when opening older, existing workbooks in Tableau Desktop 10.1.8, 10.2.2, 10.3, or higher.
When connecting to a web data connector based data source, if you converted a string field to a whole number and then extracted the data, the number values would be incorrect.
The Dropbox and OneDrive connectors were missing if you activated Tableau Desktop using a trial.
An internal error would occur if you published a data source containing multiple connections, with the Include external files option unchecked, and at least one of the connections was file-based.
An internal error would occur when you tried to edit the alias of an empty bin segment.
When connected to Google BigQuery, an error would occur when you attempted to view the full underlying data if the view contained a level of detail calculation based on a converted date field: Abstract query is not defined
When you were connected to Microsoft Analysis Services, turning on grand totals and then selecting Keep Only on members of a dimension in a hierarchy would result in an error: The ANCESTOR function expects a member expression for the 1 argument. A tuple set expression was used.
After editing an extracted custom SQL data source, the extract would be unexpectedly regenerated twice and white space characters would be injected into the custom SQL statement.
Tableau Desktop would often become slow to respond when you duplicated a calculated field containing special characters in its name, and then used the duplicated field in a filter action.
In some cases, Tableau Desktop would crash when loading a workbook containing a date filter set to filter to latest date and a data source filter.
When you were connected to a cube data source, an internal error would occur when you tried to apply advanced table calculation settings to a view containing a filter action.
Using calculated fields involving datetime fields that had been converted to date would, in some cases, result in an error: ColumnTable: Schema/DataTable mismatch
When you edited an axis in a dual axis view, the opposite axis from the one intended would sometimes be modified.
When connecting to Oracle Eloqua on a Mac, dates would sometimes be returned as null.