Tableau Changelog

What's new in Tableau 2024.1.1

Mar 27, 2024

Resolved Issues:
W-14411304 When a parameter with string value is added to the URL of a Web Page object, a strange error ""’s server IP address could not be found"" (the parameter name can vary) may appear.
This appears to be an authoring issue - in other words, the issue only occurs with new workbooks, or when the Web Page object is modified.

New in Tableau 2024.1.0 (Feb 22, 2024)

New in Tableau 2023.3.3 (Feb 16, 2024)

New in Tableau 2023.3.2 (Jan 31, 2024)

New in Tableau 2023.3.1 (Jan 11, 2024)

New in Tableau 2023.3.0 (Oct 25, 2023)

New in Tableau 2023.2.2 (Sep 22, 2023)

New in Tableau 2023.1.2 (May 19, 2023)

New in Tableau 2023.1 (Mar 15, 2023)

New in Tableau 2022.4.1 (Feb 24, 2023)

New in Tableau 2022.4 (Feb 24, 2023)

New in Tableau 2022.3.1 (Nov 18, 2022)

New in Tableau 2022.3 (Oct 19, 2022)

New in Tableau 2022.2.2 (Sep 29, 2022)

New in Tableau 2022.2.1 (Aug 31, 2022)

New in Tableau 2022.2.0 (Jun 30, 2022)

New in Tableau 2022.1.3 (Jun 22, 2022)

New in Tableau 2022.1.2 (May 25, 2022)

New in Tableau 2022.1.1 (Apr 23, 2022)

New in Tableau 2022.1.0 (Mar 31, 2022)

New in Tableau 2021.4.4 (Feb 25, 2022)

New in Tableau 2021.4.3 (Jan 14, 2022)

New in Tableau 2021.4.2 (Dec 20, 2021)

New in Tableau 2021.4.1 (Dec 16, 2021)

New in Tableau 2021.4 (Dec 10, 2021)

New in Tableau 2021.3.4 (Dec 2, 2021)

New in Tableau 2021.3.3 (Oct 27, 2021)

New in Tableau 2021.3 (Sep 8, 2021)

New in Tableau 2021.2.2 (Sep 3, 2021)

New in Tableau 2021.2.1 (Jul 25, 2021)

Resolved Issues:
An intermittent error: "Unable to complete action. Internal Error - An unexpected error occurred and the operation could not be completed. Error Code: 0E1EAFA4" could occur when editing a view.
When attempting to refresh or open a workbook with multiple data source, the error could display stating, "ERROR: no such field '[Calculation_XXXX:ok]', datasource='(name)."
"Error: Unable to complete action. Internal Error - An unexpected error occurred and the operation could not be completed. Error Code: 6EA18A9E" could occur when publishing or opening a workbook on Tableau Server when there is a table calculation, a parameter, and data blending in one worksheet.
Error code 6ea18a9e could display when performing an incremental refresh of an extract that uses custom SQL.
OData V3 could fail to refresh using 2020.3+.
A workbook could generate a "collation mismatch" error when trying to view full data with Excel and extract data sources.
An extract could repeatedly be created when switching between the sheet and the data source tab even after the extract had been created successfully.
The Impala data connector would fail to connect via the HTTP transport protocol.
With PostgreSQL data, a timezone set by the initial SQL command when connected via JDBC would fail to apply.
When opening and closing workbooks, aliases and sorts were sometimes not saved when connected live to Microsoft Access.
Some users were not able to log into Tableau Online from Tableau Desktop when using a Gmail email account.
"Error code 2F0F5E42" could display when a workbook was connected to a live data source with joined tables.
Error Code: F5328B32, "Tableau cannot evaluate the query that results from this calculation" could result when more than one spatial calculated field is added to the view.
In Tableau Reader, a workbook would fail to open when custom geocoding was contained.
A "Driver not found" error message would sometimes result and the sign-button was unavailable when opening a workbook connected to an Impala data source.
Presto data queries could fail with the error, "Value is not a number: java.lan.String", when converting custom SQL to decimal using the DECIMAL() function to cast the data type.
When generating the forecast for a Measure, an "Internal error" could occur.

New in Tableau 2021.2 (Jun 24, 2021)

New in Tableau 2021.1.2 (May 19, 2021)

New in Tableau 2021.1.1 (Apr 23, 2021)

New in Tableau 2021.1 (Mar 26, 2021)

New in Tableau 2020.4.3 (Mar 25, 2021)

New in Tableau 2020.4.2 (Feb 26, 2021)

New in Tableau 2020.4.1 (Jan 22, 2021)

New in Tableau 2020.4 (Dec 15, 2020)

New in Tableau 2020.3.3 (Nov 23, 2020)

New in Tableau 2020.3.2 (Oct 30, 2020)

New in Tableau 2020.3.1 (Oct 1, 2020)

New in Tableau 2020.3 (Aug 12, 2020)

New in Tableau 2020.2.4 (Jul 31, 2020)

New in Tableau 2020.2.2 (Jun 24, 2020)

New in Tableau 2020.2.1 (May 29, 2020)

New in Tableau 2020.2 (May 27, 2020)

New in Tableau 2020.1.3 (Apr 30, 2020)

New in Tableau 2020.1.2 (Apr 1, 2020)

New in Tableau 2020.1 (Feb 25, 2020)

New in Tableau 2019.4.2 (Jan 24, 2020)

New in Tableau 2019.4.1 (Dec 20, 2019)

New in Tableau 2019.4 (Nov 7, 2019)

New in Tableau 2019.3.1 (Oct 25, 2019)

New in Tableau 2019.3 (Sep 19, 2019)

New in Tableau 2019.2.3 (Aug 23, 2019)

New in Tableau 2019.2.2 (Jul 25, 2019)

New in Tableau 2019.2.1 (Jun 26, 2019)

New in Tableau 2019.2 (Jun 26, 2019)

New in Tableau 2019.1.3 (Apr 24, 2019)

New in Tableau 2019.1.2 (Mar 27, 2019)

New in Tableau 2019.1.0 (Feb 13, 2019)

New in Tableau 2018.3.3 (Feb 1, 2019)

New in Tableau 2018.3.2 (Feb 1, 2019)

New in Tableau 2018.3.1 (Dec 6, 2018)

New in Tableau 2018.3 (Oct 30, 2018)

Resolved Issues:
When you used a filter on a data source with a non-January fiscal year start, sometimes an "Unable to complete action Internal Error - An unexpected error occurred and the operation could not be completed" error occurred.
Selecting Total Using > Server with an ASO cube resulted in a “value 'Server' not in enumeration” error.
Creating an extract in a remote shared folder using Tableau Desktop 2018.2 on a Mac failed with an "fcntl(): Operation not supported" error.
When you changed a "Multiple Values (dropdown)" filter to select no values, then a single value, an "Unable to Complete Action: Table Arrays Must be of the Same Size" error occurred.
When using a cluster in a workbook, extract refreshes sometimes failed with the error "Unable to complete action Internal Error - An unexpected error occurred and the operation could not be completed."
int64 field in OData sometimes rounded incorrectly.
When using Tableau Desktop with Microsoft Office IME 2010 Japanese, re-entering Japanese words do not convert them properly in the field name search. It looks like incremental auto-search is interrupting the IME character conversion and resulting in unintended characters appearing in search string.
When you connected to an Odata feed from a non-default namespace, an "Odata: Cannot find corresponding ComplexType" error occurred.
When doing a wildcard search on a pivoted field based on a .csv data source, a "collation mismatch" error sometimes occurred.
When you added description text to a story point, and then deselected the text object, you could not format the description again.
Using a calculated field containing a spatial geometry field and an failed conditional statement could result in an error: "unable to deduce expression type, use 'NULL::' to specify the type"
Updated province data for the Democratic Republic of the Congo.
Updated Turkish postcode data.
Many Thai vowel characters were not rendered correctly in Tableau Desktop.
After you refreshed an extract, saving the workbook would silently fail to retain the extract location if the extract was also open in another instance of Tableau Desktop, resulting in an "Extract not found" error upon reopening the workbook. There is now a warning for the failure and you are prompted to specify an alternate location to save the new extract data.
Updated Australian postcode data.
Updated German postcode data.
Updated German county data.
Sometimes, nested level of detail calculations in a workbook produced an "Error occurred communicating with the data source. No such column [Calculation_]." error message.
When trying to create an extract of Sybase ASE using a MAX() or Top N extract filter, the extract would fail.
When using the NOW() function with a live connection to Snowflake, Tableau followed the data source location time instead of the time configured on the data source server.

New in Tableau 2018.2.3 (Oct 17, 2018)

New in Tableau 2018.2.2 (Sep 28, 2018)

New in Tableau 2018.2.0 (Jul 31, 2018)

New in Tableau 2018.1.3 (Jul 11, 2018)

New in Tableau 2018.1.2 (Jun 20, 2018)

New in Tableau 2018.1.1 (May 18, 2018)

New in Tableau 2018.1.0 (Apr 24, 2018)

New in Tableau 10.5.3 (Apr 24, 2018)

New in Tableau 10.5.3 (Apr 15, 2018)

752269: Sometimes Tableau Desktop closed unexpectedly when performing a Save As on a Mac.
751448: When viewing Full Data in Tableau Desktop or downloading Full Data in Tableau Server, sometimes a timeout error occurred.
748917: When attempting to insert a user filter in Tableau Desktop, if there were multiple Tableau Server groups with the same name, they all showed the user list from the first group created, and the filter selection would apply to all groups with the same name.
749485: Japanese and Korean characters sometimes could not be typed correctly into the calculated field dialog.
747446: After upgrading a .tde file to .hyper, sometimes DATEPARSE calculations would return unexpected results.
742840: If Tableau Server contained more than 201 projects, the Publish Workbook to Tableau Server dialog in Tableau Desktop would not display all the projects.
742824: Highlighters would be removed when replacing data sources.
742816: After upgrading an extract and navigating to a dashboard, sometimes Tableau Desktop closed unexpectedly.
740884: In environments requiring proxy authentication for internet access, Tableau Desktop would sometimes crash after entering proxy credentials.
740687: In some cases, when you opened a workbook based on a Hive data source on a Mac, Tableau Desktop quit unexpectedly.
739827: After upgrading extracts to .hyper, some workbooks would load slower due to calculated fields triggering extremely large CASE expressions.
738055: Level of detail calculations containing user references would disappear from a data source after it was published to Tableau Server.
732938: Selecting a project when publishing a workbook to Tableau Server would sometimes cause Tableau Desktop to crash. Upgrading Tableau Desktop and Tableau Server is required to resolve this issue.
731436: Materialized calculated fields were removed from published extracts when refreshed using the Refresh from Source option in Tableau Desktop or when refreshed using Tableau Bridge.
718914: When connecting to the Campaigns standard Salesforce connection in a Chinese, Japanese, or Korean Tableau Desktop environment, a Table alias is not unique error would occur.
717462: When connected to Google BigQuery, adding a level of detail calculation to the view would unexpectedly remove valid null values from the view.
700985: Creating and saving an extract on a Mac would sometimes cause Tableau Desktop to crash.
674665: Added query cancel notifications for PostgreSQL and Vertica connections.

New in Tableau 10.5.2 (Mar 9, 2018)

New in Tableau 10.5.1 (Feb 16, 2018)

