Tableau Server 8.1.6

Invalid JSON syntax caused issues with filters in published workbooks.

Working with a single workbook over a long period of time which includes navigating between tabs could encounter a CSS rules limit in Internet Explorer versions 6-9. Tableau was adding the CSS rules on each tab switch within the workbook which could accumulate to the IE limit. We now clear the unneeded rules when leaving a tab.

In certain versions of Firefox, views would sometimes take a very long time to load or to redraw after scrolling down. Other browsers performed these actions quickly. Firefox versions now perform the same as the other browsers.

Parameter controls where you type in values would not autocomplete if the parameter had more than 199 values.

The Tableau Server background process wasn't executing certain tasks in the PostgreSQL database, resulting in outdated cluster configuration details being kept instead of discarded.

Under heavy load, Tableau Server could generate frequent "502 – bad gateway" errors.

When using SAML configured to access multiple domains in AD, logging in with domain\username would fail.

After exporting a Tableau Server view to a PDF, the server view could then display broken image icons in place of the proper view elements.

Extract refreshes would hang in the background process until the process was manually terminated by a user.

On Tableau Server, a vertical line (slice/angle) would appear on pie charts that used Measure Names/Measure Values with null values; in this case the pie chart should either be full or empty.

Installing the 64-bit version of Tableau Server would install the 64-bit version of Tabcmd but not the 32-bit version. Both versions are now installed.

On Linux, the Tableau Data Extract API would return an error after running MakeOrder. The error text would begin: "com.tableausoftware.TableauException: server did not call us back".

Custom logos would not display on gateways located on worker servers.

Quick filters on hidden sheets would not be not exposed when a workbook was downloaded from or viewed on Tableau Server 8.0 or 8.1.

When publishing a workbook to Tableau Server, all users and groups would be displayed, including users and groups that were not associated with the selected project.

When restoring a Tableau Server backup from a production environment running Tableau Server 7.0.8 to an environment running Tableau Server 8.0.0, the backup would fail with an error: “ActiveRecord::JDBCError: ERROR: could not create unique index "users_luid_unique" Detail: Key (luid)=(8da1bbdf-10dd-4f5d-ba9c-7c732f1cf7a7) is duplicated.”

On Tableau Server, accessing a report that points to SQL Server Analysis Services 2012 would sometimes result in the error: "Analysis Services database error 0x80004005: An error was encountered in the transport layer." After clicking "Yes," the user would get routed to the other available server and the report would refresh.

Workbooks that connected to cube data sources would open with intermittent errors from the data source. This was due to numerical counters being added to measures, and to calculated measures in particular.

Addressed a "Denial of Service" vulnerability in Tableau Server's Ruby on Rails code.

On Tableau Server, quick filters would not be displayed after a view was exported as an image or PDF file. The issue would occur only when table calculations were being used to return string values that were being used as filters.

In Tableau Server, mark labels would sometimes overlap. The issue would affect vertical labels that use multiple text styles in the same line.

On Tableau Server, selecting "Assign Permissions to Contents" would not work as expected. For example, permissions assigned at the project level were not being applied to the workbooks in the project.