Softpedia >Mac >Business >Tableau Reader >  Changelog

Tableau Reader Changelog

What's new in Tableau Reader 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 Reader 2024.1.0 (Feb 22, 2024)

  • Resolved Issues:
  • When using an "if" calculation in Tableau Desktop, incorrect results are displayed if there is a nested "if" statement within the calculation.
  • Views may take drastically longer to load in 2023.x after selecting a filter value.
  • The filter pill for a single-value domain does not display the value.

New in Tableau Reader 2023.3.3 (Feb 16, 2024)

  • Resolved Issues:
  • When connecting to an Oracle database with a field of the TIMESTAMP WITH LOCAL TIME ZONE data type, that field was assigned a STRING data type in Tableau Desktop, instead of a DATETIME as expected.
  • 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.
  • Tableau Desktop on Macintosh intermittently hangs while publishing large workbooks or data sources to Tableau Cloud.

New in Tableau Reader 2023.3.2 (Jan 31, 2024)

  • Resolved Issues:
  • After January 1, 2024, Hamamatsu City in Japan will change from 7 Wards to 3 Wards.
  • "Error code: 63CFBA9A" and "Error executing subquery id:xxxx [SQLSTATE:42710] database alias name 'dbxxx' already in use" appears frequently with some workbooks.

New in Tableau Reader 2023.3.1 (Jan 11, 2024)

  • Resolved Issues:
  • W-13576170 When a live Snowflake connection was used, an incorrect month value was returned for date/time fields when using datetrunc.
  • W-13678602 Connected to Salesforce data and using custom SQL, the "Group by" clause returns NULL for the aggregated results ID on Tableau Desktop version 2021.3 or higher.

New in Tableau Reader 2023.3.0 (Oct 25, 2023)

  • Resolved Issues:
  • W-13143369 The Parameter changes on a Story Point also would change the underlying worksheet.

New in Tableau Reader 2023.2.2 (Sep 22, 2023)

  • Resolved Issues:
  • W-13630830 Connecting from Tableau Desktop or Tableau Server to a Snowflake data source could result in "Invalid consent request" error when the Role Name entered used double quotes because case sensitivity (lower case) was not retained with the double quotes.
  • W-12903840 MongoDB ODBC driver was not picked up by Tableau Desktop on macOS.

New in Tableau Reader 2023.1.2 (May 19, 2023)

  • Resolved Issues:
  • When trying to connect to a Virtual Connection from Tableau Desktop, the follow errors could occur, "Internal Error - An unexpected error occurred and the operation could not be completed. Error Code: 64EA58CC".
  • When trying to change the case sensitivity for any field, an error would display stating "Can't rename the Field." For example, changing "ID" to "id" would result in an error.
  • When using the Image Role feature with a resized argument, the image is not displayed.

New in Tableau Reader 2023.1 (Mar 15, 2023)

  • Resolved Issues:
  • When using a calculation as a parameter's value when the workbook opens, and refreshing the Salesforce extract, the following error could occur: "Error Code: 0x08DDBC8C".
  • When using a Reference Line, the following errors could occur: "Error code: 58D44822. Unable to complete action. Type doesn't match expected type."
  • On Mac OS Big Sur, the edit alias could be unresponsive when double-clicking a column or field name.

New in Tableau Reader 2022.4.1 (Feb 24, 2023)

  • Resolved Issues:
  • When opening a workbook, some worksheets fail to load and show null values when using French locale.

New in Tableau Reader 2022.4 (Feb 24, 2023)

  • Resolved Issues:
  • For External Actions, when a string is mapped to a boolean flow input, any non-"false" string defaults to "true".

New in Tableau Reader 2022.3.1 (Nov 18, 2022)

  • Resolved Issues:
  • In version 2022.3.0 and 2022.4.0, the "Hide card" option could be missing on the context menu of sets, legends, highlighters, and parameters.

New in Tableau Reader 2022.3 (Oct 19, 2022)

  • Resolved Issues:
  • When attempting to login to Tableau Cloud from Tableau Desktop "ALT-GR" can not be used to input symbols on non-English keyboards.

New in Tableau Reader 2022.2.2 (Sep 29, 2022)

  • Resolved Issues:
  • When trying to select a data source in the "Edit Tableau Server Data Connection" window, a crash would occur when Tableau Server had more than 10,000 data sources.
  • In the aggregation options of the reference line, "Total" and "Sum" are translated to Japanese and duplicated starting with 2021.4.
  • When Japanese or Chinese characters were used in the Parameter dialog, the error "Uncaught TypeError: e.persist is not a function" would occur.

New in Tableau Reader 2022.2.1 (Aug 31, 2022)

  • Resolved Issues:
  • The Spark SQL connection did not allow for the viewing of the "httppath" when using the Simba driver.
  • A crosstab would often show null values after changing and removing the quick filter value.
  • A crash could occur signing into Tableau Server if using OAuth and a Java Environment variable that contained a dot (".").
  • When using the Zoom Area feature in the View toolbar, the following error could occur, "The filtering operation did not complete successfully because of an unexpected error. Error code: 00BF554A."
  • After publishing a view to Tableau Cloud in 2022.2.0, the drill-down set actions do not function as they did in the previous release.
  • Tableau Desktop with Mutual SSL logins to Tableau Server could fail with error 9F4C5638 after upgrading to a version of Tableau Desktop released in November of 2021 or newer such as 2021.1.8.

New in Tableau Reader 2022.2.0 (Jun 30, 2022)

  • Resolved Issues:
  • When publishing a workbook, it would sometimes not be possible to see existing content in the publishing dialogue box.
  • Selecting "Show actions for this sheet" would display actions existing for all sheets even if the source sheet was not selected

New in Tableau Reader 2022.1.3 (Jun 22, 2022)

  • Resolved Issues:
  • Data connection details are not pre-populated when a workbook is opened with a Presto LDAP connection.
  • If a search term contained a space character, the ability to find and open a workbook on Tableau Server returned no results when on Tableau Desktop.
  • Multiple OAuth authorization prompts would occur when a workbook has multiple Google BigQuery connections.
  • Using the Dropbox connector could lead to the Dropbox authentication error message, "Error connecting app: This app is unable to link additional users because it has been frozen pending review."

