Várias alterações foram aplicadas para aumentar a segurança. Para ver mais detalhes, consulte ADV-2017-16 e ADV-2017-18 nos Boletins de segurança.
ID do problema
At smaller display resolutions, the publish workbook dialog could be cut off and you would not be able to click the Publish button.
In some cases, when Hebrew text was used in a parameter and the parameter values were displayed in a dashboard, the word Parameter would be displayed instead of the parameter value.
In some cases, resetting the color palette in the Edit Colors dialog would not reset colors in the view.
Extracts on Tableau Server with hidden columns could sometimes be unhidden during an extract refresh.
The Sort by Field option was not available when you were connected to Apache Drill.
When attempting to connect to Spark SQL, an internal error would sometimes occur.
Aggregated boolean calculations would return False for totals even when only True records existed and the aggregate form was also True.
When you extracted a data source with string fields containing nulls, and converted to an integer, the nulls would be changed to zeros.
When connected to Microsoft Analysis Services, if you had a dimension in the view with a Top N condition applied and then attempted to add a named set as a context filter, an internal error would occur.
When connected to Oracle Essbase, changing a filter applied to selected worksheets would result in an internal error in some cases.
When copying aggregated decimal values (with 5 or more decimal places) from Tableau Desktop to Excel, the pasted value would sometimes have incorrect decimal placement.
In some cases, previously working connections to SAP HANA began failing with a Communication with the Tableau Protocol Server process was lost. error after upgrading to Tableau 10.2 or higher.
When connected to Presto, using a calculated field containing Chinese, Japanese, or Korean characters would sometimes result in an error: There must be two or more concatenation arguments.
Views in dashboards, in workbooks created prior to Tableau 10.0, could appear collapsed when the workbook was opened in Tableau Desktop 10.0 or higher.
An internal error would sometimes occur when the Force y-intercept to zero trend line option was used.
A typically benign error, Failed to load proxy credentials: 'The parameter is incorrect.' showed up excessively in log files, making troubleshooting difficult.
Tableau Desktop for Mac would sometimes quit unexpectedly when publishing a data source to Tableau Online.
Performing a union of Excel sheets could sometimes result in incorrect measure values.
Connecting to a local cube file (.cub) would fail inconsistently with various errors.
Published extracts based on Custom SQL could not be refreshed using the Data Extract Command Line Utility or the Online Sync Client (Tableau Bridge).
Column borders in workbooks created in Tableau 9.2, or prior, were not visible when the workbook was opened in Tableau 9.3 or newer. It was also not possible to add them.
When you explicitly set the geographic role of a field to None, the setting would not be retained after you edited the data source, refreshed an extract, or saved the workbook as a packaged workbook.
If a data connection is lost (e.g. timeout or disconnected network), adding a field into the view would error instead of prompting to reconnect.
Tableau Desktop sometimes became unresponsive when using multiple parameters with a data source based on a stored procedure.
Certain data blending scenarios, involving an SAP HANA data source as the primary data source, stopped working in Tableau 10.0 or higher when they worked in previous versions.
In some cases, colors assigned based on a calculated field did not persist when closing and reopening a workbook.
An intermittent crash would occur, when creating a connection to Google Analytics, if dimensions and measures were selected too quickly.
In some cases, extracting a published data source would unhide hidden fields in the data pane.