When workbooks with a horizontal scroll bar were published to Tableau Server, charts could be truncated at the bottom.
On Tableau Server, connecting to or using a published workbook that joins a table containing custom SQL with a parameter to another table resulted in the error: "Custom SQL relation refers to a non-existent parameter: [Parameters].[Parameter 1]
Unable to connect to the server ''. Check that the server is running and that you have access privileges to the requested database".
Dashboard filter actions did not navigate to a worksheet unless you selected the object before the action.
When using a URL action to pass parameters from one dashboard to another, no data was displaying in the view because an ampersand in the data being passed in the action was not encoded.
Attempting to establish an impersonated database connection to a SQL database using a user name with an apostrophe caused an error: "TableauException: Microsoft SQL Server was unable to establish an impersonated database connection."
When using web authoring to edit a published workbook, if you deleted a sheet, then added a new sheet and saved it with the same name as the deleted sheet, an error displayed: "LogicException: Internal Error An unexpected error occurred".
When exporting a view to PDF, legends appeared in the PDF export even though the legend card was hidden in the view.
Clearing All in a quick filter and then selecting All again caused a white space to appear at the top of the view where the caption was placed.
When the browser window was shrunk to a very small size and then returned to the original size, filter names remained truncated instead of showing full text.
Using client-side rendering caused the second line of text in some tooltips to become truncated.
Refreshing the browser two or more times when working with a published view with a multiple value filter disabled the Revert All button.
When row and column axes have different formats, Tableau Server displayed only one of the formats for both axes.
"Relative to Now" quick filters showed incorrect time when configured for Last N hours or Last N minutes.
The initial dashboard render for a workbook with relevant-value quick filters waited unnecessarily for acceleration view queries to complete and sometimes timed out.
When Tableau Server was configured to use an external load balancer or proxy server, Kerberos authentication failed with the error: “No key table entry found matching [n].
The "next run" time displayed for a schedule on the Schedules page could show a mismatch with the time range a schedule was supposed to run. This happened if the server was in a different timezone than the client computer.
A workbook publisher could sign in to Tableau Server and schedule an extract refresh for the workbook even when Tableau Server was not configured to allow scheduling.
With the REST API, using concurrent threads to create multiple sites and add users to those sites could cause the error: “user [username] was already added to the site [site id].”
Embedded views would not display when accessing HTML files using the file:// protocol.
After editing the data source name (i.e., the connection name) of a Tableau Server data source, the original name continued to appear when you re-edited the data source.
In map views published to Tableau Server, overlapping marks could not be individually selected.
When a URL parameter was used to change a table calculation sheet link action filter, a “LogicException” error would appear.
When using Internet Explorer browsers, tooltips would disappear too quickly, making it difficult to select links in the tooltip.
Using a hyphen (–) in search caused inconsistent results.
Multiple Values (custom list) quick filters would generate an "Unknown server error" when they were included in the first selected story point on a published workbook.
The "tabcmd export --png" command did not adjust the image width and height when you specified a width and height.
On occasion, when installing Tableau Server, the install would generate a "MoveFile failed;... Cannot create a file when that file already exists." error. Clicking Retry allowed the installation to complete successfully.