When connected to Exasol, filtering on null or blank string values would produce unexpected results.
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.
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.
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.
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.