Release Notes for Tableau 9.1.5
This release addresses an issue found in Tableau Server 9.1.4 (9100.16.0114.0755) for some environments configured to use Active Directory. A change to the Active Directory user binding (from samAccountName to UPN) caused existing users to be removed from groups and new users to be added based on UPN when synchronizing Active Directory groups. This resulted in duplicate users and/or users not being able to sign into Tableau Server.
A new version, Tableau Server 9.1.5 (9100.16.0125.1553), is available from the Alternate Download Site.
In Tableau Desktop and Tableau Server, changing stored procedure parameters via workbook parameters resulted in an error: "No such table."
In Tableau Server, unauthorized users were given the option to export data or a crosstab that resulted in a blank page or unknown server error.
In Tableau Server, you could add multiple user or group rules without clicking "Save," which caused permissions to be applied incorrectly.
In Tableau Server, if you published a workbook using the "Prompt User" data source authentication mode, accessing the published workbook via trusted authentication resulted in a "Resource Not Found" error.
Exporting a Tableau Server site using the "tabadmin exportsite" command sometimes resulted in a "commit failed" error.
In Tableau Server, improperly URL encoded special characters caused certain URL actions to fail.
In Tableau Server, the command "tabcmd echo %ERRORLEVEL%" returned the exit code "0" for failed operations instead of a non-zero value.
In Tableau Server, using the "tabadmin reset" command to reinstate an administrator account did not correctly free up licenses.
After upgrading from Tableau Server 9.0 to 9.1 or higher, some dashboards presented an error when loaded: "Cannot read property 'w' of null."
In Tableau Server, using a color legend to filter a view resulted in an error: "Uncaught TypeError: e.get_blockType is not a function."
In Tableau Server, in a workbook connected to a published Cloudera Impala data source that did not use the default schema, using a relative date filter or the "NOW()" function in a calculated field resulted in an invalid table name error.
In Tableau Server, clicking "Done" in web authoring resulted in an error message instead of redirecting back to the Views page.
In Tableau Server, a change to the Active Directory user binding (from samAccountName to UPN) caused existing users to be removed from groups and new users to be added based on UPN when synchronizing Active Directory groups. This resulted in duplicate users and/or users not being able to sign into Tableau Server.
In Tableau Server, custom shapes and images on dashboards appeared blurry in browsers after publishing.
In Tableau Server, when configuring Tableau Server to use SAML, the exported metadata XML file was missing the SingleLogoutService element.
In Tableau Server, embedded views didn't load if the view belonged to a site name containing only numbers.
In Tableau Server, Teradata extracts could not be refreshed if the data connection contained a <ServerUser> or <ServerUserFull> query band parameter.
In a published workbook on Tableau Server, a legend sometimes included no specified title or body font, and resulted in an error: "undefined is not an object (evaluation 'e.pe.split')."
In Tableau Server 9.1 or higher, importing a site from Tableau Server 8.x failed.
In Tableau Server 9.1 or higher, using a highlight action in a workbook published from Tableau Server 8.2 resulted in an error.
In Tableau Server, extract files were sometimes missing after restoring a backup.
In Tableau Server, workbooks using published blended data sources sometimes did not load.