New in Tableau Reader 2022.1.2 (May 25, 2022)

  • Resolved Issues:
  • When opening a workbook connected to a JSON cloud file data source, the following error could result, "Error Code A7CFA9FE".
  • When connecting to Informix/Denodo data using the CData connector, the error "AlqProcessor evaluation failed" could occur. The following message could also occur, "Bad Connection: Tableau could not connect to the data source. Error Code: B19090E0".
  • When publishing a workbook to server and modifying a user's permissions, the user in the preview window would be blank.
  • Workbook data accuracy could render differently in 2021.3 and newer when compared to older versions.
  • Adding a map layer with blended data could result in an error code D9151F7B.
  • An error code E04B915D would occur when attempting to edit a calculate field after pivoting data.
  • It was not possible to connect to a data source using a port greater than 65499.
  • The Kanji character was incorrect when using the Workbook Optimizer.
  • The Workbook Optimizer would redirect to the incorrect help link when expanding a section and a rule.
  • When using LBLM as the activation method, sometimes the LBLM reports on Tableau Server or Tableau Online would not show the correct usage data.

New in Tableau Reader 2022.1.1 (Apr 23, 2022)

  • Resolved Issues:
  • Updated Spring framework to 5.3.18
  • Updated Spring Boot to 2.5.12
  • A field label on a bar chart would sometimes not display after a sort occurred when at least one column field is blank. When published to Tableau Server, the label would appear as expected.
  • Visualizations within tooltips applied across all marks, were not properly passing filters when there were multiple fields. The filter would only work against the last field.
  • The Viz in Tooltip option was not filtering the sheet correctly when a dual-axis was used for the same measure.

New in Tableau Reader 2022.1.0 (Mar 31, 2022)

  • Resolved Issues:
  • When filtering two marks on a view the axis labels would sometimes not appear.
  • When the end user selected a column header after initiating the parameter button, it would sometimes result in a crash.
  • The 'Exclude' option would sometimes not work in the color marks card list, when the same field was used also on the filters shelf and had 'Use All' selected.

New in Tableau Reader 2021.4.4 (Feb 25, 2022)

  • Resolved Issues:
  • Queries would fail to run if they contained the "TO_LOCALDATE" function.
  • The "exclude" option within a Tooltip would sometimes not work.
  • When connecting to Exasol with a live connection the end user would sometimes be unable to use the "Quarter" function.
  • Combined headers would sometimes be missing a white space separator if the UI language was not English.
  • When replacing a published data source with a local copy, it would sometimes result in a an error.

New in Tableau Reader 2021.4.3 (Jan 14, 2022)

  • Resolved Issues:
  • Updates all active log4j-core files to 2.17.1.
  • The timezone would be correctly set via InitialSQL, however selecting a timestamp from a PostgreSQL table via custom SQL would return the incorrect time.
  • In a visualization after selecting "show empty rows" it would sometimes result in having wrong axis values displayed.
  • When conducting a fixed Level of Display calculation it would sometimes result in a pop-up that states, "Processing request: Executing query", and would run until the program was terminated.

New in Tableau Reader 2021.4.2 (Dec 20, 2021)

  • Resolved Issues:
  • Updates Log4J to 2.16.0 to address the issues identified in CVE-2021-44228 and CVE-2021-45046

New in Tableau Reader 2021.4.1 (Dec 16, 2021)

  • Resolved Issues:
  • Contains updates to Log4J 2.15.0 to mitigate against CVE-2021-44228

New in Tableau Reader 2021.4 (Dec 10, 2021)

  • Resolved Issues:
  • An unknown license line item appeared in Manage Product Keys for Tableau Desktop which showed the license expiration date as "30-Dec-1899".

New in Tableau Reader 2021.3.4 (Dec 2, 2021)

  • Resolved Issues:
  • When creating a "custom value list" filter with more than ten values on the list and a live connection to Google BigQuery an error would occur.
  • If the user used a context filter and another filter displaying all the values within the context filter, by selecting one value in each filter it would reset the filter displaying all values to "all".
  • If a relationship and extract were applied in the same workbook and an ISO calculation was used it would result in an error: "Unable to complete action. Tableau cannot evaluate the query that results from this calculation. Error Code: F5328B32"
  • The workbook title would sometimes display incorrectly when using a set as a filter in version In 2020.4.0 or later.
  • The time to show the menu dialog box after right clicking a parameter would sometimes be longer than expected
  • End user would sometimes experience a decrease in performance when filtering date range and location in a workbook with row level security.
  • End users would encounter an error when using CTRL+A to select column on the data source screen
  • End users were unable to reset the field names of multiple fields at once.

New in Tableau Reader 2021.3.3 (Oct 27, 2021)

  • Resolved Issues:
  • When using continuous dimensions it was not possible to set "Force the y-intercept to zero"
  • Data Server would fail to start on Ubuntu after upgrading to Tableau Server 2021.3.0
  • In Tableau Desktop when using range parameters the default value would be disabled.
  • In Tableau Desktop unexpected formatting behavior would sometimes occur when visualizing certain datetime parts on a continuous axis.
  • In a Redshift data connection, a data type for a field defined as a date, would return "datetime" and result in a slow query.
  • When connecting to a published data source over 3 GB and using a join, an error could display stating, "Error opening archive file. Invalid twb or twbx file."
  • In Tableau Desktop, within the Analytics pane the language would sometimes not localize correctly in the "Add Totals" display.

New in Tableau Reader 2021.3 (Sep 8, 2021)

  • Resolved Issues:
  • It was not possible to connect to PrestoSQL after rebranded as Trino.
  • After dragging a field to the view, an error could occur ,"SQLSTATE:53100] Hyper was unable to grow the file partition."

New in Tableau Reader 2021.2.2 (Sep 3, 2021)

  • Resolved Issues:
  • With the Denodo connector, when using an "OR" condition in a calculated field and dragging the calculated field to Filter card, an error would occur stating "ERROR: Syntax error: Exception parsing query near 'IN'".
  • The error, "invalid map key", could occur when setting Extend Date Range and the Most Recent option on the Label Marks card.
  • When logging into Tableau Server from Tableau Desktop, the "Select Site" dialog could be blank after switching sites but using the same site originally selected.

