Notas de versão do Tableau 8.2.8
Making a connection to an HP Vertica data source could take a long time.
When using Tableau Desktop to connect to a published data source that does not normally require credentials (extracts and certain Hive Server configurations), a data source with embedded password, or a data source with integrated authentication (SSPI for example), you are prompted unnecessarily for credentials.
If you click Cancel, the prompt closes but you are left at a blank screen. If you click OK without entering anything, the prompt displays again.
To work around this, enter any value for username and password when prompted, then click OK to continue as usual.
This issue was found in the 2/19 release of Tableau Desktop 8.2.8 and is corrected in the 2/20 release of 8.2.8 (build 8200.15.0219.2110).
When connecting to a Pivotal Greenplum data source using the ODBC driver, long string values were truncated to 100 characters.
Making a connection to Odata took longer than in previous versions.
When connecting to a data source, Tableau Desktop quit unexpectedly.
When connected to an Oracle database, copying and pasting sheets between workbooks resulted in the error: "Oracle database error 1005: ORA-01005: null password given; logon denied".
When you added comments to a set in a workbook and saved the workbook, the comments were not saved. The next time you opened the workbook, the Comment field was blank.
When using a published data source, if you hid a calculated field and published a workbook, the hidden field would display.
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.
Upgraded to the latest version of OpenSSL (1.0.1k).
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".
Upgraded to libpng 1.6.16 to address an external security vulnerability.
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".
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".
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 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 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.
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]
Using parameters in a bin caused values to show as zero instead of the values in the data.