733764: In some Mac environments, connecting to a data source or opening an existing workbook would result in repeated attempts to complete the action and eventual failure with an error: an error occurred while communicating with hyper.
710181: Body font color formatting did not work for compact list parameters.
716683: In non-English environments, a garbled message could be shown in the authentication window after signing into your Google account when connecting to Google Analytics or Google BigQuery.
718104: In some cases, calculated fields containing the LEFT() function returned unexpected results when connected to data containing non-English strings.
720024: When you exported a dashboard as an .emf image, and your display scaling (DPI) was set to something other than 100%, text alignment would be off in the resulting image.
726475: When connected to a web data connector data source, the data source name would be displayed in parenthesis next to all field names.
711871: In some environments, the Tableau Bridge client would quit unexpectedly when switching it to run in service mode.
717252: Next Refresh Time and Last Refresh Time were not being properly updated in the Tableau Bridge client.
728814: When you connected to a text or CSV file using most English locales other than English (United States), a collation::resolve: Unknown collation error would occur when you dragged a field to the view.
733366: When performing a cross-database join involving a legacy Excel connection, and error would occur: collation mismatch, use COLLATE statements to resolve
721830: Hyper logs would not get created if the file path for your My Tableau Repository folder included non-ASCII characters. The result was an inability to connect to data sources.
726001: When you applied a dimension filter with a wildcard match, the entire view would be incorrectly filtered out. If you toggled a filter setting and clicked Apply again, the filter would work as expected.
706208: A Tableau Data Engine Error: 504 error could occur refreshing a view that utilized data blending of file-based data sources in the same folder.
702237: Workbooks opened from some non-SSL enabled Tableau Servers would show up in the Tableau Desktop recently opened workbooks list with the workbook name followed by [http].
705898: When connected to Denodo, generated queries would sometimes contain unnecessary case statements.

New in Tableau 10.5.0 (Jan 11, 2018)

CONNECT TO AND PREPARE DATA:
Extracts use the new .hyper format:
Beginning with version 10.5, when you create an extract, it uses the new .hyper format. Extracts in this new format take advantage of the improved data engine, which supports the same analytical and query performance as the data engine before it, but for even larger extracts. Similarly, when you perform an extract task on a .tde extract using version 10.5, the extract is upgraded to a .hyper extract. For more information, see Extract Upgrade to .hyper Format.
Google authentication method update:
Starting in October 2017, Google's updated security requirements changed the connection workflow for some Tableau connectors. Now Tableau opens at tab in your external default browser when connecting to data that uses OAuth authentication. The connectors affected are Google Sheets, Google BigQuery, Google Analytics, Dropbox, OneDrive, and Box.
New Box connector:
Use the Box connector to connect to Box data. For more information, see Box.
Support for SSL authentication to IBM DB2 and BigInsights databases:
You can now connect to IBM DB2 and IBM BigInsights databases using SSL authentication.
Use the Extract API:
You can use the Extract API 2.0 to create .hyper extracts. For tasks that you previously performed using the Tableau SDK, such as publishing extracts, you can use the Tableau Server REST API or the Tableau Server Client (Python) library. For refresh tasks, you can also use the Tableau Server REST API. For more information, see Tableau Extract API.
SAP HANA support for failover:
Tableau supports connecting to a server that’s configured for failover. For more information, see SAP HANA.
SAP Sybase ASE support for SSO:
You can now connect to SAP Sybase ASE data using single sign-on (SSO). For more information, see SAP Sybase ASE.
Support for OData V4:
You can now connect to OData V4 data connections. For more information, see OData.
DESIGN VIEWS AND ANALYZE DATA:
Show visualizations in tooltips:
As you craft views and look for ways to reveal more details about data to your audience, you can embed visualizations within tooltips—aka "Viz in Tooltip." As users hover over a mark, the tooltip displays relevant data and details from another visualization filtered to that mark. When you show related views in tooltips, you can help your audience engage with the data at a deeper level, while keeping them in the current context and maximizing the space available for the current view. For details, see Create Views in Tooltips (Viz in Tooltip).
Power trend lines:
When you add trend lines to a view, a Power option is now available. For related details, see Add and Edit Trend Lines and the "Power" model type in Trend Line Model Types.
Map data updates and additions:
In Tableau 10.5, additional cities are available for South East Asia, Central America, and South America.
Demographic data updates including 2018 to 2023 statistical projections are now available.
U.S. Core Based Statistical Areas (CBSA) and Metropolitan Statistical Areas (MSA) are up to date with 2015 definitions.
Updates are now available for U.S. postcodes.
Additionally, the following updates are now available for China:
The areas of Beijing, Chongqing, Shanghai and Tianjin no longer contain city-level districts in the Administrative level 2/County geographic role.
Administrative level 2 features in China (prefecture-level cities, prefectures, leagues, autonomous prefectures) are considered cities in Tableau. The center points of these areas are included in the City geographic role as well.
Additional cities such as Tiemenguan are now included in the City geographic role.
Names for Administrative level 1 & 2 features are now consistent with names published by the People’s Republic of China’s National Bureau of Statistics.
Extend dashboard dimensions to 10,000 pixels:
To optimize designs for very large screens or vertical mobile layouts, you can now extend dashboard width and height to 10,000 pixels.
PUBLISH DATA SOURCES AND WORKBOOKS:
Downgrade workbooks in Tableau Desktop:
If you upgrade a workbook in Tableau Desktop to a newer version, you can now downgrade it to a previous version so that users who are using Tableau Desktop 10.2 and later can still open the workbook. To downgrade the workbook, in Tableau Desktop select File > Export As and select the version that you want to downgrade to. Then save it to your My Tableau Repository or a selected location. The downgraded workbook can be opened in the version selected and later. Any features not available in that previous version will be removed when the workbook is downgraded. For more information about version compatibility, see Make Workbooks Compatible Between Versions.
Note: This feature is not available for workbooks that include a Tableau Data Extract that has been refreshed in 10.5. The extract will have been converted to use the new .hyper format and this format can't be downgraded back to a .tde format.
NEW IN WEB AUTHORING:
Edit axes on the web. To open the Edit Axis dialog box on the web, double-click an axis in the view. Options available from the Edit Axis dialog box include Synchronize dual axes, clearing the axis range (Reset), and editing tick marks. You can also enable or disable Dual axis in a field context menu (right-click a measure field on Rows or Columns shelf).
Add text objects to dashboards and edit them.
Edit worksheet and dashboard titles. Double-click the title to open the Edit Title dialog box.
Edit trend lines and view a description of the trend model. To view the trend model, hover over any part of the trend line. To edit a trend line on the web, click a trend line and hold the cursor in place, and then click the Edit menu.
Trend lines now include a Power option.
Create hierarchies by dragging one dimension onto another in the Data pane.
Set the default color property for a field.
For quantitative color legends, advanced settings are available (dates not included).
COLLABORATE WITH TABLEAU ONLINE AND TABLEAU SERVER:
Upload custom images for user profiles:
By default, users and groups now have profile images that reflect their first two initials. To help you visually distinguish between profile types, user images are circular, while group images are square. User profiles support custom images. To upload one, go to your account settings page, and click the current image or initials next to your name. If your organization uses Active Directory, default profile images come from that system. But two-letter images may briefly appear until Active Directory next synchronizes with your Tableau server.
Subscribe users in groups, and add custom messages:
To quickly subscribe several users, you can select entire groups created by your Tableau administrator. Each user in a group is subscribed independently, so the list of recipients remains fully customizable. You can also add custom messages to subscription emails, clarifying their contents. For more information, see Subscribe to Views.
Rename workbooks on Tableau Online or Tableau Server:
There's no need to republish workbooks just to rename them. Now you can rename workbooks directly on Tableau Online or Tableau Server. When you do, workbook URLs remain the same, so any links you've shared keep working. Navigate to the main Workbooks area, click the pop-up menu in the upper-right corner of a workbook, and select Rename. To rename a workbook, users need the Save permission. You'll have that by default for workbooks you own, but you might need to add it for other users. For details, see View or Edit Permission Rules in Help for Tableau site administrators.
RESOLVED ISSUES:
667919: If you used an extracted data source, calculations that referenced sets would sometimes not return updated values after the referenced sets were modified.
643719: The Compute compounded rate checkbox in the Percent difference from table calculation was incorrectly made available for certain Relative to settings.
647599: If you tried to use multiple sets with conditions that referenced each other (i.e. circular reference), Tableau Desktop would crash.
652572: Custom shapes using the path mark type would, in some cases, be distorted due to floating point number precision issues.
660091: The Parent options when editing a calculated member would sometimes be incorrectly disabled.
662897: Certain .tms files, when copied to the repository Mapsources folder, would not appear in the Background Maps dialog menu.
667093: The Page Setup dialog would appear in the upper left hand corner of your screen and it was not possible to move it.

New in Tableau 10.4.2 (Dec 13, 2017)

Resolved Issues
709447: Workbooks connected to multiple stored procedures that accepted parameters could become unresponsive.
704157: In Tableau Desktop, the drop down menu in the sign in dialog for Tableau Server did not retain server names for non-SSL enabled servers.
704817: Use of certain SAML identity providers could result in a blank sign in window when connecting to Tableau Server or Tableau Online.
706724: If one of your tables involved in a join contained a field with a user-defined, or otherwise unknown, type, attempting to create a join calculation would result in an internal error.
707684: In some cases, the dimensions of layout containers changed size after upgrading to Tableau 10.0 or higher from a prior version, causing objects in the container to disappear.
707736: Creating a local copy of a calculated field from a published data source would name the copy as Calculation_XXXXXXXXXXX if the calculated field contained user functions.
576949: When connected to a cube datasource, filter selections in Multiple Values (Custom List) filters were not shown when printing a dashboard to PDF.
693763: Extracting a table containing large strings would sometimes fail with an Error enerating sort key error for certain collations.
688320: When you selected a custom shape mark and then printed the view to PDF, the mark would not appear selected in the resulting PDF.
691782: In views with a reference line, selecting marks or legend items would update the reference line value dynamically. If you printed the view with a selection, or exported it to a PDF/image, the resulting image or PDF would not display the correct reference line value based on the selection.
687398: Adding additional files to a data source in a packaged workbook would eventually cause the workbook to fail to open with an error: Error getting archive file info (0)
599307: Workbooks based on published data sources would fail to load when there was a discrepancy in the data source folder structure between the workbook and published data source.
667000: When you opened a workbook containing sheets with Auto Update Worksheet turned off, changing to another sheet would unexpectedly cause that sheet to load.
677942: Workbooks connected live to an Excel file data source would sometimes fail to display the latest data upon opening the workbook, requiring a manual data source refresh. In those cases, even after you refreshed the data source and saved the workbook, old data would be shown if you closed and re-opened the workbook.

New in Tableau 10.4.1 (Nov 22, 2017)

683766: Updated the SQL Server ODBC driver for Tableau Desktop for Mac to resolve an issue of some tables not being listed when creating an initial data source connection.
697499: In workbooks where actions are used to navigate between sheets, story points based on multiple data sources would sometimes fail to load with a null pointer error.
647192: Using level of detail calculations could, in some cases, generate slow-running SQL queries when connected to Teradata.
668443: In some workbooks, hiding or deleting a sheet would result in an internal error.
687812: Color assignments for calculated fields based on sets would change when an older workbook was opened in Tableau Desktop 10.3 or higher.
689018: When joining two or more SAP HANA tables containing variables to a non-SAP HANA table, you could not specify variable values after joining the first SAP HANA table.
695773: When connecting to Sybase ASE, stored procedures were not listed for users who did not have SELECT permissions on tables even though they had explicit permissions to execute stored procedures.
696190: When connected to Snowflake, if you tried to change the aggregation of a boolean calculated field, an error would occur: Invalid identifiers BOOL_OR, BOOL_OR.
687344: In some cases, dashboard layout could be misaligned when opening older, existing workbooks in Tableau Desktop 10.1.8, 10.2.2, 10.3, or higher.
688953: When connecting to a web data connector based data source, if you converted a string field to a whole number and then extracted the data, the number values would be incorrect.
692551: The Dropbox and OneDrive connectors were missing if you activated Tableau Desktop using a trial.
687129: An internal error would occur if you published a data source containing multiple connections, with the Include external files option unchecked, and at least one of the connections was file-based.
675088: When you were connected to a cube data source, an internal error would occur when you tried to apply advanced table calculation settings to a view containing a filter action.
677094: An internal error would occur when you tried to edit the alias of an empty bin segment.
677361: When connected to Google BigQuery, an error would occur when you attempted to view the full underlying data if the view contained a level of detail calculation based on a converted date field: Abstract query is not defined.
678523: When you were connected to Microsoft Analysis Services, turning on grand totals and then selecting Keep Only on members of a dimension in a hierarchy would result in an error: The ANCESTOR function expects a member expression for the 1 argument. A tuple set expression was used.
686741: After editing an extracted custom SQL data source, the extract would be unexpectedly regenerated twice and white space characters would be injected into the custom SQL statement.
673477: Tableau Desktop would often become slow to respond when you duplicated a calculated field containing special characters in its name, and then used the duplicated field in a filter action.
673483: In some cases, Tableau Desktop would crash when loading a workbook containing a date filter set to filter to latest date and a data source filter.
664788: Using calculated fields involving datetime fields that had been converted to date would, in some cases, result in an error: ColumnTable: Schema/DataTable mismatch.
665078: When you edited an axis in a dual axis view, the opposite axis from the one intended would sometimes be modified.
658121: When connecting to Oracle Eloqua on a Mac, dates would sometimes be returned as null.