New in Tableau Reader 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 Reader 2021.2 (Jun 24, 2021)

  • Resolved Issues:
  • Simba SQL Server ODBC driver version 1.5.5 required "Integrated Security=true" in the connection string for NTLM and Kerberos Windows authentication on Macintosh.
  • "Error Code: AE406838 [SQLSTATE:53100] Hyper was unable to grow the file partition" would sometimes occur when changing a filter in a worksheet. The Tableau Online error would show "[SQLSTATE:53S03] Cannot allocate bytes of memory."
  • When a federated datasource is published from the Data tab by selecting "Create Data Extract" or "Activate Data Extract", the screens presented could be incorrect and confusing.
  • A WDC could cause Tableau Desktop to become unresponsive.
  • An error message could display on opening a workbook, "Error Code: ADE4BC90 Missing password. Unable to properly calculate the domain for the field 'Artifact Id'. Displayed data may be incorrect."

New in Tableau Reader 2021.1.2 (May 19, 2021)

  • Resolved Issues:
  • When a live connection to Oracle and context filters are used, the following error could occur:
  • "Oracle database error 1652: ORA-01652: unable to extend temp segment by 128 in tablespace TEMP".
  • It would not be possible to disable the "Allow Pan and Zoom" option when using a background image.
  • An error would sometimes occur when connecting to a SAP HANA table. The error would display, "Internal Error - An unexpected error occurred and the operation could not be completed. Error Code: 6EA18A9E".
  • In some cases, the data type of a specific column was not being recognized correctly.
  • Tableau Desktop was not persisting the authentication cookie in some cases with the WDC connector starting in 2020.2.2. The updated version of the WDC javascript library will need to be used in addition to the WDC making a call to the tableau.enableCookiePersistence() to enable cookie persistence in the Desktop session.

New in Tableau Reader 2021.1.1 (Apr 23, 2021)

  • Resolved Issues:
  • The published data source list could be empty from Tableau Desktop when Tableau Server was behind an authenticated reverse proxy.
  • Data source connection error messages could be obscure when connecting to PostgreSQL and a proxy server was used.

New in Tableau Reader 2021.1 (Mar 26, 2021)

  • Resolved Issues:
  • Exporting or printing a dashboard as a PDF could cause missing data lines on a map.
  • The filled map with zip code polygons would not line up correctly with the background map layer for the state of New Mexico.
  • Errors that occurred when connecting to SharePoint Lists would not display in the user interface.

New in Tableau Reader 2020.4.3 (Mar 25, 2021)

  • Resolved Issues:
  • An error would sometimes occur when creating a PostgreSQL extract that reported, "An error occurred while communicating with the PostgreSQL data source 'influencer_v4 (ALL)'. Error Code: 1A7DD10C. ERROR: function min(json) does not exist. Error while executing the query. Unable to create extract."
  • An error could occur when an attempt was made to connect to a .tds file and an Oracle schema was selected. The error would display as follows: "Internal Error - An unexpected error occurred and the operation could not be completed. Error Code: 6EA18A9E."
  • Dimensions and Measures could be missing when a workbook was opened that was created with a custom SQL Salesforce data connection.
  • It would sometimes not be possible to create an empty extract using a calculated field with aggregate data. The error would display as follows, "Internal Error - An unexpected error occurred and the operation could not be completed. Error Code: 6EA18A9E. Unable to create extract."
  • Extracted data could show incorrect when using SQL Server table collation Japanese_90_CI_AS.
  • A crosstab to PDF export sometimes had duplicated row dividers.
  • When a workbook used a percentile in the custom sort of a table calculation, the workbook save would fail. The save would produce the error "Save workbook failed. Error Code: CA8336D0."

New in Tableau Reader 2020.4.2 (Feb 26, 2021)

  • Resolved Issues:
  • Aggregation of a calculated field could show incorrect results when another measure was added or removed from the Measure Values card starting with 2020.2.
  • Korean characters would display as black boxes in a Japanese Windows system.
  • A string calculation that is used for a search filter could produce inconsistent results after an upgrade of the product.
  • Opening some WDC connectors could cause a Tableau Desktop crash.

New in Tableau Reader 2020.4.1 (Jan 22, 2021)

  • Resolved Issues:
  • A worksheet within a dashboard would appear blank if a parameter that limits data is increased to allow records to more than 300,000.
  • Error Code F5328B32 could occur when the SPLIT function was used on joined CSV files in a relationship.
  • Starting with version 2020.4.0, the second page of an exported landscape PDF could be zoomed in to not match the scale of the first page.

New in Tableau Reader 2020.4 (Dec 15, 2020)

  • Resolved Issues:
  • CEILING() function could return incorrect results when using a scalar or a constant as the argument.
  • Creating an extract from an OData connection could fail after navigating to a worksheet.
  • "Error code: 6EA18A9E. Unable to create extract" could occur with text files when selecting a merged mismatched field as a matching field between two logical tables.
  • A table calculation could disappear from the view after the data source was published to Tableau Server.
  • In the Relationship dialog, when a linking field was changed from an integer to a string, the dialog displayed the correct type but the query used the original data type which could result in a "type mismatch" error.
  • The Data Quality Warnings would not refresh for a workbook if the data source connection is opened or a workbook with the connection is opened before signed into Tableau Server.
  • The calculated field set in a title of a Viz is displayed as "All" when using a discrete date dimension for a table across or table down calculation.
  • When a workbook contained a file union, any subsequent workbook open attempts could fail because the column name would not exist in the data source due to a language translation.
  • An error would occur stating, "Invalid SET statement in the triggered action," when an attempt to connect to Teradata with a username that contained an apostrophe was performed.
  • It was not possible to edit an axis range of a continuous bin when the range is fixed to set either the fixed start or fixed end to a decimal number.

New in Tableau Reader 2020.3.3 (Nov 23, 2020)

  • Resolved Issues:
  • Using the MSAS 15.1.x driver, an error would occur when dragging any field into the view, "Error Code A7AE04D2. Unknown error communication with the data source
  • (COM 0xC1010000)."
  • The MIN() function added in the query causes performance degradation since 2020.2.0.
  • 1164363
  • Tableau Desktop installation property DRIVEDIR did not work as expected.
  • "Initial Connection : Hyper : Failed to start a new hyper instance. AssignProcessToJobObject() failed.: Access is denied" would display when creating an extract on Citrix XenApp.
  • Oracle error "ORA-01424: missing or illegal character following the escape character", would sometimes display when dragging a table to the canvas.
  • The "Sort Field" menu bar would sometimes disappear on the data source page after navigating from worksheet to data source page.
  • 'Getting data from server' pop-up window would sometimes display when trying to edit a Calculated Field.

