Changes were applied to improve security. See ADV-2019-024, ADV-2019-025, and ADV-2019-026 in Security Bulletins for more details.
After upgrading to Tableau Desktop 2019.2, a “No such table” error occurred when using parameters in custom SQL joined with an Excel sheet.
When joining tables from MSSQL and Oracle, the error: "Collation mismatch, use COLLATE statements to resolve” could appear.
Web data connectors and other browser-based sign-in windows sometimes did not render correctly.
In a dual-axis bar chart, the background bar sometimes could not be selected.
Sometimes connecting to SAP HANA took longer than expected after upgrading to 2019.1.
When you ran a menu action to filter a target sheet, selecting a mark in a non-target sheet would clear the original action selection, resulting in the target sheet becoming blank.
In large environments where usernames contained a backslash (\) character, editing a user filter sometimes caused the filter to become invalid and resulted in a blank view.
When you were republishing a workbook or data source connected to a Hive-based database using Microsoft HDInsight authentication, an "Invalid username or password" error would occur indefinitely if you did not enter database credentials correctly when prompted during publishing.
When you used Data > Refresh all extracts with an OData extract using username/password authentication, there was no prompt for credentials, which caused a login failure.
When converting datetime to string, minute portion returned incorrect value. We were using MM instead of MI for the minute portion of our TO_CHAR function to SNOWFLAKE.