New in Tableau 10.4.0 (Sep 26, 2017)

Connect to and Prepare Data:
Certified and recommended data sources
New Denodo connector
Other Databases (ODBC) connector on the Mac
Oracle connector supports SSL
SAP GUI 7.4 support
Create an SAP BW extract without a special license
Design Views and Analyze Data:
Precise dashboard spacing, with border and background color controls
High DPI support for Windows
Support for linear geometries
Map data updates and additions
MATLAB integration
WCAG-conformant drop-down filters in embedded views
New in Web Authoring:
Turn on the View Toolbar on the web
Edit groups on the web
Create aliases on the web
Format lines
Share and Collaborate:
Enhanced commenting on Tableau Server and Tableau Online
Learn who has seen a view on Tableau Server and Tableau Online
Resolved issues:
632304: Updated some postcodes in the Netherlands (9939, 9629, 1114, 1115).
634746: Totals for a calculated field containing a sub-expression that matches the formula for another calculated field could incorrectly inherit Total Using settings.
636185: When connected to a large Excel file, and viewing Data Interpreter results, an error could sometimes occur: We found a problem with some content.
639047: When you connected to SAP HANA attribute views, technical column names would be displayed instead of friendly column labels.
639769: When a combined field was used in a view with colors and grand totals, the colors would apply to the totals even when Include Totals was unchecked in the Edit Colors dialog.
650687: When you were connected to a cube data source, adding values to a string parameter using the Add from Field button did not correctly add the values.
658151: In some cases, actions used to navigate between dashboards stopped working after upgrading to Tableau 10.3 or higher.
659150: Some Marketo DATETIME fields were brought into Tableau Desktop as DATE fields and you could not properly convert it to a Date & Time type.
660300: Connecting to some shapefiles would fail in Tableau 10.3 or higher, when they used to work in previous versions.
662675: SAP BW extract refreshes could sometimes fail with a no such table error.
615320: In workbooks connected to multiple published data sources, it was not possible to correctly reference parameters from secondary data sources in a calculated field due to internal parameter naming collisions.
666716: Color palette assignments for ad-hoc clusters were not retained when saving and re-opening a workbook.
616539: Colors assigned to an ad-hoc calculated field would often fail to persist after saving and re-opening a workbook, publishing to Tableau Server, or sometimes even after refreshing a view.
622187: Edited size legend titles in bar chart views would revert to the default title when the sheet was printed or exported to PDF.
628172: Dimension member aliases containing a line break character could not be used to filter the view.
631074: Added support for DATETIME fields when connected to Google BigQuery.
631423: When you selected multiple forecast marks from multiple measures and viewed the underlying data, only values from one measure would be displayed in the summary tab.
613724: Opening older workbooks containing the MAKEDATETIME() function in calculations could result in an error: Mismatched case result types

New in Tableau 10.3.3 (Sep 20, 2017)

Resolved Issues:
686481: Connections to Excel files saved in Excel version 1707 would fail with an error: Errors occurred while loading the data source.
643218: SAML authentication from Tableau Desktop to Tableau Server would fail in some environments.
652691: With recent updates to the Amazon Redshift driver, connections could fail with a no pg_hba.conf entry for host error. A workaround was to republish workbooks or data sources with Require SSL checked in the data connection.
677500: Extracts would unexpectedly refresh when you switched between the Data Source tab and a sheet tab.
666924: When source and target sheets were based on different data sources, filter actions failed to trigger sheet navigation when the action was set up to use selected fields.
670276: An internal error would occur, in some cases, when you attempted to sort a calculated field containing conditional statements.
671192: When you were connected to Snowflake and cast a string dimension to an integer or float, a Numeric value is not recognized error would occur.
671236: Query execution errors would occur when you connected to Cloudera Impala using custom SQL with a date parameter.
655498: When you saved a workbook in presentation mode and then re-opened the workbook, the view would not be correctly centered.
659319: When connected to a data source using custom SQL, if you changed the data type of a field and then created an extract or saved the workbook, extra line feed characters would be injected into the custom SQL query.
660780: In certain cases involving parameter-based calculated fields used as filters, incorrect or inefficient SQL queries would be generated when connected to Google BigQuery, Apache Drill, or Amazon Redshift, resulting in error or poor performance.
664031: In some cases, when you joined multiple tables and performed a pivot, null values would incorrectly appear in Pivot Field Names.
665085: An internal error would occur when you renamed a sheet and then tried to use the controls on the Pages shelf in the sheet.
673768: Printing to PDF was noticeably slower in Tableau Desktop 10.0 and higher compared to prior versions.
677755: When the filmstrip was used to navigate between sheets in a workbook, interactions in sheets would cause Tableau Desktop to gradually consume more memory and eventually crash.
647710: In some cases, aggregated calculated fields would return no data after an extract was created.
649008: When you connected to MySQL, case-sensitive table collation was ignored when custom SQL was used. Custom SQL connections to MySQL now default to database collation.
634535: In some European locales, double-precision numbers were returned as #ERROR or null.

New in Tableau 10.3.2 (Aug 4, 2017)

Resolved issues:
627874: 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.
636727: At smaller display resolutions, the publish workbook dialog could be cut off and you would not be able to click the Publish button.
670693: Extracts on Tableau Server with hidden columns could sometimes be unhidden during an extract refresh.
657412: The Sort by Field option was not available when you were connected to Apache Drill.
658203: When attempting to connect to Spark SQL, an internal error would sometimes occur.
650235: 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.
650906: When connected to Oracle Essbase, changing a filter applied to selected worksheets would result in an internal error in some cases.
652952: 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.
653656: 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.
657211: 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.
628226: 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.
644857: An internal error would sometimes occur when the Force y-intercept to zero trend line option was used.
644867: A typically benign error, Failed to load proxy credentials: 'The parameter is incorrect.' showed up excessively in log files, making troubleshooting difficult.
645994: Tableau Desktop for Mac would sometimes quit unexpectedly when publishing a data source to Tableau Online.
648994: Aggregated boolean calculations would return False for totals even when only True records existed and the aggregate form was also True.
649592: When you extracted a data source with string fields containing nulls, and converted to an integer, the nulls would be changed to zeros.
593217: Performing a union of Excel sheets could sometimes result in incorrect measure values.
611763: Connecting to a local cube file (.cub) would fail inconsistently with various errors.
640956: Published extracts based on Custom SQL could not be refreshed using the Data Extract Command Line Utility or the Online Sync Client (Tableau Bridge).
532425: 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.
598585: 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.
612687: 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.
632697: Tableau Desktop sometimes became unresponsive when using multiple parameters with a data source based on a stored procedure.
636433: 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.
638250: In some cases, colors assigned based on a calculated field did not persist when closing and reopening a workbook.
643843: An intermittent crash would occur, when creating a connection to Google Analytics, if dimensions and measures were selected too quickly.
649063: In some cases, extracting a published data source would unhide hidden fields in the data pane.

New in Tableau 10.3.1 (Jun 22, 2017)

New in Tableau 10.3 (Jun 1, 2017)

