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.
When connected to a published data source in Tableau Desktop, attempting to pivot more than 26 columns in the data grid produced unexpected results.
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.
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.
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.
In Tableau Desktop, connecting to OData using Windows Authentication would fail.
In Tableau Desktop, attempting to create a conditional extract filter, by formula, on a date field would result in an internal error.
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.
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.
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.
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.
In some cases, incrementally refreshing a Salesforce extract would cause excessively slow Data Engine queries resulting in workbooks appearing to fail to load.
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.
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".
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.
In some cases, incrementally refreshing a Salesforce extract would remove some or all data from the extract.
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.
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.
Editing a filter title on a dashboard would sometimes fail to preserve the change when saving and re-opening the workbook in Tableau Desktop.
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.
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".
When connected to Exasol in Tableau Desktop, converting a datetime field to float using the FLOAT() function would incorrectly return an integer.
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".
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.
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.