New in Tableau Reader 2020.3.1 (Oct 1, 2020)

  • Resolved Issues:
  • In a dashboard action, settings were not correctly saved when a worksheet name ended with a "" character.
  • Table names beginning with a number were displayed as a letter on the data source pane when connected to Google BigQuery.
  • Error 6EA18A93 would sometimes occur when joining unioned tables.
  • The error, "Type doesn't match expected type" would sometimes occur when changing a quick filter using Animations.
  • The auto field improvement to remove underscores would sometimes not work.
  • The Schema list was not in order when connected to Amazon Redshift.
  • In a logical join with a flat file, dragging measures from the CSV table to the view could cause a collation mismatch error.

New in Tableau Reader 2020.3 (Aug 12, 2020)

  • Resolved Issues:
  • Joining two data sources, performing a pivot, and then aggregating one of the resulting measure fields would sometimes result in an error, "Failure parsing: No such column [{name}]."
  • In some cases, Tableau would fail to create an extract when you extracted a data source with cross-database joins containing a spatial file.
  • The Pages shelf date counters would sometimes not advance with animations enabled.
  • When a workbook uses a published data source along with other secondary data sources, and two parameters from different data sources have the same internal names, Tableau would sometimes return incorrect cached results
  • Dynamic Parameters using aliases would sometimes display the warning message, "The 'calculation' value is not in this parameter's list of values" despite meeting the necessary criteria.
  • Syntax errors occur when refreshing data using custom SQL where newlines are removed from the query.
  • A Manual sort would not work correctly after Auto Updates was paused.
  • OData extract refreshes would fail after the update to version 2020.2 if the Odata server name contained a blank space.
  • The function editor tooltip for RANK_DENSE would show "Ausdruck" instead of the expression if the language was previously set to German.
  • Refreshing a data source and viewing the visualization as the same user would sometimes lead to a data mismatch between the visualization and a parameter.
  • A "DataServiceFailure" error or "insufficient privileges to operate on schema" sometimes occurred when trying to refresh or open a workbook with a published Snowflake connection.
  • An LOD calculation that references another calculation containing a constant would sometimes have a different result after a data source was published.
  • Singapore postal code 388402 was not recognized.
  • View containing Rank_Unique appeared different in Tableau Public than in Tableau Desktop.

New in Tableau Reader 2020.2.4 (Jul 31, 2020)

  • Resolved Issues:
  • The use of Double Precision with a SharePoint List caused a "Malformed SQL Statement" error.
  • When connecting to Tableau Online or Tableau Server, "Error Code: 9F4C5638
  • Internet communication error: SSL connect error" would occur using Tableau Desktop 2020.2.2.
  • It would sometimes not be possible to publish or create an extract when making a Relationship on a pivoted value. Error: "Unable to complete action. An error occurred when publishing the workbook. Error Code: 6EA18A9E Internal Error - An unexpected error occurred and the operation could not be completed."
  • The date and time of 1899/12/30 12:00:00 AM was not handled correctly as a fixed start of the axis range.
  • When a join with Salesforce tables was created using one of the tables twice, fields hidden in the first instance of the table were also hidden in the second table after creating an extract.
  • View filters disappeared after renaming a field in a database and replace references was performed.
  • When the Teradata driver was loading, a possible crash was experienced due to a race condition with the driver.
  • The create extract and preview join data window would sometimes be unresponsive with the 'loading' status when a spatial file was joined with a CSV file.
  • User calculations and parameters with fixed precision numbers would sometimes not return the correct results from the database.
  • Schema name list was not in order when connected to Amazon Redshift.
  • An LOD calculation that references another calculation containing a constant would sometimes have a different result after a data source was published.
  • In some cases, it was not possible to refresh subscription keys before the expiration date occurred.
  • The following error would sometimes occur when importing custom geocoding: "Unable to complete action. Internal Error - an unexpected error occurred and the operation could not be completed. Error code: 6EA18A9E"

New in Tableau Reader 2020.2.2 (Jun 24, 2020)

  • Resolved Issues:
  • When an English workbook with Union Data is opened in Non-English Tableau Desktop versions 2020.1 and over, there are added Non-English translation of 'Sheet' and 'Table Name' fields added to the Union resulting in "Unknown Column Error"
  • Sometimes when using Explain Data, the error, "unable to poll port number of Yaxcatd" would occur.
  • Selecting "Update Now" with a grouped Dimension when using Quickbooks Online resulted in the error: 6EA18A9E.
  • The RANK_DENSE function tooltip would sometimes show "Ausdruck" instead of the correct expression when the German language was previously set.
  • When publishing to a Tableau Server Site with more than 3,000 projects, not all projects displayed.
  • Using a published Spatial file and an action filter from one dashboard to another dashboard, the resulting map displayed no data when the secondary dashboard used a different primary data source.
  • Nested calculation execution time increased with some visualizations.
  • SAP BW extract refresh would sometimes fail due to a timeout limit.
  • Some of the regions of Ghana were not recognized.
  • Using Tableau Desktop command line tool to refresh extracts "tableau refreshextract" sometimes resulted with "Internal error"
  • SAML SSO sometimes failed with the following error "ERROR 6: SSL handshake failed".

New in Tableau Reader 2020.2.1 (May 29, 2020)

  • Resolved Issues:
  • Loading certain published views resulted in the error "LogicException: Internal Error - An unexpected error occurred and the operation could not be completed.
  • Internal Error - An unexpected error occurred and the operation could not be completed.
  • Unable to calculate the sort for the field .... The display may not show correct data.
  • LogicException details: LogicAssert at ../../../modules/platform/tabquery/main/query/provers/FoldableNullCheckQueryProver.cpp line 168: leftOut.size() == 1 || rightOut.size() == 1"
  • In some cases, data source fields changed folders or folders disappeared after the data source was published.

New in Tableau Reader 2020.2.0 (May 28, 2020)

  • Resolved Issues:
  • When using the DATENAME function with the quarter option in Tableau Desktop and with a live connection to an Exasol database, the incorrect quarter is displayed.
  • When connecting to Amazon Athena, views did not display in the connection window.

