Tableau Server 10.0.1

In Tableau Server, site administrators of a single site were unable to view the Status and Settings pages for the site they administered. Also applies to Issue ID 548042 and 547468

In some cases, when you published a small multiples view with pie marks to Tableau Server, the marks became unclickable in a browser. The result, most of the time, was that tooltips could not be exposed.

In Tableau Server, when you loaded a view using a URL parameter, and the same parameter was also used in custom SQL for the workbook's data source, the view would sometimes fail to show the correct data for the specified parameter value unless ':refresh=yes' was also appended to the URL.

In some cases, when you interacted with a small multiples view containing pie charts in Tableau Server, visual artifacts would appear in the browser.

In Tableau Server, views connected to SAP HANA using SAML SSO would prompt users for SAP HANA credentials, if left idle in a browser for too long, and it would not actually be possible to sign back in for a period of time. The SAML timeout for SAP HANA SSO now has a longer default and is configurable.

Tableau Server connections to SAP HANA using SAML SSO were sometimes unnecessarily slow.

When you used a published data source that was connected live to an underlying table, and additional columns were added to that underlying table, refreshing the data source in Tableau Desktop would not update the data pane with the new columns for an extended period of time. Due to potential performance trade-offs of extra queries for column metadata, the fix is hidden behind a Tableau Server configuration setting that must be toggled on.

When performing an in-place upgrade to Tableau Server 10.0 from a prior version, with SAML previously configured, saving the Tableau Server configuration during the upgrade would fail with an error and prevent the upgrade from proceeding.

After upgrading to Tableau Server 10.0, File Store processes would sometimes appear in an indefinite, busy "Synchronizing" status.

When web authoring, after clicking Save or Done, a "Done Editing" page would appear and you could not return to the page you were on prior to web authoring.

Periodically, VizQL server processes would encounter an internal error and CPU consumption sometimes increased. To work around this issue, restart the VizQL server process.

In some cases, scheduled Salesforce-based extract refreshes would fail with an error: "com.tableausoftware.nativeapi.dll.DataSourceException:No such column [field name]."

Line marks with transparency would sometimes fail to render in browsers on certain high-DPI displays or when the browser window was zoomed.

After upgrading to Tableau Server 10.0, if you tried to configure Tableau Server to use SAML and specified the HTTPS protocol in the return URL, without configuring Tableau Server for SSL (i.e. SSL is being offloaded), an error would occur and configuration could not proceed: "invalid protocol specified for SAML return URL. Use https if SSL is enabled or http otherwise"

When you edit the credentials for a published QuickBooks Online data source, you cannot select a different company than the one originally associated with the published data source. Otherwise, extract refresh jobs for the data source will return a generic authentication error.