9.3.3

Télécharger dès maintenant
This version is available from the Customer Account Center.

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.

Date de publication:
14 Juin, 2016
Numéro de version Tableau Desktop:
9300.16.0606.1812
Numéro de version Tableau Server:
9300.16.0606.1812

New Capabilities

No new capabilities.

Tableau Desktop (Back to top)
Issue ID
504875

In some cases, incrementally refreshing a Salesforce extract would remove some or all data from the extract.

489790

In some cases in Tableau Desktop, after refreshing an extract in a packaged workbook and saving the workbook, re-opening the workbook would fail with an unexpected error.

490239

In Tableau Desktop, connecting to an SAP BW query containing navigational attributes exceeding 28 characters, and attempting to use the attributes in a view, would result in an invalid MDX command error.

506152

If a workbook contained a data source with tables joined on a pivoted field, a data source error would occur every time the workbook was re-opened in Tableau Desktop, which then required editing the data source to redefine the join condition.

506775

Searching for fields in the Tableau Desktop Data pane would not display broken or invalid fields (i.e., fields with a red exclamation point) in the search results.

476990

When connecting to Google Analytics in Tableau Desktop running on a Windows 10 machine, and specifying a fixed date range or fixed start date, the calendar widget would partially or completely cut off Saturdays.

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".

503212

In Tableau Desktop, connecting to OData using Windows Authentication would fail.

502572

In Tableau Desktop, attempting to create a conditional extract filter, by formula, on a date field would result in an internal error.

503435

Removing a web page object from a dashboard, or closing the workbook containing the web page object, would sometimes cause Tableau Desktop to quit unexpectedly.

511716

When connected to Exasol in Tableau Desktop, converting a datetime field to float using the FLOAT() function would incorrectly return an integer.

502938

When creating a range of dates filter in Tableau Desktop, the slider and type-in boxes in the filter dialog did not allow for seconds to be specified.

486278

In some cases, a field that was unhidden in the data grid on the Data Source tab would still not appear in the Data pane when authoring a sheet. This tended to occur for fields containing mostly null values.

512045

In some cases in Tableau Desktop, attempting to use a published data source containing a parameter that was duplicated from an original parameter, with an angle bracket in its name, would result in an error: "Custom SQL relation refers to a non-existent parameter".

503795

In some cases, when you ran a filter action used to navigate between dashboards, it would unexpectedly trigger across all dashboards in the workbook and cause a cascading filter effect or take you to the wrong dashboard.

501054

In some cases, incrementally refreshing a Salesforce extract would cause excessively slow Data Engine queries resulting in workbooks appearing to fail to load.

515507

A site user with the "Unlicensed (Can publish)" role was not able to publish content from Tableau Desktop to Tableau Server if the same user also existed in a different site.

504160

In certain cases, when connected to Google BigQuery in Tableau Desktop, filtering on a field not used in the view would result in a "No such column" error.

517162

Opening workbooks connected to published data sources in multiple instances of Tableau Desktop would sometimes result in a "Worksheet unavailable" error when loading a view.

511348

In Tableau Desktop, a parameter inserted into the URL of a web page dashboard object used the display value of the parameter instead of its actual value.

501941

When attempting to edit a published data source in Tableau Desktop, if the data source resided on a Tableau Server configured to use a non-default port, an error would occur: "This workbook contains a Data Source that is dependent on a different Tableau Server. Multiple Tableau Server connections are not supported".

519083

When signing into Tableau Server from Tableau Desktop, if your Tableau Server was configured to use local authentication, the remembered username in the Tableau Desktop sign in dialog would contain a "local\" prefix and fail to sign in after entering your password. Removing the "local\" prefix would allow the sign in to succeed.

473011

When connected to a published data source in Tableau Desktop, attempting to pivot more than 26 columns in the data grid produced unexpected results.

476002

Editing a filter title on a dashboard would sometimes fail to preserve the change when saving and re-opening the workbook in Tableau Desktop.

Tableau Server (Back to top)
Issue ID
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.

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".

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".

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.

504875

In some cases, incrementally refreshing a Salesforce extract would remove some or all data from the extract.

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.

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.

503807

In Tableau Server, scheduled extract refreshes would intermittently fail with a logic assert error.

501054

In some cases, incrementally refreshing a Salesforce extract would cause excessively slow Data Engine queries resulting in workbooks appearing to fail to load.

507404

In some cases in Tableau Server, tooltips would prematurely disappear when clicking on a header and trying to use the tooltip command buttons.

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".

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.

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".

476788

In some cases, running multiple highlight actions on a dashboard exhibited different behavior between Tableau Desktop and Tableau Server.

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.

479808

Importing users into Tableau Server from a file did not recognize domain nicknames and the import would fail.

Tableau Online (Back to top)
Issue ID
501054

In some cases, incrementally refreshing a Salesforce extract would cause excessively slow Data Engine queries resulting in workbooks appearing to fail to load.

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.

This version is available from the Customer Portal or Alternate Download Site.

non-humans click here