Help Redesign:
Combined help system
Starting with version 10.3, Tableau Desktop Help is now known as Tableau Help. Tableau Help contains all help topics related to analyzing and consuming data in Tableau Desktop, Tableau Server, and Tableau Online. This help is for people who create workbooks or data sources and publish them, and for people who want to see, interact with, and share views in Tableau.
We welcome your feedback on this change, as well as any feedback or ideas you might have on how to make our content better. Please use the feedback bar on the top of any page ("Was this page helpful?") to open the comment field and submit your feedback.
Using Tableau on the Web provides links to the topics that used to be located in Tableau Server and Tableau Online help.
Connect to and Prepare Data
Connect to .pdf files
Now you can use the PDF File connector to connect to tables in your .pdf files. For more information, see PDF File.
Union even more data
You can union tables from a .pdf file as well as Aster Database, Cloudera Hadoop, Hortonworks Hadoop, IBM DB2, IBM PDA (Netezza), Pivotal Greenplum Database, SAP Sybase ASE, SAP Sybase IQ, and Teradata. For more information about union, see Union Your Data.
Recommended tables and joins
When you’re setting up your Tableau data source or modifying an existing one, it can be helpful to see what tables are popular with other people at your organization. So when you connect to a database while simultaneously signed in to Tableau Server (from Tableau Desktop), in the left pane a Recommended list shows the tables used most often in data sources and workbooks published to Tableau Server.
After you add a recommended table to the canvas, others tables that are frequently joined to it appear in the Recommended list. Double-click one to automatically create a recommended join between the tables, using the most popular fields and join type by default. Note: If foreign keys are specified in the database, they override the recommended joins.
Recommended tables and joins are supported for a subset of connectors. For more information, see About Recommended tables and joins.
New connectors
New Amazon Athena connector
Use the Amazon Athena connector to connect to Amazon Athena data. For more information, see Amazon Athena.
New Dropbox connector
Use the Dropbox connector to connect data on Dropbox. For more information, see Dropbox.
New MongoDB BI connector
Use the MongoDB BI connector to connect to MongoDB BI data. For more information, see MongoDB BI.
New OneDrive connector
Use the OneDrive connector to connect to data on OneDrive. For more information, see OneDrive
New ServiceNow ITSM connector
Use the ServiceNow ITSM connector to connect to ServiceNow ITSM data. For more information, see ServiceNow ITSM.
JSON schema updates
Tableau scans the data in the first 10,000 rows of the JSON file and infers the schema from that process. Sometimes, more fields exist in rows that were not scanned to create the inferred schema. Now, Tableau indicates when additional fields are detected that you may want to include in your analysis. For more information, see JSON File.
Design Views and Analyze Data
Double-click to zoom
In prior releases, when you double-clicked on a view that used continuous measures for both the X and Y axis (also known as quantitative/quantitative views, for example scatter plots) and the View toolbar was turned off, Tableau would automatically zoom in.
This resulted in a confusing user experience. Now for these quantitative/quantitative non-map view types, Tableau no longer zooms in by default when you double-click on the view. This change applies to new workbooks and upgraded workbooks. The double-click to zoom functionality is also turned off by default for table and cross-tab chart types.
Tooltip selection
This feature enables you to select similar marks in a view from the tooltip by category. Any discrete dimension or measure that is included in the tooltip becomes an active link that you can click on to select other marks in the view that have the same value.
This feature works on Tableau Desktop, Tableau Server and Tableau Mobile. It is turned on by default for new worksheets and turned off by default for upgraded worksheets. To turn the feature off or on, at the worksheet level click Tooltip on the marks card to open the Edit Tooltip dialog box, and then clear or select the Allow selection by category check box.
For more information, see Tooltips.
Latest date presets for discrete date filters
Discrete date filters can be set to filter to the latest date value in the data source. You can use this setting to ensure that the most recent date in the data source is selected in the filter. For details, see Latest Date Preset for "Filter Discrete Dates" under "Filter Dates" (Desktop) in Filter Data from Your Views.
On Tableau Server and Tableau Online, presets are applied when the view first loads in the browser, but not when the browser or data is refreshed.
Apply table calculation filters to totals
When you show totals and you want a table calculation filter to apply to the totals, you can now select Apply to totals in the drop-down menu for that filter (on the Filters shelf). This option lets you decide when a table calculation filter should be applied to totals. For details, see "Filter table calculations" in Filter Data from Your Views.
Map data updates and additions
The following data has been updated for Tableau version 10.3:
French region names were updated to the final 2016 naming scheme.
NUTS (Nomenclature of Territorial Units for Statistics) codes and Airport codes no longer require country as a parent to geocode on a map.
Netherlands landen and provincies were updated.
Australian LGAs were updated with 2016 data.
Additionally, Rwanda districts (uturere) are now supported by Tableau, and can be geocoded using the County geographic role. Polygons for New Zealand postcodes were also added. For more information about additional map data supported by Tableau, see What data does Tableau support for building map views.
Evenly distribute a layout container's items
After you add a layout container to a dashboard, you can make the items it contains evenly spaced using the Distribute Evenly command (on the desktop and in web authoring). For details, see Size and Lay Out Your Dashboard.
Easy access to story actions
The new story toolbar appears when you mouse-over the story navigation area. Use it to revert story changes, apply updates to a story point, delete a story point, or create a new story point out of the current, customized one.
Use numbers for story navigation
The story Layout tab includes a new navigation option: Numbers. Use this option to make the story navigator display a sequence of numbers instead of caption boxes or dots. For details, see Create a Story.
New to Web Authoring
Web authoring topics for Tableau Server and Tableau Online are now located in Tableau Help, starting with version 10.3. To see web authoring features from past releases, see What's New in Tableau Server.
Edit quantitative color legends
You can now edit the color palette for continuous color legends in web authoring. You can open the Edit Colors dialog box from the Marks card or by clicking the drop-down arrow on the legend.
You can also set a custom color for the start and end colors by entering the Hex value.
Edit colors on separated legends
When you create separate color legends for measures in your view, you are no longer restricted to using only the default color palette or the color palette assigned to each color legend when the view was published from Tableau Desktop.
In web authoring mode, you can now select different color palettes for each legend. Click the drop-down arrow on the legend to open the Edit Colors dialog box and then select the color palette. You can also set custom start and end colors using Hex values.
Customize how people interact with your map
In web authoring mode, you can now customize how your audience interacts with your map view in the following ways using the Map Options dialog box:
Show a map scale
Hide map search
Hide the view toolbar
Turn off pan and zoom
For more information, see Customize How People Interact with your Map.
Format numbers on the web
You can now specify basic number formatting for measures in the view on Tableau Server and Tableau Online. For more information, see Format Numbers and Null Values on Tableau Server or Tableau Online.
Format lines
When you are authoring on the web, you can quickly change all the lines in your workbook. Select Format > Workbook, then expand the Lines section on the Format Workbook and make your selections. For more information, see Format at the Workbook Level.
Create stories
In web authoring, you can now create a story to tell a data narrative, provide context, demonstrate how decisions relate to outcomes, or to simply make a compelling case. See Create a Story for details.
Create and edit bins
Create bins from continuous measures and edit them in Tableau Server and Tableau Online, similar to how you do it in Tableau Desktop. For details, see Create Bins from a Continuous Measure.
Drag fields to Show Me in the view
Select and drag dimensions and measures of interest to the view area. A "Show Me" view is automatically created. You can then click other Show Me options to try different view types.
Drill up and down a continuous hierarchy in the view
In a view with a continuous hierarchy, hover near the headers on a continuous axis to display the + and - controls. Click to drill down or up.
Save data source
You now have the option to save a data source that is embedded with a published workbook, as a separate, published data source on Tableau Server and Tableau Online that other users can connect to. When you save the data source, you can choose to update the workbook to connect to the newly saved data source.
Share and Collaborate
Data-driven alerts from Tableau Server
When data reaches important thresholds for your business, data-driven alerts automatically send email notifications to key people you specify. You can set alerts on all chart types except Gantt charts and maps.
To begin, select a continuous numeric axis of a chart.
Then click Alert in the toolbar.
When the Create Alert pop-up window appears, set the data condition and threshold value that triggers alert emails. In the view, a red line shows where the threshold falls relative to current data. Simply specify the email subject line, schedule, and recipients to start alerting your organization about critical metrics.
To manage alerts you own or receive, click your name at the top right corner of a Tableau Server page, click My Content, and then click Alerts.
Resolved Issues:
In some cases, opening a workbook connected to Amazon Redshift would fail with a No such column error.
Appending data from a file to an extract created from a file-based data source would fail with an error.
When connected to Google BigQuery, custom SQL statements containing tab or carriage return characters would fail to execute with a parse error.
In some cases when a dimension is used as a filter, values from INCLUDE and EXCLUDE level of detail calculations did not sort or total correctly.
Excess Kurtosis summary data was not calculated correctly for some data sets.
Using the Tableau Data Extract Command-Line Utility to refresh a published extract, based on a local text file, would fail with errors.
When you show totals in the view and you want a table calculation filter to apply to the totals, you can now select Apply to totals in the drop-down menu for that filter (on the Filters shelf). This option lets you decide when a table calculation filter should be applied to totals.
When you exported a very large crosstab to Excel in Tableau Server, a Session Ended by Server error could occur due to resource exhaustion. Tableau Server now warns that the export is too large and will not permit the export.
In the Open workbook from Tableau Server dialog, you could select a workbook to be opened but the selection sometimes would not be highlighted.
Size legends would appear unexpectedly and show 'Null' when all values were filtered out in some views.
The order of parameters in the Edit Reference Line, Band, or Box dialog did not remain consistent.
Corrected map polygons for Florida zip codes 33556 and 33147.
When you filtered a view using a group, the view would sometimes become blank after modifying and applying the filter.
When using map small multiples, custom polygons could sometimes overlap between the separate map panes.
Opening older workbooks connected to SAS files would sometimes fail with Cannot get modification time of non-existent path errors.
When you used a calculated field, containing an INCLUDE or EXCLUDE level of detail expression, as a filter and selected All Values, the field would either become invalid or the view would not get filtered correctly.
Corrected the border for the province of Zeeland in the Netherlands.
In some scenarios, involving calculated fields or sets based on a user filter, changing the user did not refresh the view to show data based on the newly selected user.

New in Tableau 10.2.2 (May 12, 2017)

Resolved Issues:
When connected to Hortonworks Hadoop Hive, calculations containing the DATEADD function would return null values when they did not in prior versions.
In some workbooks, refreshing the view would cause the view to go blank due to filter selections becoming deselected.
Workbooks created in Tableau 10.1.3, 10.1.4, 10.1.5, and 10.1.6, that connected to Splunk, could not be opened in other newer versions of Tableau Desktop.
When using an Other Databases (ODBC) connection the list of available tables would disappear, and need to be reloaded, after any table was added to the join canvas.
Exported summary data for some views appeared to be rounded incorrectly when compared to the values shown in Tableau Desktop.
Creating an extract of a data source containing a union of text files joined to another text file would fail with an error.
Tableau Desktop would sometimes crash when utilizing geometry fields containing null values.
When you attempted to join Google BigQuery tables containing identically named columns, but with different letter casing, a Duplicate column names in the result are not supported error would occur.
Restored the Microsoft Azure HDInsight Service authentication option to Hive-based connectors.
In some cases, data based on a pivoted field would return null where non-null values were returned prior to Tableau 10.2.
Some extracts, created using the Tableau SDK, would cause Tableau Desktop for Mac to crash when connecting to the extract.
When editing an extracted file-based data source in a packaged workbook, a file not found error would occur and no option to locate the underlying data source file would be presented.
Workbooks connected to HANA via single sign on would incorrectly prompt for credentials when loaded.
Updated Firebird components to version 2.5.6.
Formatting text in a sheet on dashboard would sometimes cause text in other sheets on the dashboard to shift unexpectedly.
Workbooks connected to published data sources, containing parameters with large numbers of selections, loaded considerably slower than equivalent workbooks using embedded data sources.
When connected to Exasol in Tableau Desktop, TIMESTAMP WITH LOCAL TIME ZONE fields were not visible.
Updated psqlODBC drivers to version 09.06.0200. This version includes an updated version of OpenSSL 1.0.2k.
Refreshing a published, Snowflake connection based extract, using the Tableau Data Extract Command Line utility, would fail with a There is no active connection to the data source error.

New in Tableau 10.2.1 (Apr 6, 2017)

New in Tableau 10.2 (Mar 1, 2017)

Tableau Desktop:
In some cases, when you were connected to an SAP HANA calculation view, attempting to preview or extract the data, or adding fields to the view, would result in a "441 this feature has been deprecated and will be removed in next release" error from which you could not proceed. Attempting the action again or refreshing the view would often succeed.
When you created a group using a combined field, a "collation retrieval requires query" error would occur in various ways that could make the workbook unusable.
When you connected to a JSON file with a top-level array of values, an internal error would occur.
Re-introduced the Temperature Diverging color palette.
When connected to Presto, date and datetime field values are now returned using the UTC time zone by default. Previously, the timezone was determined by your operating system's local timezone.
PDFs generated by printing or downloading a workbook to PDF would sometimes include extra lines that appeared to be graphical artifacts.
When connected to Oracle using custom SQL, adding a Top N, IN/OUT set to the view would result in a query that ran indefinitely.
Tableau Server:
When you created a group using a combined field, a "collation retrieval requires query" error would occur in various ways that could make the workbook unusable.
In workbooks containing global filters, filter selections would disappear, in some cases, when the workbook was published to Tableau Server or Tableau Online.
Generating a performance recording would fail when Tableau Server was accessed through an SSL termination proxy or external load balancer.
PDFs generated by printing or downloading a workbook to PDF would sometimes include extra lines that appeared to be graphical artifacts.
Tableau Server did not respect custom delimiters in URL actions with multiple values allowed when FILTERVALUES was defined in the URL.
When web authoring a workbook with a large number of data sources and fields, a scroll bar would not appear in the data pane making it impossible to access all the fields and data sources.
You could not sign into Tableau Server when Tableau Server was configured for OpenID authentication using Salesforce as the identity provider.

New in Tableau 10.1.5 (Feb 16, 2017)

Tableau Desktop:
When connected to Vertica, attempting to use the DATEPART function within a DATEADD function in a calculated field would result in Vertica error 4286.
Tableau Desktop would crash unexpectedly when connecting to a Progress OpenEdge synonym.
Unchecking "Show Header" for a dimension belonging to a hierarchy could make it impossible to expand the hierarchy, within the view, using the expand and collapse buttons in the dimension headers.
In some cases, your Preferences.tps file can have unexpected character encoding resulting in invalid custom color palettes. Tableau Desktop would crash when you attempted to select on of these invalid color palettes in the Edit Colors dialog.
Filter actions being used as "reset" buttons in previous versions, failed to clear selections and reset the view after upgrading to Tableau 10.1.
Opening workbooks containing duplicated Oracle Essbase connections would fail with an invalid username and password error.
In some cases, Tableau Desktop would repeatedly prompt for Tableau Online credentials after a period of idle time and would not successfully reconnect without closing Tableau Desktop and launching it again.
In some cases, attempting to replace a published data source with a local copy of the same data source would result in an error stating that a data source with the same name already exists.
When you refreshed a live, generic ODBC data connection, cached, existing data would be returned instead of any new data.
After upgrading to Tableau 10.0 or higher from a previous version, performance when loading some workbooks containing data sources with a large number of joined tables was noticeably slower.
Tableau Server:
The My Content and My Account Settings pages failed to load if your username contained special characters.
Custom sign in logos would revert to the default Tableau logo when you embedded a view in an iframe.
In workbooks published with prompt user authentication, creating a custom view in Tableau Server and then switching back to the original view would result in an unexpected error.
In environments where outbound traffic requires proxy authentication, attempting to register Tableau Server would cause the process to crash.
Tooltips would often show data from previous story points when navigating between story points in Tableau Server.
When web authoring a workbook connected to a published ODBC data source, you could not add an aggregated measure to the view.
Intermittent "LogicException" internal errors would occur when viewing published workbooks.
When you ran the "tabadmin backup -v" command repeatedly and frequently (e.g. once every hour), a "duplicate key value violates unique constraint" error would occur intermittently and the backup would fail.
In some cases, Data Server and Data Engine processes would frequently be down and cause views to fail to load. A server restart was typically required to bring the processes back up.
Long site names could sometimes be truncated in the "Select a Site" menu after signing into Tableau Server.
In some cases, mark labels would appear cut off when viewing your published workbook in a browser.
The Stats for Space Usage administrative view did not handle multiple sites correctly and would fail to load when you clicked the "Go to {user}" actions in tooltips.
In certain environments, restoring a Tableau Server backup would fail with an error: "Exception during sos data restore: java.lang.IllegalArgumentException: MALFORMED"
In certain environments, restoring a Tableau Server backup would fail with an error: "Exception during sos data restore: java.lang.IllegalArgumentException: MALFORMED"

