In some cases, when you opened a workbook in Tableau Desktop, the application crashed if the workbook was downloaded from a mismatching version of Tableau Server, or if the same workbook had been opened in multiple major releases of Tableau Desktop on the same machine.
In Tableau Desktop, when connected to Spark SQL, converting an integer field to date resulted in an error when trying to use the field in a view or when extracting the data source.
In Tableau Desktop, when connected to a multi-dimensional data source with dimensions containing multi-level hierarchies, inserting a dimension into a sheet title displayed "Null" if the same dimension was also used as a filter and if a hierarchy level greater than 0 was selected.
In Tableau Desktop, when you added or edited a Web Page dashboard object, the edit dialog no longer contained the option to insert parameters.
When you refreshed a published extract based on a connection containing initial SQL using the Tableau Data Extract Command-Line Utility, an error occurred: "Tableau Data Engine Error: 4: Invalid Command: database: Path does not exist."
When you connected to SAP HANA in Tableau Desktop, variable value selection drop-downs sometimes showed incorrect values or no values at all. The drop-downs now correctly populate variable values based on mandatory input parameter values; however, if a mandatory input parameter is not defined, variable values still sometimes appear blank.
In Tableau Desktop, when you clicked "Yes" in the warning dialog box to embed data source credentials when publishing, credentials were still embedded even when "Allow publishers to embed credentials in a workbook or data source" was unchecked in Tableau Server general settings.
In Tableau Desktop, when you extracted a Progress OpenEdge data connection containing joined tables and an extract filter, the extract failed with an error if the data contained a boolean field.
In Tableau Desktop for Mac, when you exported a large worksheet as a crosstab to Excel, a dialog warning about the length of time required to export occurred, and then Tableau Desktop failed to export the crosstab. In a subsequent attempt, the same dialog flashed and then reappeared and persisted in an unclickable state, though the crosstab exported successfully.
In Tableau Desktop, when you changed a parameter originally configured to use a range of allowable values to then use all values, values outside of the original range were still unable to be selected.
In Tableau Desktop, when you replaced a local data source with a published data source, an internal error sometimes occurred.
In some cases in Tableau Desktop, when you replaced data sources, an unexpected error occurred.
When connected to Teradata, query band statements weren't issued with initial SQL related queries.
In Tableau Desktop, when connected to a Microsoft Analysis Services cube, attempting to modify mark labels resulted in an internal error if the view contained a continuous date field.
In Tableau Desktop, when connecting to an SAP BW query containing variables, the list of available operators wasn't complete for defining selection option variables.