New in Tableau Reader 2020.1.3 (Apr 30, 2020)

  • Resolved Issues:
  • In Tableau Desktop 2019.2.4, when publishing a dashboard that is using multiple CSV files as its data source, irrelevant CSV files within the same folder are unexpectedly packed into the .twbx file.
  • Workbooks connected to an Oracle union that included NCLOB fields gailed to load with the error "Internal Error - An unexpected error occurred and the operation could not be completed"
  • Data sources with the same name in different projects were missing from the "Edit server and site path" drop down list.
  • Presto, Qubole and Redshift tables that were renamed to have upper case or initial capitals reverted back to lower case.
  • It was not possible to enter the letter "t" in a password field inside a web object on a dashboard.
  • No data displayed in the Search For Data window when connected to Tableau Server from Tableau Desktop.
  • When using a group based on a field in a file joined to a relational data source, the error "Unable to complete action. No such table: Error Code: 353FBC8D" sometimes occurred.
  • In Salesforce custom SOQL, greater than ">" or less than "

New in Tableau Reader 2020.1.2 (Apr 1, 2020)

  • Resolved issues:
  • Joining an extract and Excel file sometimes resulted in the error "extract 0 collation mismatch, use COLLATE statements to resolve" when using Japanese OS locale.
  • Tableau Desktop Data Interpreter does not work on CSV files with file length of 26 Character or more.
  • NULLS remained at the top of the viz when using a nested sort, whether ascending or descending sort was selected.
  • When connecting to Excel and Google BigQuery in a same connection, using a ROUND function will result in the following error: "ROUND is being called with (float, integer), did you mean (float)?"
  • Error Code 8B31AE48 sometimes occurred when attempting to enable Show Empty Columns.
  • When there are fields with the same names in an existing data source, then adding another data source to canvas and selecting "Create Join Calculation", will result in the following error, "Internal Error - An unexpected error occurred and the operation could not be completed."
  • When connecting to Excel and Google BigQuery in a same connection, then using the ROUND function, the following error occurs, "ROUND is being called with (float, integer), did you mean (float)?"
  • Shapes in maps have changed since upgrading from version Tableau 10.3 to 2019.2 in both desktop and server.
  • When loading a Geojson (Spatial connector), "unable to create unit vector from zero-length vector" error is returned.
  • Tableau Desktop 2019.1 crashes every time after activation, if Virtual Desktop Support is enabled. It works well after being re-launched.
  • Maps of Norway still showed 18 Norwegian counties rather than the current 11.

New in Tableau Reader 2020.1 (Apr 1, 2020)

  • The Linkedin Sales Navigator connector failed to connect when Tableau Desktop was set to English (UK), Italian, or Traditional Chinese.
  • District boundaries for Hong Kong did not render as expected.
  • "Export to Excel" did not preserver number formatting when a percentage format was used.
  • Actian Vector connector did not support creating temp tables.
  • Attempting to connect to QuickBooks Online would fail and users would be redirected to a QuickBooks Online Blog post.
  • Parameter Action did not trigger when clicking dimension value that has NULL measure value.
  • Logarithmic axis with an automatic minimum and fixed maximum sometimes displayed marks in an unexpected position.
  • The error "There is no active connection to the data source" occurred intermittently when refreshing data sources using JDBC.
  • Switzerland postal codes 01011, 03010, 03801, 04031, 04101, 0504, 06039 and several postcodes starting with 09 were not recognized by Tableau Desktop.
  • Menaka and Taoudenit regions were missing from maps of Mali.
  • From Tableau Desktop, when selecting Tableau Server on the data source page to connect to a published data source, one or more published data sources were missing and/or could not be used.

New in Tableau Reader 2019.4.2 (Jan 24, 2020)

  • Resolved Issues:
  • When connecting to CSV files from a Dutch locale version of Tableau Desktop, initially 'comma' is not recognized as a field separator. After selecting any other character and then changing it back to comma, everything works as expected. The issue does not occur when using a different locale, for example English (Ireland).
  • Zip code 60686 was mapped in the incorrect location.
  • Confusing registration file warning message, "Unable to flatten service registration info, because there is no registration file." needs no action from users setting configuration using TSM.
  • Arbitrary 10k limit for SSL certificate chain file upload causes this error, "External SSL Configuration Error: The file 'intermediate_longer.cert' exceeds the maximum allowed size of '10.240' bytes."
  • If there is an increase in settings like nprocs and other process limits on a Linux system running Tableau, then there should be an increase in kernel.pid_max and vm.max_map_count to avoid native thread errors.
  • Embedded views failed to load after updating to Chrome 80. For more information and solutions, see this KB.
  • After exporting a workbook to PowerPoint, apostrophes " ' " in the workbook name were encoded as "'".
  • Redshift extract creation failed without any error message if a query was cancelled by the database.

New in Tableau Reader 2019.4.1 (Dec 20, 2019)

  • Resolved Issues:
  • Tableau Desktop 2019.4.0 does not recognize the following 3 Japanese cities: 1. 丹波篠山市 (Tamba-Sasayama, Hyōgo)- city changed its name from 篠山市 to 丹波篠山市 in May 2019. 2. 標津町 (Shibetsu-chō, Hokkaido) 3. 那珂川市 (Nakagawa, Fukuoka)- city founded on October 2018, from 筑紫郡那珂川町.
  • All Tableau releases have been upgraded to JDK 8 to minor version 232 GA.
  • DataServer data source with default sort created and published in Tableau Desktop 2018.1, but when this data source is used with Tableau Desktop or Web Editor, then saved to a server that is > 2018.1 the default sort is not respected.
  • Filtering a view based on an extract at the quarter level sometimes filtered all data from the view.
  • On a live site: extract refresh succeeded, then seemed to fail, but in fact did succeed and recorded new versions of everything in postgres, before deleting the new extracts so workbooks point to nowhere.
  • In MacOS Mojave dark mode, significant UI text is missing in the Data pane, Analytics pane, and Save dialog when exiting.

