Softpedia >Windows >Internet >Servers >Other Servers >Tableau Server >  Changelog

Tableau Server Changelog

What's new in Tableau Server 2023.3.4

Mar 27, 2024
  • W-14411304 When a parameter with string value is added to the URL of a Web Page object, a strange error ""%3Cparameters.url%3E’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 Server 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 Server 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 Server 2023.1.2 (May 18, 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 Server 2023.1.1 (Mar 29, 2023)

  • Tableau Server and TSIG upgraded to Apache httpd 2.4.56.

New in Tableau Server 2023.1.0 (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."

New in Tableau Server 2022.3.4 (Feb 23, 2023)

  • Support for Linux Ubuntu 20.04 has been added.
  • Minimized the response of an internally used data source connection REST API call.
  • If subtraction using the FIND function is specified as the third argument of a MID function, the flow cannot be opened.
  • An unexpected error would occur when a non-Server Administrator would try to change the run-flow task priority.
  • For task type subscriptions, the count of tasks was incorrect on the Schedules page when a particular schedule had more than zero subscriptions.
  • Tableau Server Site Administrators could force password updates for Server Administrators.
  • With an Azure DB accessed using Active Directory (AD) credentials, if "Remember Password" was selected and the password changed in AD, the view would error out instead of prompting the user to re-enter the password.
  • Tableau Server could be degraded because the Prep Cores were incorrectly applied to nodes that were not set for the flow-only configuration.
  • In a multi-node cluster, Data Management flow subscriptions would intermittently fail and not contain the data attachment.
  • In the Schedules menu when selecting a specific flow that contains Tasks, the schedule opened would report there are no flows.
  • With the Core license type activated, it was not possible to keep both Explorer and Viewer values at 99999999 in the Site Role Limit setting.
  • The Explorer role (that can publish) would not allow the publishing of flows to Tableau Server.

New in Tableau Server 2022.3.3 (Jan 26, 2023)

  • Resolved Issues:
  • Alias for a calculated field value reverts to default when removing and re-adding a data source table.

New in Tableau Server 2022.3.2 (Dec 15, 2022)

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

New in Tableau Server 2022.3.1 (Nov 17, 2022)

  • 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 Server 2022.3.0 (Oct 19, 2022)

  • Fixed:
  • 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 Server 2022.1.7 (Sep 29, 2022)

  • Resolved Issues:
  • Part of a dashboard could become blank and an error would display after applying filters stating "Cannot read properties of undefined (reading '0')"
  • It was not possible to authenticate against Azure when implementing Azure KMS via the "tsm security kms set-mode azure"
  • After an upgrade from 2020.3.6 to 2021.4.6, pdf exports with a view filter returned incorrect data when using the REST API intermittently
  • An error could occur when changing the parameters in a dashboard stating "Unexpected Error. Uncaught RangeError: Maximum call stack size exceeded."
  • Server Administrators were not receiving bell notifications for other users extract refresh failures
  • When an http_request_id_seq exceeds 2,147,483,647, the error "integer out of range" would occur and the http_request table would not be updated
  • Headers can retain font color when exporting to an Excel file format which can render the label to not be visible if a white font color was used
  • Running "tsm maintenance cleanup -a" stopped users from being able to download or export content once the server was running again
  • In mobile browsers, when the filter was reset, the view would update to default data but the filtered parameter drop-down menu option is not reverted back to the reset values
  • A custom number format in an axis scale would sometimes not be used after publishing to Tableau Server
  • When the "--multithreaded" parameter was used to create a new backup schedule, the parameter was being ignored
  • When a worksheet was opened that used a published data source, hyperd.exe could consume 100% CPU usage
  • Prep Flows actions can intermittently fail beginning with Tableau Server version 2022.1.4. Actions include creating a new flow, editing an existing flow, or running a published flow

New in Tableau Server 2022.1.5 (Aug 31, 2022)

  • Addressed an issue in Tableau Server Administration Agent.
  • "An unexpected error occurred on the server" would display when logged into one site then loading an embedded view from a different site.
  • Published Virtual Connection extracts can go missing on a workbook causing load errors.
  • The Tabcmd export or get command could return cached results intermittently even using the parameter ":refresh=yes".
  • An error, "OAuth access token expired", could occur when running a Tableau Prep flow transferring data to Snowflake.
  • The REST API will fail with a "500" error when querying data source lists over 10,000.
  • Tabcmd export to a PNG file encodes the URL from "%" to "%25".
  • The REST API schema definition of "SiteType" was missing from the "selfServiceScheduleForRefreshEnabled".
  • The Apply button can be missing from set filter when no values are present.
  • Clicking on the sort button could cause an exception error with client side rendering when the sort indicator didn't fit in the axis header.
  • Tableau Server configured in a multi-node configuration may fail to back up successfully on 2021.4.7 and 2022.1.2 if the Data Management Add-On is not being used. The error would occur as follows: "BackupRestoreException(message:ProxyClient was unable to find a gRPC channel to the service 'extract_service' as required by class 'com.tableausoftware.domain.extractdata.grpc.IExtractServiceMaintenanceGrpc'."
  • When "Manage all Sites" was selected and the "Tasks" reviewed, the Flows tab when selected, would drop the flows count to zero and report that "There are no flows with scheduled tasks." Flows listed under Tasks at the site level would work correctly.

New in Tableau Server 2022.1.3 (Jun 22, 2022)

  • 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 Server 2022.1.2 (May 25, 2022)

  • Resolved issues:
  • In some circumstances, top-level projects in Tableau Server would be in an illegal state making it impossible to update the project's lock status or permissions via the Tableau Server REST API.
  • Null values could appear in a workbook containing an Excel data source after being published to Tableau Server on Linux.
  • 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".
  • The dashboard action filter for navigating to a secondary dashboard would sometimes not work correctly after selecting a row starting in version 2021.1.0 and newer.
  • The axis label would sometimes not render correctly on 2021.1.0 or newer when using client-side rendering.
  • Selecting filter values on a view could cause the view to become unresponsive and the Chrome browser to produce the "Aw, Snap!" page.
  • When using web authoring and connecting to data, the wrong table could be displayed when dragging a table onto the data pane.
  • It was possible to publish a data source with an identical name as a data source already residing in the project.
  • Desktop license reporting could not save localized registration date values and data displayed as NULL.
  • Server ATR activation preflight check failed during initialize-tsm when installed in forward proxy environments. The response would return "ERROR: TSM services returned status 100."
  • It was not possible for another Creator user to overwrite a published Virtual Connection.
  • Adding a map layer with blended data could result in an error code D9151F7B.
  • The Kanji character was incorrect when using the Workbook Optimizer.
  • In Tableau Server 2022.1.0 when a local identity store was used, user login could fail due to case sensitivity in the username. More information available in this Tableau Knowledge Base article.
  • Deploying a new Coordination Ensemble in Tableau Server 2022.1 will result in a failure.
  • When accessing the background tasks for non-extracts admin view, the user would sometimes see a repeating failing job for simple object storage reconcile job.

New in Tableau Server 2022.1.1 (Apr 23, 2022)

  • 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 Server 2022.1.0 (Mar 31, 2022)

  • Resolved Issues:
  • The relative date filter would sometimes not localize correctly.
  • Row divider borders would sometimes render differently than expected.
  • After publishing a viz to Tableau Server, row labels in table calculations would sometimes not display correctly.
  • If the end changed versions from Tableau Server 2021.4 to Tableau server 2022.1 and then downgraded again, any Virtual Connections that was created or existed in 2022.1 would no longer work due to permission issues.
  • With the ATR activation method, the activation service could result in excessive logging at the "info" level.
  • After publishing a workbook, a line could appear in a crosstab, which was not present in the rendering in Tableau Desktop.

New in Tableau Server 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 Server 2021.4.3 (Jan 13, 2022)

  • 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 Server 2021.4.2 (Dec 20, 2021)

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

New in Tableau Server 2021.4.1 (Dec 16, 2021)

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

New in Tableau Server 2021.4.0 (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 Server 2021.3.4 (Nov 30, 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 Server 2021.3.3 (Oct 27, 2021)

  • Resolved Issues:
  • After publishing a viz, the date on the axis would change and become incorrect.
  • In Tableau Server, clicking a button on a dashboard might result in an error "Failed to execute 'arc' on 'CanvasRenderingContext2d'".
  • In Tableau Server when there were over 1000 sites, the Site Admin would not be able to see any sites on the Site Picker.
  • When loading a view, an error could display stating "Uncaught SyntaxError: Unexpected token U in JSON at position 0."
  • With the SAP HANA data source and using web authoring, creating a filter could display an empty list and the error, "TableauException: Reference to undefined field."
  • Google Big Query data sources could fail an incremental extract refresh with the following message, "Error with duplicated DS: 'Destination exists. Not copying file.'"
  • Upgrade could fail with the error, "Error performing restore at com.tableausoftware.installer.operations.RestoreRepositoryOperation".
  • 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."
  • When connecting to a Google sheet the connection would sometimes fail with the error "OAuth-client cannot be passed in as null or empty".
  • After upgrading to Tableau Server 2020.1, a large SAS extract refresh could fail with the error, "Exceeded per-process memory threshold." Large memory is consumed when this error occurs. KB: https://kb.tableau.com/articles/Issue/large-sas-file-extract-refresh-failed-and-huge-memory-consumption-observed-after-upgraded-tableau-server-to-2020-3-1.
  • Starting in 2021.1+ , if SAML is configured, users were not getting the site selection option but redirected to a site.

New in Tableau Server 2021.3.0 (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 Server 2021.2.2 (Sep 2, 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 Server 2021.2.1 (Jul 23, 2021)

  • Resolved Issues:
  • An intermittent error: "Unable to complete action. Internal Error - An unepected 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_:ok]', datasource='(name)."
  • "Error: Unable to complete action. Internal Error - An unepected 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 etract 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 Ecel and etract data sources.
  • An etract could repeatedly be created when switching between the sheet and the data source tab even after the etract 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 Server 2021.2.0 (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 Server 2021.1.2 (May 18, 2021)

  • 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 Server 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 Server 2021.1.0 (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 Server 2020.4.3 (Mar 24, 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 Server 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 Server 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 Server 2020.4.0 (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 Server 2020.3.3 (Nov 20, 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.
  • 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 Server 2020.3.2 (Oct 30, 2020)

  • Opening a workbook with an extract where the extract was created within a packaged workbook could sometimes fail with the message, "Internal Error - An unexpected error occurred and the operation could not be completed. Error code 6EA18A9E".
  • Auto update could have an inconsistency between the user interface and a twb file with the 'lock-update' flag.
  • An error would sometimes occur retrieving OData feeds with the message, "Error '20B40A5E'. The table does not exist" .
  • If the data source filter was initially set to exclude all values, changing the existing data source filter would not work correctly.
  • Creating an Oracle extract would sometimes result in the error, "Invalid datetime value Error Code: DD90F63D, Unable to create extract".
  • To refresh extracts for an Oracle JDBC connection to the same database, the user would be prompted for the password to each connection instead of one prompt.
  • A workbook connected to an Impala data source could result in the error "AnalysisException: LEFT OUTER JOIN requires an ON or USING clause" when "none" is selected in a parameter.
  • A query could take an excessive amount of time on a complex worksheet and not load.
  • WDC based connectors would not respect proxy configurations from PAC files starting with 2019.4.
  • Connecting to Google BigQuery would sometimes be slow on the initial load of datasets.
  • Sometimes Tableau Desktop would quit when signing out of Tableau Online.
  • When connected to a large spatial file that is a published data source, and an attempt to load a geometry field was performed, an error would display, "Error: BinaryTupleReader::NextWireValueAligned:941 Not enough data for header".
  • Duplicated translations appeared in the Dashboard menu. "Caption" was translated as "Title" in zh-CN.
  • With Impala an ISO-8601 cast from a string to a date and time field failed on 2020.2 and higher with the error, "Invalid character value for cast specification".

New in Tableau Server 2020.3.1 (Oct 1, 2020)

  • 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.
  • Calculations that use RAWSQL are not included in the GROUP BY clause when used as a Dimension with AWS Athena and Amazon Redshift.

New in Tableau Server 2020.3.0 (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 Server 2020.2.4 (Jul 30, 2020)

  • Resolved Issues
  • Issue ID Description
  • 1139225
  • The use of Double Precision with a SharePoint List caused a "Malformed SQL Statement" error. What's resolved:
  • 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 Server 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 Server 2020.2.1 (May 28, 2020)

  • 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 Server 2020.2.0 (May 26, 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 Server 2020.1.3 (Apr 29, 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 failed 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 "<" symbols resulted in an error "Unable to complete action An error occurred while loading the data. Error Code C926DA9F An unknown error related to remote content was detected (500) MALFORMED_QUERY"
  • Filtering on a calculation based on parameters and sets sometimes removed more data than expected from the view.

New in Tableau Server 2020.1.2 (Mar 31, 2020)

  • 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 Server 2020.1.1 (Mar 9, 2020)

  • Resolved Issues:
  • 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 Server 2020.1.0 (Feb 27, 2020)

  • Resolved Issues:
  • Published workbooks with blended data sometimes showed some unexpected values.
  • "Download Workbook" events sometimes displayed in admin views when users had not downloaded workbooks.
  • When subscribing to PDFs of an entire workbook that included custom views, all views defaulted to original.
  • Creating or opening a workbook based on a Google BigQuery data source sometimes resulted in the error "IllegalArgumentException contentIds must be non-null and non-empty"
  • Right-click context menu on parameter search box sometimes failed to appear.
  • CSV files with uppercase extensions stored in a Windows shared directory were not found by Tableau Server on Linux using wildcard union.
  • Changing the height or width of a dashboard button caused the button image to offset.
  • Centered mark labels sometimes displayed as off-center when using client side rendering.
  • Custom sign-in logos looked different on the sign-in page and site selection page.
  • Image icons for Lineage were sometimes missing when using published data sources.
  • Running a published flow that used Cloudera Hive with Kerberos failed with the error "Bad format in credentials cache".
  • The error "An error occurred. [...] Uncaught SecurityError: Blocked a frame with origin "" from accessing a cross-origin frame." would occur when interacting with an embedded view and attempting to save a custom view.
  • Attempting to connect to QuickBooks Online would fail and users would be redirected to a QuickBooks Online Blog post.
  • You noticed database disk space and elevated CPU/latency spikes in Tableau Server.
  • In published views, the tooltip sometimes showed a different value than the mark.
  • Subscriptions created between 10/23 and 11/05 may not run on Tableau Online and instead the error "NullPointerException" is received.
  • Refreshes scheduled via Tableau Desktop had a creator ID of 0, rather than the ID of the user who scheduled the refresh.
  • When using Run Now to run an extract, the job creator ID displayed was for the user who created the extract task, not the user who ran the task.
  • After editing the credentials for a cross-database join, "test connection" and subsequent refreshes failed with an "Invalid username or password" error.
  • After changing a site URL, the following error occured when using Tableau Desktop to open a workbook that connected to a data source published before the site URL change was made: "Item Not Found (Error Code 12)"

New in Tableau Server 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.
  • 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 Server 2019.4.1 (Dec 20, 2019)

  • Resolved Issues:
  • 1031097
  • Tableau Desktop 2019.4.0 does not recognize the following 3 Japanese cities: 1. ????? (Tamba-Sasayama, Hyogo)- city changed its name from ??? to ????? in May 2019. 2. ??? (Shibetsu-cho, Hokkaido) 3. ???? (Nakagawa, Fukuoka)- city founded on October 2018, from ???????.
  • 1028076
  • All Tableau releases have been upgraded to JDK 8 to minor version 232 GA.
  • 967899
  • 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.
  • 1003349
  • Filtering a view based on an extract at the quarter level sometimes filtered all data from the view.
  • 1030952
  • 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.
  • 1018977
  • In MacOS Mojave dark mode, significant UI text is missing in the Data pane, Analytics pane, and Save dialog when exiting.

New in Tableau Server 2019.4.0 (Nov 18, 2019)

  • Resolved Issues:
  • Worksheet not rendering on a dashboard in Tableau Desktop and Tableau Server version 2019.1.x when LogicalQueryCache is enabled.
  • There is no validation for the RunAsUser in TSM.
  • Chinese, Japanese and Korean fonts sometimes rendered incorrectly.
  • When connected to Snowflake, using -1 in a Split calculation resulted in the error "Splitting from right is not supported by the data source".
  • TabPy secure connections do not work for Tableau Desktop on MacOS. The current method for gathering certificates to perform client side validation in Tableau Desktop requires curl built with OpenSSL while MacOS uses DarwinSSL which does not share the same functionality.

New in Tableau Server 2019.3.1 (Oct 25, 2019)

  • Resolved Issues:
  • 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 Server 2019.1.3 (Apr 24, 2019)

  • Resolved Issues:
  • ISSUE ID DESCRIPTION
  • 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 Server 2019.1.2 (Mar 27, 2019)

  • 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 displays labeling and mapping inaccuracies between the current region names and the pre-2013 region names.

New in Tableau Server 2018.9.1 (Feb 13, 2019)

  • Resolved issues:
  • 831047
  • Errors are displayed, when visiting the Extensions Settings Page, and the Extension zones are blank when a viz is rendered.
  • 802304
  • 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.
  • 812492
  • 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.
  • 854729
  • 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.
  • 817431
  • Selecting a mark to highlight and changing filter selections sometimes resulted in the wrong measures being highlighted.
  • 840413
  • With a table calc an reference line in the view, nested sorting failed with a "No such column" error.
  • 840484, 829745
  • When using a fixed logarithmic axis, values in the view did not scale correctly.
  • Read more at https://www.tableau.com/support/releases/desktop/2019.1#TlV0q5gP7Zdj5Kld.99

New in Tableau Server 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 Server 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 Server 2018.3.1 (Dec 3, 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.

New in Tableau Server 2018.3 (Oct 30, 2018)

  • 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.
  • In some multi-node Tableau Server clusters, it was not possible to generate log snapshots via the UI.
  • When using Rest API 3.0 code to access user information, only old Site Role names were returned.
  • When you called the REST API method "Query Datasources", the field "createdAt" showed the same value as "updatedAt".
  • Workbook size was inconsistently reported between the Stats for Space Usage administrator view and the Workbooks content view
  • In Tableau Server on Linux environments, Microsoft Azure SQL based published data sources failed to connect to the database when you published them with prompt user authentication.
  • When running a backup, the following error sometimes occurred, "Did not parse exactly one backup result, got 0."
  • 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 Server 2018.2.3 (Oct 17, 2018)

  • 820533
  • 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.
  • 820393
  • In some multi-node Tableau Server clusters, it was not possible to generate log snapshots via the UI.
  • 814656
  • When you added a node to a cluster using an incorrect Run As User password in Tableau Server 2018.2, the Run As User account became locked due to multiple incorrect password attempts.
  • 824620
  • 2018.2 TSM Maintenance Backup stops with this error "61% Uninstalling backup services. An error occurred on the server generating the backup."
  • 802009
  • After adjusting zoom levels, some column and header borders were missing.
  • 798973
  • When viewing a dashboard in IE 11 which used Javascript embed code, check boxes and radio buttons intermittently failed to display.
  • 742859
  • Clicking the vertical browser scrollbar sometimes cleared filter action selections on a dashboard.
  • 827784
  • When running tsm upgrade script with a path containing parenthesis, the install fails with "TableauTableau was unexpected at this time." during upgrade from 2018.1 to 2018.2.1.
  • 821312
  • When running a backup, the following error sometimes occurred, "Did not parse exactly one backup result, got 0."
  • 817922
  • The Run As Service account cannot be set to use an account from an Active Directory domain that is different from the server’s AD domain.

New in Tableau Server 2018.2.2 (Sep 28, 2018)

  • In some cases, it was not possible to clear the text from a string parameter.
  • When you set a fiscal year start for a date field used in blending, an "Invalid datetime value" error occurred.
  • Using Tableau Desktop 2018.1 or 2018.2, a debug.log file appeared when you installed or double clicked a workbook.
  • In some cases, when connecting to Tableau Server via mutual SSL, Tableau Desktop displayed an "error 6 SSL handshake failed" error message.

New in Tableau Server 2018.2.0 (Jul 31, 2018)

  • In some cases, calculated fields containing multiple level of detail expressions returned unexpected results.
  • In some cases where some sheets in a dashboard have been filtered down to display a single data point, tooltips containing views (Viz in tooltip) would show the same view when hovering over marks in different sheets.
  • An unknown collation error would occur when connecting to CSV files using the Norwegian Bokmål (Norway) locale.
  • Updated postcode data for the Czech Republic.
  • In some Mac environments, visualizations would either disappear or turn into black boxes on when the Tableau Desktop window was dragged to a secondary display.
  • With accelerated graphics enabled, text in annotations that was set to a font size of 48pt or higher was not rendered cleanly on some systems.
  • When you were connected to IBM DB2 and using date filters, the TIMESTAMP_ISO function was sometimes used in queries which negatively impacted performance.
  • In histogram views, the axis labels did not match the bin values represented by the marks in the view.
  • Updated Japanese postcode data.

New in Tableau Server 2018.1.3 (Jul 11, 2018)

  • Resolved Issues:
  • In Tableau Desktop for Mac, it was not possible to connect to SAP HANA as the driver was not being properly recognized.
  • In some environments, the Edit Axis dialog would appear blank or as a black box.
  • With accelerated graphics enabled, text that was formatted to use a large font size was not rendered correctly.
  • Appending a Microsoft Access file to an extract would fail with an error: Unable to append data from file. Microsoft JET database error 0x80004005: Unrecognized database format
  • Missing field errors could occur when opening workbooks connected to Google Analytics.
  • Malformed SQL queries and resulting errors could sometimes occur when using a date parameter to modify a view.
  • Data appended to a .tde extract using Tableau 10.5 or higher could be lost when you edited the data source in an existing workbook.
  • In some cases, unexpected metadata queries would be sent to the underlying database in workbooks using an extracted data source.
  • After you performed a union of CSV or Excel files, merging mismatched fields would, in some cases, result in an Incompatible types error.
  • On macOS, if you exported a sheet as a crosstab and the file path or file name of the export contained a Chinese, Japanese, or Korean character, the export file would not be created or the resulting file name would have garbled characters.
  • Updated the Google Analytics connector with additional dimensions and metrics.
  • When connecting to statistical files, if a field contained a NaN value in its first row, all values in that field would be recognized as NaN.

New in Tableau Server 2018.1.2 (Jun 20, 2018)

  • In some cases, changing a filter selection could cause the filter width to shrink with each successive change to the selection.
  • 771008
  • Selecting a large number of marks (~100 or more) and then choosing to Keep Only or Exclude those marks would result in an internal error.
  • 767724
  • When connecting to Excel files containing Japanese data, big and small Katakana characters were incorrectly recognized as equivalent. Deleting existing shadow extract files (.hhyper) may be required to see the correct behavior after upgrading Tableau Desktop. On Windows platforms the files are located in UsersAppDataLocalTableauCachingTemporaryExtracts and on Mac these files are located in ~/Library/Caches/com.tableau.caching/TemporaryExtracts.
  • 769287
  • Viewing full underlying data in a view connected to Oracle would either show the incorrect number of rows or no data at all.
  • 766478
  • In some cases, custom filter titles could revert to their original name upon opening a workbook.
  • 760591
  • An ambiguous table reference could occur when connecting to certain Cisco Information Server data sources.
  • 749962
  • Users were allowed to publish an extract-only data source (e.g. Salesforce) from the Server menu in the Data Source page before the required extract was created.
  • 743018
  • In some cases, filtering on a group containing at least 8 dimension members would result in a no such column error.
  • 643637
  • Color palette assignments, based on combined fields with dimensions from different data sources, would be lost when the workbook was reopened.

New in Tableau Server 2018.1.1 (Jun 15, 2018)

  • Resolved Issues:
  • On some computers running Symantec software, Tableau Desktop would become unresponsive when performing normal authoring work.
  • When opening a Tableau Desktop workbook and viewing a worksheet, the Filters and Marks cards became excessively wide.
  • When connected to Sybase IQ, strings containing special characters were not rendered correctly.
  • Setting ATR duration, for virtual desktop support, to a value over 24 days would cause Tableau Desktop to become unlicensed after only 3 days.
  • If you connected to a data source, hid fields, and then extracted the connection, changing the data type of a field and then returning to the Data Source tab would cause all the hidden fields to reappear.
  • Connecting to an OData v4 data source could fail with an error: Bad OData Format. Make sure you are using a URL that points to a valid OData Source.
  • Saving an extract to a network folder, or opening a workbook containing an extract from a network folder, would regularly fail with a number of network related errors.
  • Adding an aggregated calculated field to the Filters shelf in a view with Aggregate Measures disabled would cause unexpected behavior.
  • On Mac systems with switchable graphics, Tableau Desktop would default to discrete graphics instead of switching from integrated to discrete when needed.
  • In some cases using a combined field, in combination with a table calculation, in a view with grand totals turned on would result in overlapping marks.
  • Type in date parameters with a specified step size would display the incorrect date for some input values.
  • No values would be returned when you connected to a Microsoft SQL Server stored procedure containing a nested stored procedure.
  • Editing custom SQL in a saved, packaged data source (.tdsx) containing a Firebird connection would fail with an error.
  • When connected to Amazon Redshift, data displayed as null if the field name exceeded 20 double byte characters.

New in Tableau Server 10.5.4 (May 18, 2018)

  • Changes were applied to improve security. See ADV-2018-006, ADV-2018-007, ADV-2018-008 and ADV-2018-010 in Security Bulletins for more details.

New in Tableau Server 10.5.2 (10500.18.0305.1200) (Mar 9, 2018)

  • Hyper processes could repeatedly go down in environments running on a CPU that did not support the SSE3 instruction set.
  • In Japanese language environments, filter selections could change when opening a pre-10.5 workbook in Tableau Desktop 10.5 or 10.5.1.
  • When connected to Sybase IQ, strings containing special characters were not rendered correctly.
  • Changing the formatting of a continuous date field would cause vertical grid lines to disappear from the view.
  • 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.
  • When you connected to text files using a legacy connection and custom SQL, it was not possible to change the text file properties.
  • Dimension members containing the
  • Data sources published to Tableau Online, containing a live connection to a stored procedure maintained using Tableau Bridge, would fail with a syntax error.
  • 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 Server 10.5.1 (10500.18.0210.2209) (Feb 15, 2018)

  • 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.
  • Body font color formatting did not work for compact list parameters.
  • 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.
  • In some cases, calculated fields containing the LEFT() function returned unexpected results when connected to data containing non-English strings.
  • 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.
  • When connected to a web data connector data source, the data source name would be displayed in parenthesis next to all field names.
  • In some environments, the Tableau Bridge client would quit unexpectedly when switching it to run in service mode.
  • Next Refresh Time and Last Refresh Time were not being properly updated in the Tableau Bridge client.
  • 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.
  • When performing a cross-database join involving a legacy Excel connection, and error would occur: collation mismatch, use COLLATE statements to resolve
  • 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.
  • When connected to Denodo, generated queries would sometimes contain unnecessary case statements.
  • 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.
  • 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].

New in Tableau Server 10.5.0 (10500.18.0109.1050) (Jan 11, 2018)

  • Optimized server performance for data alerts:
  • To improve overall performance, Tableau Server now rechecks failing data alerts only when it next checks data conditions for all alerts. You can revert to the previous setting, which checked failing alerts every 5 minutes, by changing the tabadmin set option, dataAlerts.retryFailedAlertsAfterCheckInterval, to false.
  • Nested projects:
  • You can now create project hierarchies when you want to create content segments within a larger area. For example, create a project for each department, say Operations. In each of those top-level projects, separate content based on how the audience uses it, say connecting to certified data versus in-progress collaboration. For information about permissions in project hierarchies, see Use Projects to
  • Manage Content Access:
  • Because projects can be nested, the default view resulting from clicking on a project has changed. When you click the Projects menu, rather than immediately seeing the workbooks in that project, you will see the Projects page. The Projects page will show nested projects when they exist. To see the workbooks contained in the current project, you will now need to click the Workbooks menu.
  • Tableau Data Engine with Hyper:
  • Hyper is Tableau's new in-memory Data Engine technology optimized to bring faster extract and query performance, and increased scalability. You can now analyze large data sets faster and faster extract creation. For more information, see The New Data Engine in Tableau Server.
  • Extracts use the new .hyper format:
  • Beginning with version 10.5, new extracts use the new .hyper format. Extracts in the 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 an extract task is performed 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.
  • Web authoring:
  • New features and enhancements related to web authoring and interacting with views on the web are listed in What's New in Tableau for Users and Web Authoring and Tableau Desktop Feature Comparison. For topics related to web authoring and interacting with views, see Using Tableau on the Web.
  • Resolved Issues:
  • Corrected an issue that prevented links in subscription emails from opening in the Tableau Mobile app.
  • In workbooks with tooltips set to show on hover, selecting View Data from the tooltip would result in a blank page.
  • It was not possible to drill up on a discrete truncated date hierarchy using header icons in Tableau Server.
  • When web authoring a new workbook using a published data source, fields would not appear when you added a secondary data source to the workbook.
  • Tabcmd did not return the correct error code when a command failed due to an invalid workbook or view name containing extraneous spaces.
  • In some single-site environments, it was not possible to enable guest user access.
  • Scroll position in a dashboard pane would reset if interaction with the dashboard caused the sheet in the pane to resize.

New in Tableau Server 10.4.2 (10400.17.1206.1554) (Dec 13, 2017)

  • Workbooks connected to multiple stored procedures that accepted parameters could become unresponsive.
  • 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.
  • Use of certain SAML identity providers could result in a blank sign in window when connecting to Tableau Server or Tableau Online.
  • 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.
  • 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.
  • 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.
  • When connected to a cube datasource, filter selections in Multiple Values (Custom List) filters were not shown when printing a dashboard to PDF.
  • Extracting a table containing large strings would sometimes fail with an Error generating sort key error for certain collations.
  • 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)
  • When you selected a custom shape mark and then printed the view to PDF, the mark would not appear selected in the resulting PDF.
  • 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.
  • 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.
  • When you opened a workbook containing sheets with Auto Update Worksheet turned off, changing to another sheet would unexpectedly cause that sheet to load.
  • 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 Server 10.4.1 (10400.17.1103.1137) (Nov 9, 2017)

  • Resolved Issues:
  • 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.
  • 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.
  • 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.
  • 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
  • Using level of detail calculations could, in some cases, generate slow-running SQL queries when connected to Teradata.
  • In some workbooks, hiding or deleting a sheet would result in an internal error.
  • Color assignments for calculated fields based on sets would change when an older workbook was opened in Tableau Desktop 10.3 or higher.
  • 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.
  • 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.
  • 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.
  • The Dropbox and OneDrive connectors were missing if you activated Tableau Desktop using a trial.
  • 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.
  • 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.
  • 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.
  • 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.
  • An internal error would occur when you tried to edit the alias of an empty bin segment.
  • 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
  • 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.
  • 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.
  • Using calculated fields involving datetime fields that had been converted to date would, in some cases, result in an error: ColumnTable: Schema/DataTable mismatch
  • When you edited an axis in a dual axis view, the opposite axis from the one intended would sometimes be modified.

New in Tableau Server 10.4 (10400.17.0915.2112) (Oct 4, 2017)

  • Install and Deploy Tableau:
  • Remove previous versions of Tableau Desktop during install (Windows only)
  • Downgrade and publish workbooks to an older version of Tableau Server
  • 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

New in Tableau Server 10.3.3 (10300.17.0915.2101) (Sep 20, 2017)

  • Connections to Excel files saved in Excel version 1707 would fail with an error: Errors occurred while loading the data source
  • SAML authentication from Tableau Desktop to Tableau Server would fail in some environments.
  • 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.
  • Extracts would unexpectedly refresh when you switched between the Data Source tab and a sheet tab.
  • 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.
  • An internal error would occur, in some cases, when you attempted to sort a calculated field containing conditional statements.
  • 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.
  • Query execution errors would occur when you connected to Cloudera Impala using custom SQL with a date parameter.
  • When you saved a workbook in presentation mode and then re-opened the workbook, the view would not be correctly centered.
  • 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.
  • 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.
  • In some cases, when you joined multiple tables and performed a pivot, null values would incorrectly appear in Pivot Field Names.
  • An internal error would occur when you renamed a sheet and then tried to use the controls on the Pages shelf in the sheet.
  • Printing to PDF was noticeably slower in Tableau Desktop 10.0 and higher compared to prior versions.
  • 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.
  • In some cases, aggregated calculated fields would return no data after an extract was created.
  • 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.
  • In some European locales, double-precision numbers were returned as #ERROR or null.

New in Tableau Server 10.3.2 (10300.17.0728.2252) (Aug 4, 2017)

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

New in Tableau Server 10.3.1 (10300.17.0615.2100) (Jun 22, 2017)

  • This release includes minor improvements for quality and reliability.

New in Tableau Server 10.3.0 (10300.17.0515.2100) (Jun 2, 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
  • 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.
  • New connectors:
  • New Amazon Athena connector
  • New Dropbox connector
  • New MongoDB BI connector
  • New OneDrive connector
  • New ServiceNow ITSM connector
  • 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.
  • 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.
  • 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
  • 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).
  • 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.
  • NEW TO WEB AUTHORING:
  • Web authoring topics for Tableau Server and Tableau Online are now located in Tableau Help, starting with version 10.3
  • 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
  • Format numbers on the web:
  • You can now specify basic number formatting for measures in the view on Tableau Server and 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.
  • 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.
  • 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.
  • 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.

New in Tableau Server 10.2.2 (10200.17.0505.1445) (May 12, 2017)

  • Data Server processes would sometimes hang when you loaded a workbook connected to a published data source based on a text file located in a shared network folder
  • In some workbooks, refreshing the view would cause the view to go blank due to filter selections becoming deselected
  • The JavaScriptAPI getMarksAsync() function failed to return information for some larger, more complex crosstab views
  • Data Server processes would sometimes crash when loading a dashboard with multiple sheets connected to a text file in a network shared folder
  • Loading certain dashboards would fail with a Cannot read property 'substr' of undefined error
  • When you tried to load different revisions of a published workbook, the same revision version was always displayed
  • In some cases, published views connected to a published data source would render with incorrect values due to fiscal year start being inadvertently ignored
  • Labels for heat map views, created using square marks, were not displayed past the first page when the view also utilized multiple pages
  • A Version mismatch error would intermittently occur when loading views, typically when Tableau Server was under high load
  • Workbooks connected to HANA via single sign on would incorrectly prompt for credentials when loaded
  • Updated Firebird components to version 2.5.6
  • If a dashboard had a name that was longer than 160 characters, an error would occur when you tried to download it as an image or PDF
  • Views would intermittently fail to load without any error and appear blank in Tableau Server due to underlying calculated fields being incorrectly evaluated as invalid
  • Workbooks connected to published data sources, containing parameters with large numbers of selections, loaded considerably slower than equivalent workbooks using embedded data sources
  • Certain workbooks would encounter a Session ended by server error when you changed a parameter selection
  • Updated psqlODBC drivers to version 09.06.0200. This version includes an updated version of OpenSSL 1.0.2k
  • When certain font and font size combinations were used, axis labels would be truncated if the axis title was hidden
  • When you published a workbook via tabcmd, and it failed for a valid reason (e.g. incorrect data source information), subsequent attempts to republish the workbook would continue to fail even if the issue had been corrected

New in Tableau Server 10.2.1 (10200.17.0328.0755) (Apr 6, 2017)

  • Loading views in Tableau Server and Tableau Online would intermittently fail with a Failed to copy file error
  • In workbooks with a filter applied to multiple worksheets, calling the filtereventClass.getWorksheet().getName() Javascript API function would return the same worksheet name for every worksheet that the filter was applied to
  • Mitigated an issue with creating extracts on the unsupported Windows Vista and Windows Server 2008 (non-R2) operating systems. Beginning with Tableau 10.3, we will begin blocking installations on these operating systems
  • Loading published views could intermittently result in an error: Unexpected Server Error - TableauException: Unable to open file FILE: No such file or directory

New in Tableau Server 10.2.0 (10200.17.0223.1918) (Mar 3, 2017)

  • 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 Server 10.1.5 (10100.17.0203.1324) (Feb 16, 2017)

  • In certain environments, restoring a Tableau Server backup would fail with an error: "Exception during sos data restore: java.lang.IllegalArgumentException: MALFORMED"
  • 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 scenarios where visualizations are refreshed on a very frequent interval (e.g. every minute), VizQL Server processes could rapidly consume large amounts of memory.
  • 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.

New in Tableau Server 10.0.0 (Aug 16, 2016)

  • Clustering:
  • Quickly spot patterns and group your data with drag-and-drop cluster analysis.
  • Data Breakthroughs
  • Connect and prep your data faster, with new connectors and data prep improvements.
  • Cross-Database Join Google Sheets QuickBooks Connectors Maps Oracle Notifications
  • Cross-database join:
  • Join data from different data sources, like SQL Server and Oracle. Publish the integrated data source to Tableau Online or Tableau Server to collaborate with others. Learn how easy it is to make your own integrated data source.
  • Beautiful by Design:
  • With a fresh look and feel, beautiful viz defaults, and new formatting controls, your vizzes are even more impactful.
  • Downright Beautiful New Defaults Workbook Formatting Font Seamless Titles
  • Downright beautiful:
  • Enjoy a clean, beautiful canvas for analytics, with new iconography, typography, and colors. Learn more about the new Tableau design.
  • Delightfully Mobile:
  • Get Tableau on any device. Now including Android.
  • Device Designer Android Mobile Device Management
  • Device designer:
  • You can now design, customize, and publish a single dashboard that includes optimized views for tablet and phone. Learn more about device designer.
  • Do More on the Web:
  • With dashboard authoring on the web and revision history at the ready, it’s easier for everyone to use Tableau when and where they want.
  • Web authoring Data Source Analytics Revision History Publish Flow
  • Web authoring:
  • Add published data sources and author dashboards right in your browser. Learn more about these new capabilities.
  • Self Service at Scale:
  • Powerful governance and extensibility features for scalable enterprise deployments.

New in Tableau Server 9.3.4 (Jul 13, 2016)

  • In some cases, workbooks and data sources connected to Cloudera Impala did not prompt for credentials in your browser when published to Tableau Server using 'Prompt user' authentication.
  • In some cases, importing a large number of users into Tableau Server via tabcmd with a CSV file would take an unusually long amount of time and generate sustained high CPU load.
  • In some cases when a Tableau Server backgrounder process became unlicensed, scheduled extract refreshes would still run and result in "path does not exist" errors upon subsequent refreshes.
  • When you refreshed a published data source in Tableau Server or Tableau Online, the data update time inserted in titles sometimes failed to update.
  • Workbooks connected to Amazon Redshift would intermittently fail to load if a prior load had failed or was cancelled.
  • On Tableau Server, after running an action, if a sheet did not use the source or target sheets' data sources, it would fail to load.
  • Connections to Tableau Server published data sources would intermittently throw a timeout or 'No Tableau Server user found' error for no apparent reason.
  • When using a filter's 'Find Values' search functionality in an iOS browser (e.g. Safari, Chrome, etc.), searching using Japanese characters would often fail to find existing values.
  • In some cases in Tableau Server, the number of server users did not match the number of users in the All Users group.
  • Exporting a site from Tableau Server would fail if a server administrator, that was not added as a user to the site, had favorited items in the site.
  • When signed in to Tableau Server in Tableau Desktop, the ISMEMBEROF() calculated field function failed to recognize you as a member of a group if the group name contained the "@" character.

New in Tableau Server 9.2.6 (Mar 10, 2016)

  • 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.