Several changes were applied to improve security. See ADV-2017-17, ADV-2017-19, ADV-2017-20 and ADV-2017-21 in Security Bulletins for more details.
ID DO PROBLEMA
In some cases, connecting to Marketo would not return your full data set.
Connections to Excel files saved in Excel version 1707 would fail with an error: Errors occurred while loading the data source
SAML authentication from Tableau Desktop to Tableau Server would fail in some environments.
With recent updates to the Amazon Redshift driver, connections could fail with a no pg_hba.conf entry for host error. A workaround was to republish workbooks or data sources with Require SSL checked in the data connection.
When you were connected to Snowflake and cast a string dimension to an integer or float, a Numeric value is not recognized error would occur.
Query execution errors would occur when you connected to Cloudera Impala using custom SQL with a date parameter.
When you saved a workbook in presentation mode and then re-opened the workbook, the view would not be correctly centered.
In some cases, resetting the color palette in the Edit Colors dialog would not reset colors in the view.
When connected to a data source using custom SQL, if you changed the data type of a field and then created an extract or saved the workbook, extra line feed characters would be injected into the custom SQL query.
In some cases, when you joined multiple tables and performed a pivot, null values would incorrectly appear in Pivot Field Names.
Printing to PDF was noticeably slower in Tableau Desktop 10.0 and higher compared to prior versions.
In some cases, aggregated calculated fields would return no data after an extract was created.
When you connected to MySQL, case-sensitive table collation was ignored when custom SQL was used. Custom SQL connections to MySQL now default to database collation.
In some European locales, double-precision numbers were returned as #ERROR or null.