New in Tableau 10.1.4 (Jan 25, 2017)

Tableau Desktop:
When connected to a SAS statistical file, IS8601DA10 formatted date fields were not correctly recognized and could not be converted to a different data type.
Tableau Desktop would sometimes crash on Macs running macOS Sierra with integrated Intel graphics.
When you created a cross-database join involving a table with a back slash in its name, a Tableau Data Engine error would occur.
In some cases, certain calculated fields materialized in an extract prior to Tableau 10.0 could return more domain values than actually existed in the domain of the field when queried in Tableau 10.0 or newer.
In some cases, when you edited a calculated field that was being used on Color, marks would lose their color and turn white or black.
When you added a worker with backup Data Engine and Repository processes, scheduled extract refreshes would sometimes fail until the File Store on the worker finished synchronizing.
It was not possible to union comma-delimited text files in locales where commas are used as decimal separators (e.g. German).
Running filter actions could sometimes be significantly slower when compared to prior versions.
In some cases, deselecting filter actions did not behave as expected.
In some cases, excluding a mark more than once could change an associated filter from an include filter to an exclude filter.
In some cases, opening a workbook created in Tableau 9.1 in a newer version of Tableau Desktop would result in an internal error.
When connected to Google BigQuery, converting a string, containing a decimal character, to FLOAT would result in a "Bad int64 value" error.
In the data source canvas, replacing an SAP HANA table with another table containing a special character in its name would result in an internal error.
When using the Refresh All Extracts functionality in Tableau Desktop, you would be prompted to enter a username and password for data sources that did not require credentials. Refreshes would still proceed and succeed if you canceled the unexpected prompts.
Small decimals would sometimes appear as "null" in the data preview pane or show "#Error" when added to a view.
Updated Google BigQuery connections to utilize the REGEXP_CONTAINS function when REGEXP_MATCH is called.
When connected to Microsoft Analysis Services, running a filter actions would sometimes cause Tableau Desktop to become unresponsive.
Copying data from Tableau Desktop or exporting data from Tableau Server could multiply some decimal values by a factor of ten billion in the resulting data.
In some scenarios, involving cross-database joins and level of detail calculations, an "Unable to materialize temporary table" error would occur when you added a field to the view.
Specifying a negative value for number of decimals in the ROUND() function would cause Tableau Desktop and Tableau Server VizQL processes to error and crash.
Tableau Server:
Specifying a negative value for number of decimals in the ROUND() function would cause Tableau Desktop and Tableau Server VizQL processes to error and crash.
Scheduled extract refreshes for workbooks containing extracts and at least one published, SSO-authenticated or user-delegated, live data source would fail with an error: "Cannot evaluate user filter; no current user or group"
Queries generated by published Exasol data sources could sometimes be significantly less efficient than those generated when using an equivalent live connection in Tableau Desktop.
It was not possible to add a tenth worker node (i.e. 1 primary + 10 workers) when configuring Tableau Server.
In workbooks connected to an SAP BW data source, dimension member aliases would sometimes become mixed up when the workbook was loaded in Tableau Server.
Scheduled extract refreshes for workbooks containing both extracted SAP HANA connections and live, SSO-authenticated SAP HANA connections would fail.
Running filter actions could sometimes be significantly slower when compared to prior versions.
URL actions in the Traffic to Views and Traffic to Data Sources administrative views did not handle sites correctly, resulting in "That page could not be accessed." errors.
Importing a Tableau Server 9.3 site into Tableau Server 10.1, using the tabadmin importsite command, would fail with an error.
Type-in parameter font formatting did not match what was specified in Tableau Desktop when viewed in a browser and could sometimes result in white text on a white background.
Using web authoring to edit a workbook containing a global filter would result in an internal error and prevent editing of the workbook.
Vizqlserver processes would intermittently crash when loading certain workbooks if the vizqlserver.querylimit setting value was exceeded.
Copying data from Tableau Desktop or exporting data from Tableau Server could multiply some decimal values by a factor of ten billion in the resulting data.

New in Tableau 10.1.3 (Dec 29, 2016)

New in Tableau 10.1.2 (Dec 21, 2016)

Tableau Desktop:
585085 - In Tableau Desktop for Windows, printing multiple sheets to PDF, using the "Selected sheets" option, would only print a single sheet from the selection.
576384 - Tableau Desktop would often crash using when you attempted to edit a large, complex data source.
576925 - Some calculated fields, containing user functions (e.g. ISMEMBEROF), would result in a "no such column" error when used in a published data source.
578374 - In Turkish locale environments, Google Analytics dimensions would seemingly randomly fail to appear in Tableau Desktop even though they could be selected when initially connecting.
587163 - When you used a date hierarchy, based on a datetime field, in Tableau Desktop, it was not possible to drill back up from the day level to the week level.
578531 - If you attempted to sign into a different Tableau Server site in Tableau Desktop, when Tableau Server was configured to use a non-standard port, an error would sometimes occur or you would see a blank sign in dialog.
454096 - Loading some workbooks connected to Teradata, and containing a large number of complex calculated fields, was noticeably slower when upgrading from an older version to Tableau 9.0 or higher.
579496 - Publishing to a Tableau Server configured to use a non-standard port would fail with an error. In some cases, attempting to publish a second time would succeed.
579509 - When you ran a filter action on hover from a hidden sheet, targeting a dashboard, Tableau Desktop would quit unexpectedly.
540561 - Query performance could sometimes be slow when you were connected to an Exasol data source due to incorrect reporting of null columns.
580719 - Tableau Desktop would often crash when you attempted to edit a large, complex data source.
547206 - When connected to a Hive-based data source and filtering a view using discrete, exact dates, the view would not show any data.
560077 - When connected to Cloudera Impala, certain parameter-based date calculations failed to return data when expected.
583428 - Updated Curl to version 7.51.0.
572502 - Tableau Data Extract query performance was noticeably slower, in some cases, after upgrading from Tableau 9.3 to 10.0 or higher.
585085 - In Tableau Desktop for Windows, printing multiple sheets to PDF, using the "Selected sheets" option, would only print a single sheet from the selection.
585085 - In Tableau Desktop for Windows, printing multiple sheets to PDF, using the "Selected sheets" option, would only print a single sheet from the selection.
581762 - When you downloaded a published workbook and opened it in Tableau Desktop, or opened a published workbook directly in Tableau Desktop (e.g. Server > Open Workbook), an error would occur: "element 'layout-options' is not allowed for content model"
573220 - In some older workbooks opened in Tableau Desktop 10.0 or higher, when you edited the server and site path for a published data source to point it to an identical data source on another server, an error would occur: "This workbook contains a datasource that is dependent on a different
Tableau Server. Multiple Tableau Server connections are not supported"
586404 - Calculated fields using the DATEADD function, with the week date part and a level of detail calculation as arguments, returned unexpected results.
580719 - Tableau Desktop would often crash when you attempted to edit a large, complex data source.
574013 - Adding additional fields to a SAS data file stored in a network folder, and then attempting to use the new fields in Tableau Desktop, would often result in a "no such column" error.
581762 - When you downloaded a published workbook and opened it in Tableau Desktop, or opened a published workbook directly in Tableau Desktop (e.g. Server > Open Workbook), an error would occur: "element 'layout-options' is not allowed for content model"
587693 - When connected live to a Presto data source, some DATEDIFF function based calculations did not return the expected results.
Tableau Server:
582130 - Some workbooks containing date calculations, and connected live to Google BigQuery, would fail to load with an "Incorrect data type" error.
575935 - Tableau Server Data Server processes would sometimes crash when extract-based data sources were utilized.
591589 - When you had an OpenID authenticated Tableau Server, URL parameter filters would get stripped when loading embedded views.
576211 - When a view was accessed via a filter action, in a workbook with sheets shown as tabs, an access view event was not logged in the Tableau Server historical_events table. The access view event would be correctly logged when a view was accessed manually by selecting its sheet tab.
585668 - In some cases, large, long-running scheduled extract refreshes would fail with an error: "Error: 40636: UploadOpen: error creating file"
582540 - When installing Tableau Server 10.0, and the backup of the existing server failed, the installer failed to abort and would incorrectly continue with the installation.
586829 - In some Tableau Server environments configured for high availability, File Store processes would appear to be constantly synchronizing.
454096 - Loading some workbooks connected to Teradata, and containing a large number of complex calculated fields, was noticeably slower when upgrading from an older version to Tableau 9.0 or higher.
581406 - When you loaded web authoring embedded in an iframe, and then saved your work, the view would reload with the full Tableau Server interface shown in the iframe instead of the expected embedded view interface.
564733 - Turning off SAML authentication for Tableau Desktop connections to Tableau Server, using the "tabadmin wgserver.authentication.desktop_nosaml false" command, did not work as expected.
583428 - Updated Curl to version 7.51.0.
572502 - Tableau Data Extract query performance was noticeably slower, in some cases, after upgrading from Tableau 9.3 to 10.0 or higher.
585668 - In some cases, large, long-running scheduled extract refreshes would fail with an error: "Error: 40636: UploadOpen: error creating file"
586412 - In some cases, when viewing an embedded view with multiple sheet tabs on a mobile device, if you rotated the device from landscape to portrait orientation, or vice-versa, an unexpected error would occur.
575220 - In Tableau Server, if refreshing a Microsoft Access based extract failed for any reason, the file lock on the Access file would not be released. Successful extract refreshes correctly release the file lock.

New in Tableau 10.1.1 (Nov 7, 2016)

New in Tableau 10.1 (Nov 2, 2016)

Corrected Issues:
Tableau Desktop:
Corrected coordinates for the Japanese city of Nagano.
When a sheet name contained a '%' character, and the sheet contained highlighting, an error or crash would occur when interacting with the sheet in Tableau Desktop.
In some views with colored marks, and column or row grand totals shown, filtering out all mark values resulted in an error: "No such column [system:visual].[is_mark_total]"
In some cases, when the Tableau Online Sync Client is set to run continuously, pressing the 'Run Now' icon to trigger a refresh for a data source appeared to have no effect. This was especially the case when attempted immediately after logging into Windows.
In Tableau Desktop, when you right clicked a scroll bar in a view and selected 'Scroll Here', the scroll bar position would change but the view did not scroll.
Incorrectly labeled "Opacity" as "Transparency slider".
In some cases, showing a filter in a view would cause Tableau Desktop to crash unexpectedly.
Corrected the locations of the following Florida zip codes: 33037, 33040, 33050
When joining tables to create a data source in Tableau Desktop, if you added an extract filter and then added an additional table to the join, the extract filter would be removed with no warning.
Selecting packed bubbles from Show Me did not default to the correct stack marks setting.
In Tableau Desktop, if you scrolled a view, and then navigated between views via filter action, the scrolled views could sometimes become distorted.
When you copied a sheet containing a boolean parameter with aliases to another workbook, the parameter would sometimes get into a non-functional state in the target workbook.
Corrected the filled map shape for the 83544 zip code.
Tableau Desktop would automatically regenerate hierarchies when you connected to a published data source, even if the hierarchies had been explicitly removed when the data source was published.
Connecting to an R data file in Tableau Desktop could sometimes take significantly longer than an equivalent CSV file.
Corrected the filled map shape for Hong Kong.
Adding a sheet with a thicker row border to a vertical layout container would cause a scroll bar to appear in the sheet even if there was plenty of space in the container to display the sheet content.
Tableau Server:
In some cases, after closing out of web authoring in Tableau Server, you would see a blank page with a number of question marks.
In Tableau Server 10.0 and Tableau Online, it was no longer possible to collapse and hide the upper navigation toolbar in the browser interface.
Tableau Server subscription emails, for some workbooks, would show blank white space where filters were expected.
Text in tooltips for Tableau Server is not selectable and can not be copied and pasted elsewhere.
Custom number formatting for certain numeric values would not be retained in tooltips when viewed in Tableau Server.
Running a subscription schedule using the 'tabcmd runschedule' command would fail if you ran it as a site administrator.
When using web authoring in Tableau Server, if you created a new sheet in a workbook and then let your user session expire without taking any further action, an unknown server error would occur when you tried to resume work.
Tableau Online:
In Tableau Server 10.0 and Tableau Online, it was no longer possible to collapse and hide the upper navigation toolbar in the browser interface.
Tableau Mobile:
The Tableau Mobile app could not connect to a SAML-enabled Tableau Server using Microsoft ADFS as the identity provider and NTLM as the authentication mechanism.