New in Tableau Reader 2019.3.1 (Oct 29, 2019)

  • Opening a workbook and activating Tableau Desktop at the same time sends authentication request to data base with empty password.
  • Internal unexpected error occurred and the operation could not be completed while editing groups on a Mac and using "Find Next".
  • After connecting to Salesforce and then trying to edit the data source in a workbook, the error "No such function == that takes arguments of type (str, str)" appears.
  • PDFs used in a union showed as red in the Union dialog and the OK button was grayed out.
  • When dragging a pie chart label in Tableau Desktop 2019.2.2, the label jumps to a different position when dropping it. The issue does NOT occur in 2019.2.1.

New in Tableau Reader 2019.3 (Oct 29, 2019)

  • Resolved issues:
  • Built-in 2019.1 geocoding is incorrect for zip codes in Texas (76244 - 76248).
  • Unexpected data sometimes displayed in the view if USERNAME() was used in a join.
  • Opening a packaged workbook in 10.5 format crashes Tableau Desktop 2018.3 with infinite loop of interactions between Aggregate_Canonicalize and Join_ProjectInline causing stackoverflow.
  • Salesforce extract refresh failed with authentication failure when using saved credentials.
  • Incorrectly mapped Mexico zip codes are not showing the correct location for the range 250xx - 279xx.
  • "Wrap: Off" truncates by line in multi-line text in 10.5 and earlier, while the entire text block is truncated in 2018.1 and later.
  • Michuhol District is a municipal district in Incheon, South Korea, was incorrectly showing as Nam-gu (an outdated name) on Tableau maps.
  • When you saved a view based on an extract after filtering to a single value and closed the workbook, the view was sometimes unexpectedly blank after reopening.
  • Calculations using DATEPART('second') returned unexpectedly rounded results in some cases.
  • When a view contained a reference line on Table computed on Median and set to "Line only", and all quick filter values were unchecked in any quick filter on the view, the workbook closed unexpectedly.

New in Tableau Reader 2019.2.3 (Aug 23, 2019)

  • Resolved Issues:
  • When you saved a view based on an extract after filtering to a single value and closed the workbook, the view was sometimes unexpectedly blank after reopening.
  • Requests for mapsconfig.tableau.com were sent through http:// and not https://
  • Maps including Russia had missing countries when exported to .emf format.
  • After setting the width and height of a dashboard object, clicking into the view sometimes resulted in an "Internal Error" message.
  • Some error and dialog boxes appeared black or transparent on Citrix.
  • Calculations using DATEPART('second') returned unexpectedly rounded results in some cases.

New in Tableau Reader 2019.2.2 (Jul 25, 2019)

  • joined with an Excel sheet.
  • When joining tables from MySQL and Oracle, the error: "Collation mismatch, use COLLATE statements to resolve" could appear.
  • Web Data Connectors and other browser-based sign in windows sometimes did not render correctly.
  • In a dual axis bar chart, the background bar sometimes could not be selected.
  • Sometimes connecting to SAP HANA took longer than expected after upgrading to 2019.1.
  • When you ran a menu action to filter a target sheet, selecting a mark in a non-target sheet would clear the original action selection resulting in the target sheet becoming blank.
  • In large environments where usernames contained a backslash () character, editing a user filter sometimes caused the filter to become invalid and resulted in a blank view.
  • When you were republishing a workbook or data source connected to a Hive-based database using Microsoft HDInsight authentication, an "Invalid username or password" error would occur indefinitely if you did not enter database credentials correctly when prompted during publishing.
  • When you used Data > Refresh all extracts with an OData extract using Username/Password authentication, there was no prompt for credentials which caused a login failure.
  • When converting datetime to string, minute portion returned incorrect value. We were using MM instead of MI for the minute portion of our TO_CHAR function to SNOWFLAKE.

New in Tableau Reader 2019.2.1 (Jun 26, 2019)

  • Resolved Issues:
  • It was not possible to drag and drop when screen sharing using BlueJeans.
  • Signing in to Tableau Server from Tableau Desktop via Smart Card failed with an "Your Smart Card or SoftPKI Certificate could not be recognized" error.
  • When using DATETIME function in Google BigQuery custom SQL on a field which used milliseconds data, the value returned as #Error or null.
  • When using Teradata driver version 16.20 or higher, initial SQL containing command statements failed to execute.
  • In Tableau Desktop, when you tried to navigate to a child project that had the same name as its parent, the workbooks from the parent project displayed instead.
  • Sometimes background formatting changed unexpectedly when upgrading workbooks from 2018.1 to 2018.2 or newer versions.
  • When viewing a sheet which uses forecasting with a fiscal year start date set, sometimes an "Invalid Vector Subscript" error occurred.
  • The Denodo connector sometimes failed to recognize the driver.

New in Tableau Reader 2019.2 (Jun 26, 2019)

  • Resolved Issues:
  • When using later versions of Tableau Desktop, maximum DATETIME()or MAKEDATETIME() from SQL Server is null whether using YEAR([date]) or exact date.
  • Box & Whisker formatting option appears incorrect in UI. (This is a cosmetic issue that does not affect the viz/data but causes some confusion.)
  • Published live Excel data source with join does not update data during Refresh in neither Desktop nor Server.
  • When editing an axis to have an automatic start and a fixed end, marks are rendered in incorrect places. Affects Tableau Desktop 2018.1 and later.
  • Maintenance updates made to the Salesforce connector.
  • When a view has a reference line on the Table computed on Median and is set to "Line only", and all quick filter values are unchecked in any quick filter on the view, the workbook crashes.
  • Live connections using a Custom SQL query to SAP HANA experienced performance issues due to multiple metadata queries.
  • Multiple errors such as "Unable to connect" or "Malformed response" would sometimes occur when connecting to a published data source which had been configured to prompt the user for credentials via OAuth.
  • Map borders for Norway, Sweden and Finland display incorrectly when using NUTS codes.
  • Attempting to connect to Progress OpenEdge with drivers newer than 11.1 installed resulted in a prompt to download and install the drivers.
  • Tableau Desktop did not display SAP Hana input parameters that were created in SAP Web IDE.
  • When refreshing a Marketo extract, sometimes an "An unrecoverable error occurred" message occurs.

