Product release and download
Tableau Server 2018.3.1
We recommend using the newest maintenance release of this version, 2018.3.27, which contains additional fixes.
Release date
Product support
Resolved Issues
Issue ID | Description |
---|---|
847209
|
Internal error when opening workbook |
812447
|
Web Authoring functionality is not working with trusted ticket authentication. The URL to open a view in Web Edit mode works, however any action such as dragging a field into or out of view causes a redirect to Tableau Server sign in page. |
817857
|
Custom geocoding was not always applied when published from a computer using a Japanese language operating system. |
836626
|
Dashboards with "automatic" layout size, nested layout containers and subtotals displayed as blank in maximized browser windows. |
825597
|
Changing the default layout from list to thumbnail or vice versa did not save when using "Make This my Start Page". |
819235
|
When using a Chinese, Japanese, or Korean locale in Tableau Server on Linux, after you changed a date and time parameter value, the parameter reverted back to the previous value. |
820203
|
MSAS datasources published with "Prompt User" credentials continually prompted for credentials when accessed from an non-Administrator account. |
825512
|
After upgrading to or installing Tableau Server 2018.2, sometimes logs grew quickly and filled available disk space. |
825786
|
Sometimes, installing Tableau Server 2018.2 failed with an "Initialization terminated at step 5 of 40: An error occurred while waiting for services to reconfigure." message. |
827204
|
Hyper crashes due to invalid expression extraction. |
845684
|
In Tableau 2018.3, sometimes maps using custom polygons appeared distorted, inverted, or rendered as a single color box. |
834805
|
Upgrading from Tableau Server 2018.1 and earlier versions to 2018.2 and newer versions failed with an "InstallerException: Unable to login" error when the TSM admin password contained an exclamation point (!). |
821312
|
When running a backup, the following error sometimes occurred, "Did not parse exactly one backup result, got 0." |