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.
There is a known issue with Tableau Desktop and Tableau Server version 10.3.6. 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.
When searching for an Active Directory group from a secondary domain (i.e. specifying the name in SAMAccountName or UPN format) to import into Tableau Server, if you clicked Stop searching and import now the group would not be found due to the default domain being incorrectly appended to the group name.
Workbooks connected to multiple stored procedures that accepted parameters could become unresponsive.
In Multiple Values (Dropdown) filters, a single value was displayed instead of (Multiple values) when there were multiple values selected.
In some views, changing a filter and then selecting a mark would result in an error: tuple id cannot be resolved
Extract refreshes would fail with a misleading Tableau Data Engine error: The operation completed successfully. - Semaphore::Acquire. This was essentially a timeout error.
Exporting a site could fail with an error: TransactionException: commit failed.
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.
Certain workbooks would cause VizQL Server processes to crash and fail to load with an internal error.
Custom views created from a workbook based on a Microsoft Analysis Services data source failed to retain filter selections.
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.
After updating to the Microsoft Edge 16 browser an InvalidCharacterError error would occur when loading views.