|
504859 |
Borders between filled map shapes would unexpectedly appear when exporting the view to an image or publishing to Tableau Server.
|
|
|
494469 |
When joining tables, the default join relationships were often not the expected ones.
|
|
|
487198 |
In Tableau Desktop, when you opened a workbook connected to a published SAP HANA data source containing prompts, a blank worksheet without prompts appeared until you refreshed (F5) the data source.
|
|
|
501271 |
When connected to HP Vertica in Tableau Desktop using a version 7.1.x driver, Unicode characters were not displayed correctly.
|
|
|
462171 |
In Tableau Desktop, when you used multiple SAP BW extract data sources in a workbook, refreshing any one extract overwrote the other extract data sources with the same data.
|
|
|
501986 |
In Tableau Desktop, when publishing a workbook or data source utilizing an Other Databases (ODBC) connection, there was no option to publish with embedded password authentication.
|
|
|
488957 |
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.
|
|
|
504161 |
In some cases in Tableau Desktop, changing the scope for mark labels from Table to Pane had no effect.
|
|
|
482369 |
Changing a workbook parameter that was tied to a Microsoft SQL Server stored procedure parameter would sometimes cause Tableau Desktop to become unresponsive.
|
|
|
496070 |
Extracts in workbooks published to Tableau Server fail to refresh with a "cannot evaluate user filter; no current user or group" error when the extract was part of a data source containing a user filter.
|
|
|
313098 |
In Tableau Desktop, using an Microsoft SQL Server datetime2 field would sometimes result in an error: "The conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value.
|
|
|
423572 |
Color palette changes were sometimes not saved in Tableau Desktop. The issue may still occur but it is now possible to reset color assignments and reapply a color palette to correct the issue.
|
|
|
464924 |
In Tableau Desktop, filters containing table calculations would sometimes cause row and column grand totals/sub-totals to disappear.
|
|
|
465308 |
Hidden or invalid fields in a data source, that were not visible in Tableau Desktop, would sometimes appear when using web authoring in Tableau Server.
|
|
|
478182 |
In Tableau Desktop, connecting to an OData data source utilizing digest authentication was not supported and attempts to connect would fail.
|
|
|
478270 |
Connections to some databases from Tableau Desktop would fail to drop some temporary tables upon connection close.
|
|
|
493000 |
When connected to Sybase ASE in Tableau Desktop, the Sort by Field option was not available in the Sort dialog when sorting a dimension.
|
|
|
496954 |
When connected to a cube data source, sheet titles that dynamically changed with filter selections would sometimes fail to display the correct values.
|
|
|
483979 |
When connected to SybaseIQ in Tableau Desktop, attempting to edit a Top N set filter would fail with an error.
|
|
|
485958 |
When signing into Tableau Server from Tableau Desktop, the remembered user name would drop the domain prefix if it had been previously entered.
|
|
|
493436 |
In Tableau Desktop, when connected to a Salesforce data source, if you changed the data type of a field and then edited the data source it was possible to end up with a broken data source.
|
|
