Análise ao alcance de todos.
Uma solução local para empresas.
Uma solução hospedada para empresas.
There is a known issue with Tableau Desktop and Tableau Server version 10.4.2. You may encounter a string comparison error when loading views which use very long strings and double-byte characters. For more information, please see the following KCS article.
Changes were applied to improve security. See ADV-2017-023 in Security Bulletins for more details.
Workbooks opened from some non-SSL enabled Tableau Servers would show up in the Tableau Desktop recently opened workbooks list with the workbook name followed by [http].
Desktop and Reader 10.4 display incorrectly when Windows High DPI scaling is set to 150%.
Workbooks connected to multiple stored procedures that accepted parameters could become unresponsive.
In Tableau Desktop, the drop down menu in the sign in dialog for Tableau Server did not retain server names for non-SSL enabled servers.
Use of certain SAML identity providers could result in a blank sign in window when connecting to Tableau Server or Tableau Online.
If one of your tables involved in a join contained a field with a user-defined, or otherwise unknown, type, attempting to create a join calculation would result in an internal error.
In some cases, the dimensions of layout containers changed size after upgrading to Tableau 10.0 or higher from a prior version, causing objects in the container to disappear.
Creating a local copy of a calculated field from a published data source would name the copy as Calculation_XXXXXXXXXXX if the calculated field contained user functions.
When connected to a cube datasource, filter selections in Multiple Values (Custom List) filters were not shown when printing a dashboard to PDF.
Extracting a table containing large strings would sometimes fail with an Error generating sort key error for certain collations.
Adding additional files to a data source in a packaged workbook would eventually cause the workbook to fail to open with an error: Error getting archive file info (0)
When you selected a custom shape mark and then printed the view to PDF, the mark would not appear selected in the resulting PDF.
In views with a reference line, selecting marks or legend items would update the reference line value dynamically. If you printed the view with a selection, or exported it to a PDF/image, the resulting image or PDF would not display the correct reference line value based on the selection.
Workbooks based on published data sources would fail to load when there was a discrepancy in the data source folder structure between the workbook and published data source.
When you opened a workbook containing sheets with Auto Update Worksheet turned off, changing to another sheet would unexpectedly cause that sheet to load.
Workbooks connected live to an Excel file data source would sometimes fail to display the latest data upon opening the workbook, requiring a manual data source refresh. In those cases, even after you refreshed the data source and saved the workbook, old data would be shown if you closed and re-opened the workbook.