Release Notes for Tableau 9.3.3
Note: Tableau Desktop customers in environments with Product Updates enabled will be prompted to upgrade a few days after a maintenance release is made available. For more information, see the Tableau Knowledge Base.
In Tableau Server, the workgroup_session_id was being logged to the production.log file. Now the first 32 characters of the workgroup_session_id SHA-256 value are logged instead.
In some cases in Tableau Server, views based on file-based data sources would not display new data after you modified the underlying file-based data source.
In some cases, incrementally refreshing a Salesforce extract would remove some or all data from the extract.
Creating or refreshing an extract based on a published data source, and with visible dimensions aggregated, would fail with an error: "StarExtractTupleSource has wrong number of bindings for number of inputs columns".
After a scheduled or manual extract refresh for a workbook or data source, testing the associated data connection in Tableau Server would fail.
In Tableau Server, with workbook revision history enabled, exporting a site using tabcmd would fail with an error: "The file cannot be deleted in this code path, failing delete".
In some cases, running multiple highlight actions on a dashboard exhibited different behavior between Tableau Desktop and Tableau Server.
Importing users into Tableau Server from a file did not recognize domain nicknames and the import would fail.
In certain cases in Tableau Server, clicking the command buttons in a tooltip (e.g., Keep Only, Exclude) would result in an error: "tuple id cannot be resolved".
When viewing a Tableau Server embedded view, with "Show sheets as tabs" enabled, filter selection drop down menus would sometimes appear out of position in the browser window.
When embedding a Tableau Server view using the :tabs=no URL parameter, the view toolbar would not show in the browser.
In some cases, scheduled extract refreshes in Tableau Server would frequently fail with a "Cleaned up crashed job" message in the Background Tasks for Extract admin view.
In Tableau Server, scheduled extract refreshes would intermittently fail with a logic assert error.
In some cases in Tableau Server, tooltips would prematurely disappear when clicking on a header and trying to use the tooltip command buttons.
In some cases, incrementally refreshing a Salesforce extract would cause excessively slow Data Engine queries resulting in workbooks appearing to fail to load.
Trying to access a workbook or data source on Tableau Server containing the string "login" in its URL would result in an error: "SSL peer certificate or SSH remote key was not OK".
In Tableau Server or Tableau Online, editing a Salesforce connection would show "No Salesforce authentication" selected even if the workbook or data source was published with embedded password. This was mainly a display problem as extract refreshes were still successful.
In Tableau Server, it was possible to execute an extract refresh task for a workbook or data source in a site other than the one you were signed in to.
In Tableau Server, navigating between workbooks in different sites, via URL action, would intermittently fail to display workbook content and display an error instead: "The page could not be accessed. Either the workbook does not exist or you do not have the necessary permissions".