Turning off SAML authentication for Tableau Desktop connections to Tableau Server, using the "tabadmin wgserver.authentication.desktop_nosaml false" command, did not work as expected.
New line and carriage return characters in SAP HANA data would cause errant queries to be generated, which resulted in non-functioning filters and other unexpected behavior.
In some cases involving workbooks published with multiple sheets shown as tabs, when you downloaded a workbook from Tableau Server as a PDF, some sheets would not be completely rendered in the PDF document.
When subscribing to a view in Tableau Server, and editing the subject line field using an Asian language IME, hitting the Enter/Return key would prematurely save the subscription instead of finalizing the input string.
Sending a blank 'Update Data Source Connections' REST API call did not return current data source values, which was possible in earlier versions of Tableau Server.
Some mark labels in map views would not display depending on the dimensions of your browser window.
In cases where a dimension member and an aggregation (e.g. CNTD) of the dimension have the same value, and the dimension member is aliased, tooltips in Tableau Server would display the alias name where the aggregation value was expected.
When connected to SAP HANA, data ending in an escaped character could not be filtered correctly.
In some published workbooks, hovering over a mark and clicking the link in the resulting tooltip to run an action did not actually run the action.
When using Tableau Server with trusted authentication and client IP matching enabled, a "Ticket client IP:, does not match with requester IP" error would occur in the browser after publishing a workbook and attempting to view it.
Data Server would sometimes get into an infinite error loop state, resulting in very large log files and potential server unresponsiveness.
Color legends with no title rendered with compressed width in Tableau Server.
In workbooks connected to Google Sheets and at least one other data source, any dashboard images would be lost when you refreshed the workbook extract(s) in Tableau Server.
An 'Uncaught TypeError' would sometimes occur when you loaded a view in Tableau Server.
Dashboard images with transparent backgrounds did not render correctly when published to Tableau Server.
Extra padding in IBM DB2 fixed-length string fields would get unexpectedly trimmed. This resulted in broken views when refreshing extracts of workbooks upgraded from prior versions of Tableau.
After upgrading to Tableau Server 10.0.1, it was possible for users to see sites they were not a member of in the Select a Site list after signing in. Though users could see sites they were not a member of in the list, they could not actually access the sites.
Performance recordings created in Tableau 10.0 did not include "connecting to data source" events.
Tableau Server backgrounder processes would sometimes crash when running subscription jobs.
When upgrading Tableau Server in place, if the auto backup fails for any reason, the installer will continue to run, causing content to be erased. To avoid any data loss, take a manual backup before running the installer, placing it outside of the Tableau Server folder structure. Should any error occur, restore the manual backup file.
When installing Tableau Server 10.0, and the backup of the existing server failed, the installer failed to abort and would incorrectly continue with the installation.
In some cases, viewing a workbook with very complex connection elements (very numerous connections, federated data sources, a large amount of renamed fields, or other factors that might result in a lot of workbook connection element XML) could result in a non-specific 'session ended by server' error. The vizqlserver logs revealed an error that said 'Key discarded as its current size (size) exceeds the max 2097152'.