Análisis que todos pueden usar.
Una solución local (in situ) para las empresas.
Una solución hospedada para las empresas.
Release Notes for Tableau 9.3.1
If you use the Tableau Online Sync client from Tableau Desktop on Windows to refresh extracts on Tableau Online, please upgrade Tableau Desktop from 9.3.1 to 9.3.2. For more information, see the Release Notes for 9.3.2.
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.
|ID DEL PROBLEMA||Descripción|
Borders between filled map shapes would unexpectedly appear when exporting the view to an image or publishing to Tableau Server.
In Tableau Desktop, when you opened a workbook connected to a published SAP HANA data source containing prompts, a blank worksheet without prompts appeared until you refreshed (F5) the data source.
When connected to HP Vertica in Tableau Desktop using a version 7.1.x driver, Unicode characters were not displayed correctly.
In Tableau Desktop, when you used multiple SAP BW extract data sources in a workbook, refreshing any one extract overwrote the other extract data sources with the same data.
In Tableau Desktop, when publishing a workbook or data source utilizing an Other Databases (ODBC) connection, there was no option to publish with embedded password authentication.
In Tableau Desktop, when you clicked "Yes" in the warning dialog box to embed data source credentials when publishing, credentials were still embedded even when "Allow publishers to embed credentials in a workbook or data source" was unchecked in Tableau Server general settings.
In some cases in Tableau Desktop, changing the scope for mark labels from Table to Pane had no effect.
Changing a workbook parameter that was tied to a Microsoft SQL Server stored procedure parameter would sometimes cause Tableau Desktop to become unresponsive.
Extracts in workbooks published to Tableau Server fail to refresh with a "cannot evaluate user filter; no current user or group" error when the extract was part of a data source containing a user filter.
In Tableau Desktop, using an Microsoft SQL Server datetime2 field would sometimes result in an error: "The conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value.
Color palette changes were sometimes not saved in Tableau Desktop. The issue may still occur but it is now possible to reset color assignments and reapply a color palette to correct the issue.
In Tableau Desktop, filters containing table calculations would sometimes cause row and column grand totals/sub-totals to disappear.
Hidden or invalid fields in a data source, that were not visible in Tableau Desktop, would sometimes appear when using web authoring in Tableau Server.
In Tableau Desktop, connecting to an OData data source utilizing digest authentication was not supported and attempts to connect would fail.
Connections to some databases from Tableau Desktop would fail to drop some temporary tables upon connection close.
When connected to Sybase ASE in Tableau Desktop, the Sort by Field option was not available in the Sort dialog when sorting a dimension.
When connected to a cube data source, sheet titles that dynamically changed with filter selections would sometimes fail to display the correct values.
When connected to SybaseIQ in Tableau Desktop, attempting to edit a Top N set filter would fail with an error.
When signing into Tableau Server from Tableau Desktop, the remembered user name would drop the domain prefix if it had been previously entered.
In Tableau Desktop, when connected to a Salesforce data source, if you changed the data type of a field and then edited the data source it was possible to end up with a broken data source.
When joining tables, the default join relationships were often not the expected ones.