Issue ID | Description |
---|---|
When you created a Date & Time parameter, and used a custom date format to show milliseconds, the millisecond time component was arbitrarily set based on the current time and could not be corrected. Milliseconds are now set to zero by default and still cannot be edited. | |
After setting the Start page to the Sites page, Server Administrators were unable to log into some Tableau Server sites from Tableau Desktop. | |
In some cases, valid calculations returned an 'Invalid datetime error' error message. | |
In some cases, calculated fields containing multiple level of detail expressions returned unexpected results. | |
In some cases where some sheets in a dashboard have been filtered down to display a single data point, tooltips containing views (Viz in tooltip) would show the same view when hovering over marks in different sheets. Duik download after effects. | |
An unknown collation error would occur when connecting to CSV files using the Norwegian Bokmål (Norway) locale. | |
Updated postcode data for the Czech Republic. | |
In some Mac environments, visualizations would either disappear or turn into black boxes on when the Tableau Desktop window was dragged to a secondary display. | |
With accelerated graphics enabled, text in annotations that was set to a font size of 48pt or higher was not rendered cleanly on some systems. | |
When you were connected to IBM DB2 and using date filters, the TIMESTAMP_ISO function was sometimes used in queries which negatively impacted performance. | |
In histogram views, the axis labels did not match the bin values represented by the marks in the view. | |
Updated Japanese postcode data. |