In Japanese Windows environments, using tabcmd or the REST API to publish an extract containing Japanese characters in the file name would fail with an error.
Publishing an OAuth data source using the REST API would not correctly embed OAuth credentials.
In workbooks where actions are used to navigate between sheets, story points based on multiple data sources would sometimes fail to load.
Using level of detail calculations could, in some cases, generate slow-running SQL queries when connected to Teradata.
In some workbooks connected to published data sources, certain calculated fields could sometimes fail to evaluate, resulting in blank views.
When a file necessary to configure Tableau Server for SSL was missing, the error message misleadingly stated that the file failed validation. The error message has been updated to correctly state that the file cannot be found.
In the Sites page in Tableau Server, you could not sort the list of sites by the Guest Access column.
When you published a dashboard containing multiple sheets to Tableau Server, there were sometimes minor changes in sheet dimensions and alignment.
Refreshing a published view connected live to Google Sheets could sometimes take hours before the view was updated with new data.
Activating Tableau Server via command line using the tabinstallck.exe -activate command would cause tabinstallck.exe to crash.