New in Tableau Reader 2019.1.3 (Apr 24, 2019)

  • Resolved Issues:
  • Unexpected error occurs when clicking on sort icon if horizontal scrollbar cursor is not at leftmost position.
  • Error "type doesn't match expected type" occurred when changing the value of a filter.
  • Invalid queries are generated when filtering on a Fixed LOD calculation in workbooks connected to Hana.
  • Error "Unexpected Server Error" sometimes occurred when accessing a workbook containing an empty extension.
  • When scope for a reference line is set to Entire Table, the panes with null values are skipped.
  • Fields used in "Measures Values" can in some conditions scale improperly.
  • When using a table calculation in two different places (pills or shelves) in a viz, the error, "No such column" appears."
  • Selecting a table while connected to Tibco Data Virtualization 8.0 results in an error message.
  • The sc_item_option_mtom table was not available from the ServiceNow ITSM connector.
  • sys_choice and related tables were missing from the ServiceNow ITSM Connector.
  • Tableau Desktop was unable to connect to certain .sas7bdat statistical files, user receives 'Unable to lead Metadata' error.

New in Tableau Reader 2019.1.2 (Mar 27, 2019)

  • Resolved Issues:
  • Unable to see views in Tableau when connected to Hortonworks Hive 3.1.
  • Tableau 2019.1 geocoding FDB is missing the entry for the county of Waterford in Ireland.
  • 16 NUTS3 2016 codes for the UK are not recognized in Tableau Desktop.(NUTS3 means Nomenclature of Territorial Units for Statistics level 3 used by Eurostat and other European Union bodies.)
  • Background Map Data for Namibia displayes labeling and mapping inaccuracies between the current region names and the pre-2013 region names.

New in Tableau Reader 2019.1.0 (Feb 13, 2019)

  • Resolved Issues:
  • Errors are displayed, when visiting the Extensions Settings Page, and the Extension zones are blank when a viz is rendered.
  • After optimizing an Oracle extract, the extract could not be refreshed and an "Invalid field formula due to limitations in the data source" error occurred.
  • When you dragged an Exasol string field which has a size of 131072 or greater into the view, the length of the string was truncated to 15.
  • When all values were deselected in a filter and a reference line was present on the view, an "No value found at key RefLines" error occurred.
  • Selecting a mark to highlight and changing filter selections sometimes resulted in the wrong measures being highlighted.
  • With a table calc an reference line in the view, nested sorting failed with a "No such column" error.
  • When using a fixed logarithmic axis, values in the view did not scale correctly.

New in Tableau Reader 2018.3.3 (Feb 1, 2019)

  • Resolved Issues:
  • When all values were deselected in a filter and a reference line was present on the view, an "No value found at key RefLines" error occurred.
  • When using a calculated field that depends on a field whose data type has been changed, sometimes an "ERROR: collation mismatch, use COLLATE statements to resolve" error occurred.
  • When using an aggregated extract, if you changed a measure to a dimension and then refreshed the extract, the values did not update.
  • Date fields showed the wrong year when system locale was set to Thai.
  • You were unable to bold text in Tableau Desktop on Mac OS Mojave.

New in Tableau Reader 2018.3.2 (Dec 21, 2018)

  • Resolved Issues:
  • Continuous date formatting options did not appear in the context menu for date filters.

New in Tableau Reader 2018.3.1 (Dec 6, 2018)

  • Workbooks with heatmaps become unable to be opened after switching a density mark color to a non-default color palette, then switching off density mark type.
  • Extracts created via the Anaplan connector were sometimes missing rows of data.
  • The sign-in dialog for creating connections on a dashboard is garbled/overlapped when viewing in IE 11.
  • When using a fixed logarithmic axis, values in the view did not scale correctly.
  • In Tableau 2018.3, sometimes maps using custom polygons appeared distorted, inverted, or rendered as a single color box.
  • When adding a data source filter to an extract with multiple tables storage, the following error will occur: "Unable to create extract." This error message is incorrect and should be disregarded; the extract can now be created correctly.
  • 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.

