L'analyse de données à la portée de tous.
Une solution sur site pour les entreprises.
Une solution hébergée pour les entreprises.
Notes de version pour Tableau 8.3.3
When using client-side rendering, axis rulers on published dashboards did not extend the full length and width of the view if viewed on devices using Retina displays.
When you deleted a custom view and created a new view with the same name, the view showed the data from the original view and the view name was "Unlisted Custom View".
When Tableau Server is configured to use a external load balancer or proxy server, Kerberos authentication failed with the error: “No key table entry found matching .”
Using the Tableau Data Extract Command-Line Utility to perform an extract refresh on Tableau Server configured to use SAML or sites that use https://online.tableau.com caused the error: “Username or password incorrect.”
A map view could not properly display when it contained millions of marks.
In views that displayed marks on the left side of the axis, a tooltip disappeared before you were able to select an option from the tooltip.
Upgraded to libpng 1.6.16 to address an external security vulnerability.
Upgraded to the latest version of OpenSSL (1.0.1k).
When using the command "tabadmin set vizqlserver.rserve.password" to set a password that begins with 0 (zero), the password was not correctly set in workgroup.yml.
When using a published data source, if you hid a calculated field and published a workbook, the hidden field would display.
Using parameters in a bin caused values to show as zero instead of the values in the data.
When using web authoring to edit a published workbook, if you deleted a sheet, then added a new sheet and saved it with the same name as the deleted sheet, an error displayed: "LogicException: Internal Error An unexpected error occurred".
Typing text in a wildcard search quick filter with a custom sort order resulted in an error: "Uncaught TypeError: Cannot read property 'toString' of Undefined".
Attempting to establish an impersonated database connection to a SQL database using a user name with an apostrophe caused an error: "TableauException: Microsoft SQL Server was unable to establish an impersonated database connection."
When using a URL action to pass parameters from one dashboard to another, no data was displaying in the view because an ampersand in the data being passed in the action was not encoded.
Dashboard filter actions did not navigate to a worksheet unless you selected the object before the action.
On Tableau Server, connecting to or using a published workbook that joins a table containing custom SQL with a parameter to another table resulted in the error: "Custom SQL relation refers to a non-existent parameter: [Parameters].[Parameter 1]