|
516269 |
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.
|
|
|
450181 |
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.
|
|
|
476788 |
In some cases, running multiple highlight actions on a dashboard exhibited different behavior between Tableau Desktop and Tableau Server.
|
|
|
479808 |
Importing users into Tableau Server from a file did not recognize domain nicknames and the import would fail.
|
|
|
481788 |
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".
|
|
|
492018 |
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.
|
|
|
492677 |
When embedding a Tableau Server view using the :tabs=no URL parameter, the view toolbar would not show in the browser.
|
|
|
501593 |
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.
|
|
|
503807 |
In Tableau Server, scheduled extract refreshes would intermittently fail with a logic assert error.
|
|
|
507404 |
In some cases in Tableau Server, tooltips would prematurely disappear when clicking on a header and trying to use the tooltip command buttons.
|
|
|
501054 |
In some cases, incrementally refreshing a Salesforce extract would cause excessively slow Data Engine queries resulting in workbooks appearing to fail to load.
|
|
|
455561 |
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".
|
|
|
502670 |
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.
|
|
|
503469 |
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.
|
|
|
503672 |
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".
|
|
|
504875 |
In some cases, incrementally refreshing a Salesforce extract would remove some or all data from the extract.
|
|
|
509823 |
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".
|
|
|
513787 |
After a scheduled or manual extract refresh for a workbook or data source, testing the associated data connection in Tableau Server would fail.
|
|
|
522949 |
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".
|
|
