Discontinued support for connecting to Greenplum 3.3.
When connected to SAP Hana data sources, converting between date fields and a FLOAT or INT value would return incorrect values that were inconsistent with other data sources. This type of conversion now consistently returns the correct value.
Improved responsiveness and interactivity when creating views and dashboards.
When connected to Vertica databases, using non ASCII characters in group names would cause the database error "Non-ASCII characters are not supported in names".
In some specific cases, replacing a data source could cause the application to stop working.
Restoring from a backup file from earlier versions would sometimes fail with a "duplicate key value violates unique constraint" error.
When connected to Vertica databases, calculated fields that use the TRIM() function were being sent as LTRIM(RTRIM()) instead.
Adding drop lines on marks that have a null value would cause the application to stop working.
In the Amazon Redshift Connection dialog box, the Single Table list filter showed indexes in addition to the expected tables and views.
Clicking View Data in a data connection dialog box sometimes caused Tableau Desktop to stop responding.
When connected to Hive Server 2 with Cloudera ODBC 2.5 or later drivers, interacting with a dimension that contain long strings caused a ”Fetch type not supported” error.
In a worksheet using fields from multiple data source, using a division operator in a calculated field from the secondary data source caused the error “Cannot blend the secondary data source because one or more fields use the / function, which cannot be computed locally."
When working with a nested aggregate calculation, changing one of the calculation layers to a table calculation caused Tableau Desktop to stop responding.
Editing a data connection in a workbook using a blended Microsoft Analysis Services cube and extracted from a relational data sources caused Tableau Desktop to stop responding.
When connecting to a Salesforce data source, number fields with the Unique flag selected would not be available in the connection dialog box.
When connecting to a Salesforce data source, list fields were not available in the connection dialog box.
When using a workbook with table calculations and blended data, table calculations were incorrectly applied to additional aggregate measures in the view.
When adding a table calculation that uses the PREVIOUS_VALUE function to a view, a “No such column” error sometimes occurred.
When a data source was replaced with a published version of the same data source, table calculations appeared blank in the Measure Values shelf or were marked invalid.
Using date truncation for the fiscal year value caused only the second part of the year to be displayed in a view.
When exporting a dashboard image that contained Multiple Values (Dropdown) filters from Tableau Server (or Tableau Desktop), quick filter values of All or Multiple Values were blank.
When using tabs to switch between worksheets, the Quick Filters search box would stop responding.
In workbooks with labeled drop lines, dragging a dimension that contained null values off the Filters shelf caused Tableau Desktop to stop responding.
When Tableau Desktop was connected to an SAP Hana data source, a calculated field that used the SQRT function on a FLOAT measure returned a data type INT rather than FLOAT.
Closing a data connection whose fields are used in a calculation would cause Tableau Desktop to stop responding. These calculated fields now correctly become invalid when the connection is closed.
Tableau Desktop would stop responding when republishing a workbook that connected to a Tableau Server data source and another data source.
Comments on measure fields would not word wrap correctly.