The error Tableau Exception: Could not send Query (connection dead) would sometimes display when accessing a published workbook that connects to an Amazon Redshift data source.
Favorites could not be set or deleted in Internet Explorer 7, 8, or 9 when Security Support Provider Interface (SSPI) was enabled.
When scrolling a view while editing a workbook on an iPad, marks would scroll correctly but row and column labels would not.
On servers configured to use Active Directory authentication, custom views that were added as a Favorite would not load when the link in the Favorites menu was selected. The link generated a URL with a custom name that was not being handled properly.
When editing views on Tableau Server with an Essbase OLAP Cube connection, dimensions were not being displayed in the Data window.
Drop-down lists with multiple values would not open upward when the list of values extended below the bottom of the browser window.
In a distributed server environment, some VizQL processes would appear to be underutilized and others appeared overutilized causing Out of memory errors.
Workbooks that contained complex dashboards would cause a memory leak when opened in Internet Explorer 8 or 9.
When a background job was scheduled to run during a time that no longer exists due to a daylight savings time change, all background tasks would stop working.
A Commit called on nested editor error would sometimes appear when changing tabs in Tableau Server.
Assigning the Publish right to a user would successfully complete and then trigger the web browser error, Unable to get property 'text' of undefined or null reference.
For views published to Tableau Server, annotations placed over marks that trigger actions would cause those action to no longer be triggered.
In some cases, activating a license for Tableau Server 8.0 on a Virtual Machine (VM) could fail with the error, No license found for Tableau Server.
When importing Active Directory users from a *.CSV file, the email value was set to username instead of the actual email from Active Directory.
Performance was optimized to decrease the amount of time it takes to open the Users list as an administrator.
Text in workbooks was sometimes compressed to the point of unreadability when client-side rendering was used.
Passwords containing square brackets caused the error message cannot convert instance of class org.jruby.RubyArray to class java.lang.String. Using an asterisk or curly brackets resulted in a similar error message.
Tableau Server sometimes displayed an Incorrect data type error message when opening a workbook containing stacked dual axis panes and pages.
Publishing workbooks could cause a 500 Internal error on servers configured with a European locale such as German or Portuguese. The error was caused by the product version being reported incorrectly, which created an incompatible version match between Desktop and Server.
An ampersand character (&) in a Salesforce username or password would cause an Internal Server Error.
On Tableau Server, legends for the mapping data layer legend would sometimes appear as an empty box.
When views were published to Tableau Server, excess space was sometimes introduced between mark labels and marks.
For views connected to multidimensional (cube) data sources, clicking on a quick filter based on a hierarchy would cause a Tableau Exception error message.
In certain server configurations, using the command line to append data to a published extract that contained a parameter could cause the application to unexpectedly exit.
An error would occur when a workbook was published by an author who belonged to a Tableau Server group that was owned by a user that no longer existed.
When workbooks were published to Tableau Server, mark labels were incorrectly given the same transparency as marks.
When using the Tableau for iPad application to connect to servers configured to use SSL, a Couldn't load all data from Tableau Server. The request timed out error would occur.
Tooltips would not display if they had a Menu Filter Action and an invalid URL action.
Locales that use English but not U.S. English could not load Tableau Public visualizations in either Internet Explorer or Safari. The problem affected both mobile devices and computers.
When exporting to PDF from Tableau Server, legends were not always positioned correctly. For example, legends configured to display below the view would be displayed to the right of the view. This issue only occurred after clicking the Export button at the bottom of the view and not when appending PDF to the URL.
Optimized performance for some specific cases where the Data Server was slow to respond.
Enhanced security support for Tableau Server's PostgreSQL database.
In previous versions, for connections to Tableau Server data sources, acceleration views were cached remotely on Tableau Server. Now they are cached locally on the computer running Tableau Desktop. This change reduces latency and improves server performance.
Improved performance in retrieving and loading data for SAP BW connections.