New in Tableau 10.0.2 (Oct 12, 2016)

Tableau Desktop:
When you were connected to Presto in Tableau Desktop, using a fixed level of detail calculation sometimes resulted in a query error.
When you replaced references for a parameter in Tableau Desktop, some calculated field formulas did not correctly update with the new parameter.
In Tableau Desktop, it was not possible to enter Chinese, Japanese, or Korean text via IME into filter search boxes.
In some cases, when the Tableau Online Sync Client is set to run continuously, pressing the 'Run Now' icon to trigger a refresh for a data source appeared to have no effect. This was especially the case when attempted immediately after logging into Windows.
Tableau Desktop would often crash when you attempted to edit a large, complex data source. ( | 9.3.6)
When you connected to Progress OpenEdge in Tableau Desktop, joining tables would result in an internal error.
Incrementally refreshing a Google Analytics extract daily would only add new data to the extract every other day.
Some published extract data sources, created using the Other Databases (ODBC) connection option, would fail with a syntax error when refreshed from Tableau Desktop, the data extract command-line utility, or the Tableau Online Sync Client.
In some workbooks connected to Oracle Essbase, row headers were not displayed after upgrading to Tableau 9.3 or higher.
Loading certain workbooks, containing table calculations, could cause total consumption of system memory.
In workbooks connected to Oracle Essbase, and created prior to Tableau 9.3, existing filter conditions would be removed when the workbook was opened in Tableau Desktop 9.3 or higher.
Workbooks connected to OLAP cube data sources would sometimes appear to hang when executing queries and fail to load.
For published extract data sources based on R data files, refreshing an extract would fail with an error when you used the Tableau Data Extract Command-Line Utility: "There is no active connection to the data source"
Tableau Desktop would sometimes crash under certain network conditions that result in slow SSL root certificate lookups.
Tableau Server:
URL encoding for the "+" symbol was not properly handled when accessing Tableau Server content using tabcmd.
When you clicked the Export Metadata File button in the SAML tab of the Configure Tableau Server dialog, the resultant XML file was malformed. A workaround was published at http://kb.tableau.com/articles/issue/saml-metadata-xml-file-exported-fro....
When you loaded views in Tableau Server, a "union: type mismatch" error would intermittently occur.
In some environments, Tableau Server processes would send an unusually large number of HTTP requests to a licensing related URL.
In some workbooks published to Tableau Server, when you navigated to a dashboard via a filter action, some sheets in the dashboard would fail to load.
When you loaded views in Tableau Server, a "union: type mismatch" error would intermittently occur.
After publishing a workbook to Tableau Server, date range slider filters would display date and time for the start and end values even though the filter was set to only display date.
Alert tooltips would sometimes appear blank in Tableau Server after a data source extract refresh.
Incrementally refreshing a Google Analytics extract daily would only add new data to the extract every other day.
Loading certain workbooks, containing table calculations, could cause total consumption of system memory.
Workbooks connected to OLAP cube data sources would sometimes appear to hang when executing queries and fail to load.
Custom logos did not center correctly on the Tableau Server sign in and site selection screens.
When you clicked the Export Metadata File button in the SAML tab of the Configure Tableau Server dialog, the resultant XML file was malformed. A workaround was published.
Tableau Reader:
Opening a packaged workbook, with a Netezza-based extract, in Tableau Reader would fail with an error: "Unable to find matching connection config constructor for this class name: netezza"

New in Tableau 10.0.1 (Sep 20, 2016)

New Capabilities:
Connect directly to your Marketo instance, as you would any other data source in Tableau, then publish and refresh in Tableau Server/Online.
Corrected Issues:
In addition to the new capabilities, the following issues that were reported to us in prior releases have been corrected.
Tableau Desktop: 13 updates
Tableau Server: 30 updates
Tableau Online: 10 updates
Tableau Desktop:
In some cases, a 'no such function: STR' error would occur when you were connected to an SAP HANA data source in Tableau Desktop and attempted to use a calculated field that cast an integer to a string.
In Tableau Desktop, when you filtered using a top computed set and an INDEX() calculation a no such column error would occur.
In certain cases, connections to Microsoft SQL Server would fail when opening a workbook in Tableau Desktop and an unreasonable number of attempts would be made to reconnect before you were prompted to edit the connection.
Creating an extract in Tableau Desktop would fail with a "mismatched row counts" error if you had a group in a view and the group was based on a field that was also being used as a data source filter.
In Tableau Desktop, connecting to SAP BW would fail with an "Authorization failed" error if your password contained special characters.
In a small number of scenarios, sometimes involving level of detail calculations, extract query performance became significantly worse after upgrading to Tableau 9.3 or higher.
Joining a web data connector data source with another data source would sometimes fail to return valid data.
In some cases, grand total values would disappear when navigating between sheets using actions.
The Tableau Online Sync Client failed to run scheduled extract refreshes for some data sources published to Tableau Online using Tableau Desktop 10.0. This primarily affected data sources that used username and password authentication to connect to underlying databases as well as data sources containing two or more file-based connections.
When connected to a Microsoft Analysis Services data source in Tableau Desktop, using a non-English client locale, thousands separators would sometimes be incorrectly interpreted resulting in numbers that were displayed incorrectly.
Refreshing an IBM Big SQL-based extract using the Tableau Data Extract Command-Line Utility would fail with an error: '[IBM][CLI Driver] SQL30082N Security processing failed with reason "17" ("UNSUPPORTED FUNCTION"). SQLSTATE=08001 Invalid username or password.'
When you blended two data sources on a date field and exported a view as a crosstab to Excel, the results in Excel sometimes did not match the values displayed in Tableau Desktop.
In some cases, when connected to a Progress OpenEdge data source in Tableau Desktop and using a boolean field as a data source filter, a no such function error would occur when loading a view or describing a field.
Tableau Server:
When switching between custom views in Tableau Server, incorrect data would sometimes be returned if the views only differed by parameter selection and the parameter was being referenced in a calculated field used as a data source filter.
If you publish multiple QuickBooks Online data sources to Tableau Server or Tableau Online, and if the published data sources use the same embedded credentials, only the last published data source can be refreshed.
When you used a published data source that was connected live to an underlying table, and additional columns were added to that underlying table, refreshing the data source in Tableau Desktop would not update the data pane with the new columns for an extended period of time. Due to potential performance trade-offs of extra queries for column metadata, the fix is hidden behind a Tableau Server configuration setting that must be toggled on.
Line marks with transparency would sometimes fail to render in browsers on certain high-DPI displays or when the browser window was zoomed.
In some cases, when you published a small multiples view with pie marks to Tableau Server, the marks became unclickable in a browser. The result, most of the time, was that tooltips could not be exposed.
When you edit the credentials for a published QuickBooks Online data source, you cannot select a different company than the one originally associated with the published data source. Otherwise, extract refresh jobs for the data source will return a generic authentication error.
After upgrading to Tableau Server 10.0, if you tried to configure Tableau Server to use SAML and specified the HTTPS protocol in the return URL, without configuring Tableau Server for SSL (i.e. SSL is being offloaded), an error would occur and configuration could not proceed: "invalid protocol specified for SAML return URL. Use https if SSL is enabled or http otherwise"
After publishing to Tableau Server or Tableau Online, parameter slider controls were slightly offset from how they appeared in Tableau Desktop.
On one-node Tableau Server installations, no notifications were sent when Postgres went up or down.
When web authoring, after clicking Save or Done, a "Done Editing" page would appear and you could not return to the page you were on prior to web authoring.
In a small number of scenarios, sometimes involving level of detail calculations, extract query performance became significantly worse after upgrading to Tableau 9.3 or higher.
Portions of the Background Tasks for Extracts administrative view in Tableau Server and Tableau Online were cut off, particularly at smaller screen resolutions.
In Tableau Server, when you loaded a view using a URL parameter, and the same parameter was also used in custom SQL for the workbook's data source, the view would sometimes fail to show the correct data for the specified parameter value unless ':refresh=yes' was also appended to the URL.
When performing an in-place upgrade to Tableau Server 10.0 from a prior version, with SAML previously configured, saving the Tableau Server configuration during the upgrade would fail with an error and prevent the upgrade from proceeding.
In Tableau Server, adjusting a range of dates filter using the date picker would reset any previous time selection if there was a time part associated with the dates.
Periodically, VizQL server processes would encounter an internal error and CPU consumption sometimes increased. To work around this issue, restart the VizQL server process.
When you tried to configure a SAML-enabled Tableau Server, after upgrading to Tableau Server 10.0, an error would sometimes occur: "The 'xml' prefix must not be bound to any other namespace"
If you previously published a workbook, with a live connection to Microsoft SQL Server and authentication set to "Viewer credentials", and then tried to republish it with an extracted connection, you were not able to publish the workbook unless you renamed the workbook or deleted the existing published workbook from Tableau Server. This issue did not occur when publishing data sources.
After upgrading to Tableau Server 10.0, File Store processes would sometimes appear in an indefinite, busy "Synchronizing" status.
In some cases, when you interacted with a small multiples view containing pie charts in Tableau Server, visual artifacts would appear in the browser.
When viewing an embedded view, or using the share link, and downloading the view to PDF from Tableau Server, the Download PDF dialog sometimes did not appear, or was cut off, unless you zoomed out in the browser.
In Tableau Server 10.0 and Tableau Online, it was no longer possible to collapse and hide the upper navigation toolbar in the browser interface.
In Tableau Server, views connected to SAP HANA using SAML SSO would prompt users for SAP HANA credentials, if left idle in a browser for too long, and it would not actually be possible to sign back in for a period of time. The SAML timeout for SAP HANA SSO now has a longer default and is configurable.
In Tableau Server, the 'Live/Last extract' column in a workbook's data sources page failed to update when you refreshed the workbook's extracts in Tableau Desktop and republished the workbook.
Publishing a workbook to Tableau Server via REST API could sometimes fail with a bad request error.
In some cases, scheduled Salesforce-based extract refreshes would fail with an error: "com.tableausoftware.nativeapi.dll.DataSourceException:No such column [field name]."
Tableau Server connections to SAP HANA using SAML SSO were sometimes unnecessarily slow.
When you had a stepped color legend in a published Tableau Server view, zooming out in a browser would introduce an additional color step in the legend (usually white or black).
In Tableau Server and Tableau Online, the default value for the 'Min View Count' filter in the Traffic to Views administrative view was set too high, and the minimum adjustable value was 30 which was also too high.
When a dashboard with device layouts is viewed on a phone or tablet in portrait mode, Tableau Server sometimes incorrectly displays a device layout for a larger device. For example, instead of displaying a dashboard layout designed for phone, Tableau Server may display one for a tablet or desktop. If you share a link for the dashboard via the Share button, or if you view it from Tableau Mobile, the correct device layout is displayed. This issue only occurs when the dashboard is viewed from the Server user interface
Tableau Online:
In Tableau Server and Tableau Online, the default value for the 'Min View Count' filter in the Traffic to Views administrative view was set too high, and the minimum adjustable value was 30 which was also too high.
Line marks with transparency would sometimes fail to render in browsers on certain high-DPI displays or when the browser window was zoomed.
After publishing to Tableau Server or Tableau Online, parameter slider controls were slightly offset from how they appeared in Tableau Desktop.
When web authoring, after clicking Save or Done, a "Done Editing" page would appear and you could not return to the page you were on prior to web authoring.
Republishing and overwriting an existing workbook on Tableau Online would remove any previous extract refresh schedules for the workbook.
Portions of the Background Tasks for Extracts administrative view in Tableau Server and Tableau Online were cut off, particularly at smaller screen resolutions.
If you previously published a workbook, with a live connection to Microsoft SQL Server and authentication set to "Viewer credentials", and then tried to republish it with an extracted connection, you were not able to publish the workbook unless you renamed the workbook or deleted the existing published workbook from Tableau Server. This issue did not occur when publishing data sources.
The Tableau Online Sync Client failed to run scheduled extract refreshes for some data sources published to Tableau Online using Tableau Desktop 10.0. This primarily affected data sources that used username and password authentication to connect to underlying databases as well as data sources containing two or more file-based connections.
In Tableau Server 10.0 and Tableau Online, it was no longer possible to collapse and hide the upper navigation toolbar in the browser interface.
In some cases, scheduled Salesforce-based extract refreshes would fail with an error: "com.tableausoftware.nativeapi.dll.DataSourceException:No such column [field name]."

