|
388959 |
On computers with certain graphics cards, unwanted borders sometimes appeared in the view.
|
|
|
435210 |
In certain environments with fewer than four CPU cores or under load with multiple concurrent queries, a "Tableau Data Engine Error: 4: DataFlow::GetColumn" error sometimes occurred.
|
|
|
423414 |
Deleting a parameter that was used in a story or dashboard resulted in an error message.
|
|
|
436210 |
In Tableau Desktop, changing the Fiscal Year Start month did not correctly update the view.
|
|
|
423823 |
On the Mac, exporting a large crosstab to Microsoft Excel sometimes produced a corrupt file.
|
|
|
426385 |
Opening certain workbooks in Tableau Desktop or loading them in Tableau Server or Tableau Online caused the following error message to appear: "No such function (= integer string)".
|
|
|
431255 |
When you edited a connection to Hortonworks Hive, the connection page sometimes did not correctly populate the "HTTP Path" field.
|
|
|
393009 |
Interacting with multiple parameters sometimes resulted in an unexpected error.
|
|
|
420939 |
The "tableau -p" command printed only the active sheet, instead of the whole workbook.
|
|
|
422210 |
Page Setup settings were not preserved when switching tabs.
|
|
|
422229 |
Tableau Desktop could not connect to Tableau Online when behind certain authenticated proxies.
|
|
|
422939 |
Cloudera Impala returned the following error message when filtering on groups: "IN and/or EXISTS subquery predicates are not supported in binary predicates".
|
|
|
427918 |
When using a Microsoft SQL Server data source, converting a date field to a string in a calculation added time stamps to the date.
|
|
|
430600 |
When using an SAP HANA data source, a formula that contained the DATETRUNC function returned an incorrect quarter for dates in March, June, September, and December.
|
|
|
431449 |
When opening a workbook in Tableau Desktop, providing incorrect data source credentials sometimes locked out the data source user account.
|
|
|
393009 |
Interacting with multiple parameters sometimes resulted in an unexpected error.
|
|
|
411489 |
On certain devices with accessibility tools (such as on-screen keyboards), changing the selection in the Calculated Field dialog box Function Category drop-down menu causeed Tableau Desktop to close unexpectedly.
|
|
|
376840 |
Tableau Desktop treated a binary collation on Vertica connections incorrectly as a case-sensitive string collation, which caused filters on string-typed fields to return incorrect data.
|
|
|
423414 |
Deleting a parameter that was used in a story or dashboard resulted in an error message.
|
|