New in Tableau Reader 2018.3 (Dec 6, 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 Reader 2018.2.3 (Oct 17, 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."
  • When using a high resolution image as a background image in Tableau Desktop on a MacBook Pro with a Retina Display, the text on background image was distorted.
  • After creating a SAP BW extract in Tableau Desktop 10.5.4 and earlier versions, and then refreshing this extract in 10.5.5 or later versions, the date fields in the extract break: all dates are either showing as NULL, "30/12/1899" or similar. The date fields in SAP BW are of type "DATS".
  • When trying to connect to Hortonworks Hadoop Hive, sometimes an "[Hortonworks][Hardy] (34) Error from server: SSL_connect: certificate verify failed" error occurred.
  • When you clicked "Describe" on a calculated field, sometimes an "A query error occurred. No description available" error occurred.
  • "tableau.exe -register" command fails when the previous GUI registration was configured with a Country different than US in the Country Section.

New in Tableau Reader 2018.1.0 (Apr 24, 2018)

  • Resolved issues:
  • 737967: Views did not update with new data after performing an incremental extract refresh in Tableau Desktop.
  • 722607: In some cases, when connected to Amazon Redshift, using a calculated field containing a DATEDIFF function would result in an error: Invalid operation: Overflow or underflow for DATEPART/EXTRACT 'epoch'
  • 725088: Extra spaces in Initial SQL statements for Teradata could sometimes cause an error: Data definition not valid unless solitary
  • 714359: The layout of filters in a dashboard could be compressed if the dashboard was initially loaded when in presentation mode.
  • 697356: Extract refreshes using Tableau Bridge could intermittently fail with an error: Your connection has probably timed out. Try to reconnect to Tableau Server.
  • 682023: Refreshing an Amazon Athena extract using the Data > Refresh All Extracts menu option would fail because it did not prompt for database credentials
  • 680287: Referencing a level of detail calculation, containing a DATETRUNC or DATEPART function, in another level of detail calculation could result in an error: No such column [＿dimension＿N]
  • 681797: Highlighters would be removed when replacing data sources.
  • 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.
  • 740884: In environments requiring proxy authentication for internet access, Tableau Desktop would sometimes crash after entering proxy credentials.

New in Tableau Reader 10.5.2 (Mar 9, 2018)

  • Resolved Issues:
  • 735850: Hyper processes could repeatedly go down in environments running on a CPU that did not support the SSE3 instruction set.
  • 736466: In Japanese language environments, filter selections could change when opening a pre-10.5 workbook in Tableau Desktop 10.5 or 10.5.1.
  • 731028: When connected to Sybase IQ, strings containing special characters were not rendered correctly.
  • 731531: Changing the formatting of a continuous date field would cause vertical grid lines to disappear from the view.
  • 729054: Connecting to some Microsoft SQL Server stored procedures using Tableau Desktop 10.3.6, 10.4.2, or 10.5 and higher would fail to return data.
  • 728027: When you connected to text files using a legacy connection and custom SQL, it was not possible to change the text file properties.
  • 730469: Dimension members containing the "
  • 728816: Data sources published to Tableau Online, containing a live connection to a stored procedure maintained using Tableau Bridge, would fail with a syntax error.
  • 733366: When performing a cross-database join involving a legacy Excel connection, and error would occur: collation mismatch, use COLLATE statements to resolve

New in Tableau Reader 10.5.1 (Feb 19, 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.
  • 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.
  • 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.
  • 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.
  • 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.

New in Tableau Reader 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 Reader 10.4.1 (Nov 14, 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.
  • 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.
  • 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.
  • 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 Reader 10.2.0 (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 Reader 10.1.4 (Jan 25, 2017)

  • Fixed issues:
  • 594324: 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.
  • 585934: Small decimals would sometimes appear as "null" in the data preview pane or show "#Error" when added to a view.
  • 597583: Updated Google BigQuery connections to utilize the REGEXP_CONTAINS function when REGEXP_MATCH is called.
  • 586941: When connected to Microsoft Analysis Services, running a filter actions would sometimes cause Tableau Desktop to become unresponsive.
  • 598348: 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.
  • 593435: 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.
  • 595505: 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.
  • 507752: 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.
  • 596100: Tableau Desktop would sometimes crash on Macs running macOS Sierra with integrated Intel graphics.
  • 569646: When you created a cross-database join involving a table with a back slash in its name, a Tableau Data Engine error would occur.
  • 571052: 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.
  • 599908: 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.
  • 572435: 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.
  • 585492: It was not possible to union comma-delimited text files in locales where commas are used as decimal separators (e.g. German).
  • 586496: Running filter actions could sometimes be significantly slower when compared to prior versions.
  • 587412: In some cases, deselecting filter actions did not behave as expected.
  • 583951: In some cases, excluding a mark more than once could change an associated filter from an include filter to an exclude filter.
  • 583960: In some cases, opening a workbook created in Tableau 9.1 in a newer version of Tableau Desktop would result in an internal error.
  • 591675: When connected to Google BigQuery, converting a string, containing a decimal character, to FLOAT would result in a "Bad int64 value" error.
  • 585144: 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.

New in Tableau Reader 9.3.4 (Jul 13, 2016)

  • Fixed issues:
  • 513320: Creating or refreshing an extract of a file-based data source that had been pivoted would sometimes fail to complete in Tableau Desktop.
  • 496828: In some cases, workbooks created in older versions of Tableau Desktop could not be opened in Tableau Desktop 9.3.
  • 517597: In Tableau Desktop, you could not connect to a single row text or Excel file with no column headers.
  • 520558: Web data connector performance was slow in Tableau Desktop for some international system locales.
  • 519992: It was not possible to type Japanese or Chinese characters in Tableau Desktop when searching for fields to add to a join clause.
  • 526589: In Tableau Desktop, custom geocoding hierarchies were not displayed correctly as sub-menus in the Geographic Role context menu.
  • 530123: Workbooks connected to Amazon Redshift would intermittently fail to load if a prior load had failed or was cancelled.
  • 523361: When you connected to Oracle in Tableau Desktop, some Unicode encoded data did not display correctly.
  • 525693: Toggling the 'Show Apply button' option for multiple values filters, and then saving the workbook, failed to remember the last toggled setting when the workbook was re-opened in Tableau Desktop.
  • 526662: 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.
  • 528130: In some cases, Tableau Desktop would fail to launch due to an issue with automatic sign-in to Tableau Server.
  • 489737: In Tableau Desktop, when you exported a sheet as a crosstab to Excel, an error would occur in certain cases: "Unable to calculate the sort for the field ''. The display may not show correct data".

New in Tableau Reader 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 Reader 9.3.0 (Apr 5, 2016)

  • New Capabilities:
  • This release adds a new connector that gives you the ability to connect to Snowflake Elastic Data Warehouse.
  • Corrected Issues:
  • In addition to the new capabilities, the following issues that were reported to us in prior releases have been corrected.
  • Tableau Desktop:
  • In Tableau Desktop, Texas zip codes 79781 and 76880 were incorrectly mapped.
  • In Tableau Desktop, Manhattan zip codes 10162, 10174, 10175, and 10176 were incorrectly rendered in Brooklyn.
  • In Tableau Desktop, when connected to an SAP BW data source, filtering out null values also incorrectly filtered out zeros.
  • In Tableau Desktop, the filled map polygon for zip code 10271 was not correctly placed.
  • In some cases in Tableau Desktop, adding a sheet to a dashboard resulted in an internal error.
  • In Tableau Desktop, certain workbooks created prior to version 9.0 performed worse when opened in newer versions due to changes in query generation.
  • In Tableau Desktop and Tableau Server, Oglala Lakota county (previously Shannon county) in South Dakota wasn't recognized in geocoded views.
  • In Tableau Desktop, the calculation dialog example for the DATE() function used a date format uncommonly recognized by many databases.
  • In Tableau Desktop and Tableau Server, the Japanese translation of the count distinct abbreviation (CNTD) was incorrect.
  • In Tableau Desktop, when you created a local copy of a published data source, an internal error sometimes occurred.
  • In some cases in Tableau Desktop, filter actions used to navigate between dashboards took users to the wrong dashboard.
  • In Tableau Desktop, Tableau Online, and Tableau Server, incremental extract refreshes via command line or the Tableau Online Sync Client were incorrectly run as full extract refreshes.

New in Tableau Reader 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 Reader 9.2.5 (Feb 26, 2016)

  • Corrected Issues:
  • In addition to the new capabilities, the following issues that were reported to us in prior releases have been corrected.

New in Tableau Reader 9.2.4 (Feb 6, 2016)

  • 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 Reader 9.2.0 (Dec 8, 2015)

  • In Tableau Reader, a user could change a quick filter type.