New in Tableau 10.0.0 (Aug 16, 2016)

Tableau Desktop:
Tableau Desktop would sometimes crash when opening a workbook with a web data connector data source.
Updated location for the 99603 zip code.
In some cases, changing a date filter selection would cause Tableau Desktop to crash.
Tableau Desktop would intermittently crash when reading metadata.
Publishing a workbook containing visualizations with many mark labels could potentially be very slow.
Wildcard filtering of string values was sometimes unacceptably slow.
When connected to Teradata, and using continuous date filters, Tableau Desktop would issue queries that cast date to timestamp resulting in poor query performance.
In some cases, changes made to dashboard layout in Tableau Desktop were not preserved when the workbook was saved and re-opened.
When pivoting multiple columns of different data types in Tableau Desktop, an error would occur: "Pivoted data type not unique for group".
Adjusting a filter slider in Tableau Desktop for Mac would sometimes cause the application to crash.
When connected to a Hive data source in Tableau Desktop, queries containing the 'GROUP BY 1' clause would sometimes be extremely slow.
In certain cases, when connected to an Excel data source containing pivoted fields and/or custom number formats, refreshing the live connection or extract resulted in seemingly random data being displayed in Tableau Desktop.
In Tableau Desktop, using a set-based Top N filter with a separate context filter often returned incorrect results when the filters were modified.
In some cases, map shapes and other marks would render without any fill color.
Labels for the Japanese cities of Minoh (箕面) and Ibaraki (茨木) were incorrect when the 'Place Names' map layer was displayed in Tableau Desktop.
In certain cases involving calculations with aggregate functions (e.g. COUNTD, MIN, MAX), Tableau Desktop query performance would differ dramatically when using a published data source vs. an identical local data source.
Updated Australian postcodes.
When publishing a data source to Tableau Online from Tableau Desktop, the publish progress dialog window did not accurately show overall progress.
Updated locations for the 33036 and 33050 zip codes.
Tableau Server:
Exporting a Tableau Server view to PDF, via tabcmd, would fail if the page size was set to tabloid or ledger.
Zooming maps on mobile devices would stop working after swapping map views using a parameter.
Wildcard filtering of string values was sometimes unacceptably slow.
Color shading for grand totals would be lost when publishing a workbook to Tableau Server and viewing the workbook in a browser.
Tableau Server configured with Okta SAML failed to authenticate users if the URL domain name case did not match between the Tableau Server and IdP configurations. (Also applies to Issue ID 525841)
If Tableau Server was unlicensed, extract refresh jobs would still be run. Refresh jobs are now no longer attempted if the server is in an unlicensed state.
In a visualization containing multiple marks cards, with the same field on the Filters and Color shelves, changing the filter would incorrectly grey out marks when the visualization was published to Tableau Server and viewed in a browser.
In some cases, map shapes and other marks would render without any fill color.
In Tableau Server, the 'Traffic to Views' administrative view would show a separate entry for each revision of a view when the revision history functionality was enabled.
Users signing into a multi-site Tableau Server were presented the option to sign into sites that they did not have access to. Attempting to sign into one of the forbidden sites correctly resulted in a permissions error.
In some cases, editing a user filter set in Tableau Desktop would fail with an error if Tableau Server failed to return a user list.

New in Tableau 9.3.6 (Aug 16, 2016)

Tableau Desktop:
In some cases, refreshing an extract in Tableau Desktop would refresh the extract using cached data and fail to correctly update the extract with new data. This affected extracts based on relational data sources and did not affect affect those based on file-based data sources.
In Tableau Desktop, when you filtered using a top computed set and an INDEX() calculation a no such column error would occur.
In Tableau Desktop, when you extracted a table containing very long column names an error would sometimes occur: "Tableau Data Engine Error: 4: SimpleDatabase::SelectMetadataName".
Attempting to connect to a corrupted or locked Excel file would sometimes cause Tableau Desktop to crash.
Loading certain workbooks, containing table calculations, could cause total consumption of system memory.
Workbooks created in a version prior to Tableau Desktop 9.3, containing a reference line configured to use maximum, minimum, average, or median aggregation, would display a different reference line value when opened in Tableau Desktop 9.3.
When you adjusted the size of a dashboard using the range option in Tableau Desktop, the size control values often showed incorrectly after navigating to a different sheet and returning to the dashboard or after re-opening the workbook. The actual size of the dashboard would be correct, however, as the issue only affected the values displayed in the size controls.
When connected to Teradata, in Tableau Desktop, the ProxyUser query band value would not be sent correctly to the database as an empty string when additional characters were appended to the query band parameter.
In some cases when parameters are duplicated in Tableau Desktop, due to conflicting parameter names in the workbook and the data source, views did not correctly update when you changed the parameter selection.
When connected to Cloudera Impala in Tableau Desktop, certain date fields would return null values.
In some cases when you had a workbook containing multiple extracted connections to the same data source, that were created by pasting a sheet or adding a bookmark, editing one of the data sources would modify and overwrite the other data sources.
Creating an extract in Tableau Desktop would fail with a "mismatched row counts" error if you had a group in a view and the group was based on a field that was also being used as a data source filter.
In some cases in Tableau Desktop, when you were connected to a cube data source, dimensions inserted into sheet titles did not display the correct member values.
In Tableau Desktop, when you had a dropdown filter containing only a single value, the filter selection was shown as "(All)" even if the Show "All" Value option was not checked.
Tableau Desktop would sometimes crash when you attempted to publish a workbook to Tableau Server.
When you attempted to add a filter to a dashboard with a horizontal scroll bar, Tableau Desktop would sometimes crash.
Tableau Desktop would often crash when you attempted to edit a large, complex data source.
Tableau Server:
When you imported a site containing custom views into Tableau Server, the "Remove Garbage Repository Records" background task would begin to fail and the repository database would steadily grow in size.
In some cases, when you published a workbook containing multiple data sources, the Subscribe button would not appear when viewing the workbook in Tableau Server or Tableau Online (Also applies to Issue ID 520559).
Workbooks connected to Microsoft Analysis Services, when loaded in Tableau Server, would often cause the database user account to be locked out.
Loading certain workbooks, containing table calculations, could cause total consumption of system memory.
Navigating between two dashboards in Tableau Server, using a filter action run on select, would fail if the target filters for the action contained fields from multiple published data sources.
In some cases, synchronizing Active Directory groups in Tableau Server would fail to synchronize all users in a group if the group contained users from multiple domains and a user account from a secondary domain was deleted or disabled in Active Directory.
In Tableau Server, loading a dashboard based on Microsoft SQL Server data sources would sometimes cause the database user account to become locked out.
Certain large calculated fields, that contained hundreds of lines of formula, could cause excessively large queries to be generated and max out Tableau Server system resources.
When you grouped dimensions by folder in Tableau Desktop, then changed to group by table, and then published the data source or workbook, dimensions would appear twice in the data pane in Tableau Server web authoring mode.
Tableau Online:
Long running extract refreshes (i.e. multiple hours) using the Tableau Online Sync Client would sometimes fail with an internet communication error.
In some cases, when you published a workbook containing multiple data sources, the Subscribe button would not appear when viewing the workbook in Tableau Server or Tableau Online (Also applies to Issue ID 520559).

New in Tableau 9.3.5 (Jul 28, 2016)

New in Tableau 9.3.4 (Jul 13, 2016)

New in Tableau 9.3.3 (Jun 15, 2016)

Corrected Issues:
Opening workbooks connected to published data sources in multiple instances of Tableau Desktop would sometimes result in a "Worksheet unavailable" error when loading a view.
When attempting to edit a published data source in Tableau Desktop, if the data source resided on a Tableau Server configured to use a non-default port, an error would occur: "This workbook contains a Data Source that is dependent on a different Tableau Server. Multiple Tableau Server connections are not supported".
In Tableau Desktop, a parameter inserted into the URL of a web page dashboard object used the display value of the parameter instead of its actual value.
When connected to a published data source in Tableau Desktop, attempting to pivot more than 26 columns in the data grid produced unexpected results.
When signing into Tableau Server from Tableau Desktop, if your Tableau Server was configured to use local authentication, the remembered username in the Tableau Desktop sign in dialog would contain a "local\" prefix and fail to sign in after entering your password. Removing the "local\" prefix would allow the sign in to succeed.
Editing a filter title on a dashboard would sometimes fail to preserve the change when saving and re-opening the workbook in Tableau Desktop.
In some cases, incrementally refreshing a Salesforce extract would remove some or all data from the extract.
In some cases in Tableau Desktop, after refreshing an extract in a packaged workbook and saving the workbook, re-opening the workbook would fail with an unexpected error.
In Tableau Desktop, connecting to an SAP BW query containing navigational attributes exceeding 28 characters, and attempting to use the attributes in a view, would result in an invalid MDX command error.
If a workbook contained a data source with tables joined on a pivoted field, a data source error would occur every time the workbook was re-opened in Tableau Desktop, which then required editing the data source to redefine the join condition.
Searching for fields in the Tableau Desktop Data pane would not display broken or invalid fields (i.e., fields with a red exclamation point) in the search results.
When connecting to Google Analytics in Tableau Desktop running on a Windows 10 machine, and specifying a fixed date range or fixed start date, the calendar widget would partially or completely cut off Saturdays.
Creating or refreshing an extract based on a published data source, and with visible dimensions aggregated, would fail with an error: "StarExtractTupleSource has wrong number of bindings for number of inputs columns".
In Tableau Desktop, connecting to OData using Windows Authentication would fail.
In Tableau Desktop, attempting to create a conditional extract filter, by formula, on a date field would result in an internal error.
Removing a web page object from a dashboard, or closing the workbook containing the web page object, would sometimes cause Tableau Desktop to quit unexpectedly.
When connected to Exasol in Tableau Desktop, converting a datetime field to float using the FLOAT() function would incorrectly return an integer.
When creating a range of dates filter in Tableau Desktop, the slider and type-in boxes in the filter dialog did not allow for seconds to be specified.
In some cases, a field that was unhidden in the data grid on the Data Source tab would still not appear in the Data pane when authoring a sheet. This tended to occur for fields containing mostly null values.
In some cases in Tableau Desktop, attempting to use a published data source containing a parameter that was duplicated from an original parameter, with an angle bracket in its name, would result in an error: "Custom SQL relation refers to a non-existent parameter".
In some cases, when you ran a filter action used to navigate between dashboards, it would unexpectedly trigger across all dashboards in the workbook and cause a cascading filter effect or take you to the wrong dashboard.
In some cases, incrementally refreshing a Salesforce extract would cause excessively slow Data Engine queries resulting in workbooks appearing to fail to load.
A site user with the "Unlicensed (Can publish)" role was not able to publish content from Tableau Desktop to Tableau Server if the same user also existed in a different site.
In certain cases, when connected to Google BigQuery in Tableau Desktop, filtering on a field not used in the view would result in a "No such column" error.

