Tableau Server 2018.3.6

Type in parameters in published workbooks would not change from the value populated at the time of publication.

In some cases, records do not indicate the correct user id when accessing information via _http_request.

Filters in published dashboards intermittently displayed an incorrect default selection.

Cross Database join, involving Word Sort, fails after Hyper is used in Tableau.

Extract file names that contained non-ASCII characters, and were greater than 30 characters in length, could cause Tableau Server backups to fail.

Unexpected error occurs when clicking on sort icon if horizontal scrollbar cursor is not at leftmost position.

Collecting Tableau Server logs using the 'tsm maintenance ziplogs' command is slower than the pre-TSM equivalent 'tabadmin ziplogs' command.

Scheduled Active Directory sync of all groups is slow.

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.

Tableau Server backups sometimes failed with the following error, "javax.persistence.TransactionRequiredException: Executing an update/delete query trying to set preventGlobalReapExtracts."

Tableau Server Settings page did not display the most recent time Active Directory (AD) synchronization completed.

When a TSM backup job failed, it left behind .tsbak files that were not being deleted by the TSM cleanup job.

In Web Authoring, adding a live published data source, with prompt credentials, to an existing or new workbook results in a logic assert.

Full and/or incremental extract refresh does not work in the case of user filter in datasource filter, with or without extract filter.

TIBCO Information Server cross catalog joins says that the join table does not exist.

When using an LDAP identity store, if the username attribute mapped to an email address, then user import would fail.

When using a table calculation in two different places (pills or shelves) in a viz, the error, "No such column" appears."

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.