New in Tableau 9.3.1 (May 18, 2016)

New Capabilities:
This release adds a new connector that gives you the ability to connect to Cisco Information Server.
This release adds a new connector that gives you the ability to connect to Kognito 8.2
This release adds support for Oracle 12c In-Memory.
Corrected Issues:
In addition to the new capabilities, the following issues that were reported to us in prior releases have been corrected.
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.
When connected to SybaseIQ in Tableau Desktop, attempting to edit a Top N set filter would fail with an error.
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.
When signing into Tableau Server from Tableau Desktop, the remembered user name would drop the domain prefix if it had been previously entered.
In Tableau Desktop, filters containing table calculations would sometimes cause row and column grand totals/sub-totals to disappear.
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.
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.
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.
In Tableau Desktop, connecting to an OData data source utilizing digest authentication was not supported and attempts to connect would fail.
When joining tables, the default join relationships were often not the expected ones.
Connections to some databases from Tableau Desktop would fail to drop some temporary tables upon connection close.
When connected to HP Vertica in Tableau Desktop using a version 7.1.x driver, Unicode characters were not displayed correctly.
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.
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.
In some cases in Tableau Desktop, changing the scope for mark labels from Table to Pane had no effect.
When connected to Sybase ASE in Tableau Desktop, the Sort by Field option was not available in the Sort dialog when sorting a dimension.
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.
When connected to a cube data source, sheet titles that dynamically changed with filter selections would sometimes fail to display the correct values.
Changing a workbook parameter that was tied to a Microsoft SQL Server stored procedure parameter would sometimes cause Tableau Desktop to become unresponsive.

New in Tableau 9.3.0 (Mar 24, 2016)

New in Tableau 9.2.6 (Mar 10, 2016)

Tableau Desktop:
In Tableau Desktop, when you created a local copy of a published data source, an internal error sometimes occurred.
In Tableau Desktop, when connected to an SAP BW data source, filtering out null values also incorrectly filtered out zeros.
In Tableau Desktop, NULL incorrectly appeared as a member of an IN/OUT set.
In Tableau Desktop, when you added a reference line based on certain table calculations, an error occurred: "No such table."
In Tableau Desktop, when connecting to SAP HANA, performance degraded when specifying type-in values for a large number of variables and sometimes caused Tableau Desktop to become unresponsive.
In Tableau Desktop, an update to Amazon Redshift caused temporary table creation to fail when creating new connections to Redshift.
In Tableau Desktop, when you applied a context filter, deselecting a single member of a set filter resulted in deselecting all members.
In some cases in Tableau Desktop, filter actions used to navigate between dashboards took users to the wrong dashboard.
In some cases in Tableau Desktop, adding a sheet to a dashboard resulted in an internal error.
In Tableau Desktop, when you renamed dimensions in a Microsoft Analysis Services cube, existing workbooks connected to the cube threw errors when re-opened.
In certain cases, Tableau Desktop closed immediately after launch due to an internal licensing error.
Tableau Desktop crashed if you were connected to 3 or more published data sources while editing data source server and site paths.
Tableau Server:
In Tableau Server, when you clicked a URL action referencing an email address, an error displayed even though an email client correctly opened.
Scheduled background tasks in Tableau Server sometimes failed to run due to expected periodic backgrounder process shutdowns while jobs were still queued.
In Tableau Server, general filters didn't work correctly on the Data Sources page.
Custom shape images appeared stretched and blurred when rendered in a browser.
In Tableau Server, certain views containing Measure Names with "Show Empty Rows/Columns" enabled failed to render on initial load.
When viewing a schedule in Tableau Server, "No extract refreshes" sometimes displayed even though the schedule contained tasks.
Publishing a workbook or data source containing Teradata initial SQL to Tableau Server resulted in an error. This error also occurred when refreshing pre-9.2 extracts containing Teradata initial SQL on a server that had been upgraded to version 9.2.
In Tableau Server, when you published to a project with locked permissions, users were still able to edit group permissions in the Tableau Desktop publish dialog. Subsequently attempting to publish the workbook resulted in an error: "Cannot publish with modified permissions. Permissions are locked in the project you are publishing to. To publish this workbook, use the default permissions and try again."
In Tableau Server, the Cancel and Save buttons sometimes appeared in incorrect positions when modifying permissions, especially if the User/Group list was long.
In Tableau Server configured with SAML and multiple sites, either signing into the default site, and then switching sites, or signing into a non-default site caused sign out to fail.
If you accessed Tableau Server in Internet Explorer 8 and made a filter selection, an error occurred: "Exception thrown and not caught."
In certain cases in Tableau Server, users were not able to sign in using their user principal name after being added to the server.
When editing permissions in Tableau Server, the Cancel and Save buttons sometimes appeared hidden and inaccessible outside of the visible User/Group list.
In web authoring on Tableau Server, when viewing the calendar control for a date filter, Sundays were missing and dates did not line up with the correct days.
In iOS Safari and Tableau Mobile, parameters were misaligned.

New in Tableau 9.2.5 (Feb 26, 2016)

New in Tableau 9.2.4 (Feb 6, 2016)

CORRECTED ISSUES:
In addition to the new capabilities, the following issues that were reported to us in prior releases have been corrected:
Tableau Desktop: 10 updates
Tableau Server: 19 updates
Tableau Reader: 1 updates
TABLEAU DESKTOP:
In Tableau Desktop, when you edited a Microsoft SQL Server data source to point to a different Microsoft SQL Server database server, an error occurred if a database with the same name did not exist on both servers.
In Tableau Desktop, when you used an aggregated filter with data blending and a reference line based on a workbook parameter, the filter didn't correctly update the view.
In Tableau Desktop, when you were connected to an SAP NetWeaver Business Warehouse data source and assigned a custom color palette to marks, refreshing the data source caused the color palette to revert to default.
When creating a data source in Tableau Desktop, tables with foreign key relationships didn't automatically join.
In Tableau Desktop, when you created an extract from a published data source and then tried to edit the data source, an error occurred: "Errors occurred while loading the data source."
In Tableau Desktop, when you created a local copy of a published data source, an internal error sometimes occurred.
Tableau Desktop sometimes quit unexpectedly when you signed into a Tableau Server configured to use mutual SSL.
An error occurred when you ran the installer for Tableau Desktop, Tableau Reader, or Tableau Server: "The signature was corrupt or invalid."
In Tableau Desktop, when you edited certain datetime type stored procedure parameters, an internal error occurred.
When you signed into a previously used Tableau Server from Tableau Desktop, the remembered server name didn't retain SSL or any custom port information, and resulted in an error: "Username or password incorrect."
TABLEAU SERVER:
In Tableau Server, when non-admin users signed in, a "Resource Not Found" page displayed if their previously selected start page no longer existed.
In certain cases in Tableau Server, content didn't display after upgrading due to failed search indexing.
In Tableau Server, type-in filter text boxes didn't accept characters produced by the [AltGr] modifier key.
In certain cases after you upgraded Tableau Server, content was missing, and when you attempted to rebuild the search index to correct the problem, an error occurred.
In Tableau Server, when you clicked a menu action that linked to a filtered target sheet, an error sometimes occurred: "Tableau Server Error: unable to get property 'length' of undefined or null reference."
In Tableau Server, when you attempted to use certain filter actions, an internal error occurred.
In Tableau Server, tooltips in published workbooks updated inconsistently when hovering between marks.
In Tableau Server, when you refreshed a view connected to multiple SQL Server stored procedure data sources, an invalid column name error sometimes occurred.
The Tableau 9.2 SDK no longer worked with certain older Linux operating systems.
In Tableau Server, exporting a site failed if the system administrator had accessed a workbook using OAuth but did not own any content.
In some cases in Tableau Server, extract files were mistakenly reaped and deleted, resulting in failed workbook loads and/or extract refreshes.
In Tableau Server with SAML enabled, when an SHA-256 certificate was used, SAML messages were incorrectly signed with the SHA-1 algorithm.
In some cases in Tableau Server, accessing a published view using SAML authentication failed if guest access was disabled and wgserver.saml.iframed_idp.enabled was set to true.
Upgrading Tableau Server, when configured to use SSL for communication with the internal repository database, sometimes failed on a non-English operating system. The issue also sometimes occurred when first configuring Tableau Server to use SSL for internal repository database communication.
In Tableau Server, the "Background Tasks for Non Extracts" activity view showed that scheduled subscriptions were sent successfully, even if subscriptions were disabled server-wide.
In Tableau Server, when you filtered certain dashboards using a Single Value (Dropdown) filter, an error occurred: "Unexpected Error: Unable to get property 'css' of undefined or null reference."
In Tableau Server, Cache Server processes sometimes hung and showed as down in Server Status.
An error occurred when you ran the installer for Tableau Desktop, Tableau Reader, or Tableau Server: "The signature was corrupt or invalid."
In certain cases, when you imported a Tableau Online site to Tableau Server, an error occurred: "ConstraintViolationException: could not execute statement."
TABLEAU READER:
An error occurred when you ran the installer for Tableau Desktop, Tableau Reader, or Tableau Server: "The signature was corrupt or invalid."

New in Tableau 9.2.2 (Jan 21, 2016)

New in Tableau 9.2.1 (Jan 21, 2016)

New in Tableau 9.2.0 (Dec 8, 2015)

New in Tableau 9.1.2 (Nov 24, 2015)

In certain workbooks, when you used MS Analysis Services named sets as top or bottom filters, an Analysis Services database error sometimes occurred when you loaded the workbook.
When Tableau Desktop was running on a system with an Intel HD Graphics 5500 series chipset, small white dots sometimes appeared on bar marks .
On a Mac, opening a workbook connected to MS SQL Server using manually specified AD credentials sometimes locked the user account out of MS SQL Server.
In Tableau Desktop, sometimes sheet summary card labels were missing. Resizing the Tableau Desktop window and/or the summary card often corrected the issue.
In Tableau Desktop for Mac, the Worksheet > Copy menu command was sometimes unavailable and/or duplicated.
In Tableau Desktop, percentages based on table calculations did not compute correctly and, in some cases, did not add up to 100 percent.
In Tableau Desktop, Cyrillic characters in table names were mangled when you connected to MySQL.
Workbooks that contained certain Boolean calculations or other algebraic expressions displayed the following error message when opened in Tableau Desktop 9.1: "Tableau Data Engine Error: 4: DataFlow Error".
In Tableau Desktop 9.1, when you opened a workbook created in an earlier version of Tableau Desktop, creating a calculated field sometimes resulted in an internal error.
In Tableau Desktop, when you used certain parameter-based calculated fields, viewing underlying data sometimes resulted in a function call error.
In Tableau Desktop, some latitude and longitude data produced a map view that was too zoomed-in to be useful.
After an extract was refreshed and a workbook was saved, old data would sometimes be shown when the workbook was reopened.
After upgrading to Mac OS X El Capitan (10.11) it was no longer possible to connect to an SSL-enabled PostgreSQL database from Tableau Desktop. This was because the PostgreSQL library built into Mac OS X El Capitan was not compiled with SSL.
In Tableau Desktop, when working on a dashboard with quick filters that belonged to different sheets, sometimes interacting with a quick filter changed the wrong sheet.
In Tableau Desktop, printing to PDF with "Repeat headers and legends on each page" off and with a horizontally centered layout resulted in an internal error.
In Tableau Desktop, when you edited a connection to Google BigQuery that you had already saved, you couldn't change to a different data set.
In Tableau Desktop, context filters were removed from context when references were replaced in fields that the filters were based on.