マッププロキシと静的ファイアウォールルールを使用して Tableau マップにアクセスしている場合は、次のリンクをクリックしてプロキシサービスの重要な変更点を確認してください: Tableau でマッププロキシを継続して使用するために必要な処置。現在のマッププロキシは 2018 年 6 月 15 日金曜日より使用できなくなります。
Release Notes for Tableau 10.0.1
Note: Tableau Desktop customers in environments with Product Updates enabled will be prompted to upgrade a few days after a maintenance release is made available. For more information, see the Tableau Knowledge Base.
Various changes were applied to improve security. See Security Bulletins for more details.
Apache Tomcat was upgraded to 7.0.75. This upgrade fixes a potential vulnerability in Tomcat: CVE-2016-8745
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
When switching between custom views in Tableau Server, incorrect data would sometimes be returned if the views only differed by parameter selection and the parameter was being referenced in a calculated field used as a data source filter.
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 a small number of scenarios, sometimes involving level of detail calculations, extract query performance became significantly worse after upgrading to Tableau 9.3 or higher.
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 Tableau Server, adjusting a range of dates filter using the date picker would reset any previous time selection if there was a time part associated with the dates.
In some cases, when you interacted with a small multiples view containing pie charts in Tableau Server, visual artifacts would appear in the browser.
When viewing an embedded view, or using the share link, and downloading the view to PDF from Tableau Server, the Download PDF dialog sometimes did not appear, or was cut off, unless you zoomed out 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.
Publishing a workbook to Tableau Server via REST API could sometimes fail with a bad request error.
Tableau Server connections to SAP HANA using SAML SSO were sometimes unnecessarily slow.
When you had a stepped color legend in a published Tableau Server view, zooming out in a browser would introduce an additional color step in the legend (usually white or black).
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.
In Tableau Server, the 'Live/Last extract' column in a workbook's data sources page failed to update when you refreshed the workbook's extracts in Tableau Desktop and republished the workbook.
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.
When you tried to configure a SAML-enabled Tableau Server, after upgrading to Tableau Server 10.0, an error would sometimes occur: "The 'xml' prefix must not be bound to any other namespace"
After upgrading to Tableau Server 10.0, File Store processes would sometimes appear in an indefinite, busy "Synchronizing" status.
On one-node Tableau Server installations, no notifications were sent when Postgres went up or down.
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.
Portions of the Background Tasks for Extracts administrative view in Tableau Server and Tableau Online were cut off, particularly at smaller screen resolutions.
Periodically, VizQL server processes would encounter an internal error and CPU consumption sometimes increased. To work around this issue, restart the VizQL server process.
If you previously published a workbook, with a live connection to Microsoft SQL Server and authentication set to "Viewer credentials", and then tried to republish it with an extracted connection, you were not able to publish the workbook unless you renamed the workbook or deleted the existing published workbook from Tableau Server. This issue did not occur when publishing data sources.
In some cases, scheduled Salesforce-based extract refreshes would fail with an error: "com.tableausoftware.nativeapi.dll.DataSourceException:No such column [field name]."
In Tableau Server and Tableau Online, the default value for the 'Min View Count' filter in the Traffic to Views administrative view was set too high, and the minimum adjustable value was 30 which was also too high.
Line marks with transparency would sometimes fail to render in browsers on certain high-DPI displays or when the browser window was zoomed.
After publishing to Tableau Server or Tableau Online, parameter slider controls were slightly offset from how they appeared in Tableau Desktop.
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"
If you publish multiple QuickBooks Online data sources to Tableau Server or Tableau Online, and if the published data sources use the same embedded credentials, only the last published data source can be refreshed.
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.
When a dashboard with device layouts is viewed on a phone or tablet in portrait mode, Tableau Server sometimes incorrectly displays a device layout for a larger device. For example, instead of displaying a dashboard layout designed for phone, Tableau Server may display one for a tablet or desktop. If you share a link for the dashboard via the Share button, or if you view it from Tableau Mobile, the correct device layout is displayed. This issue only occurs when the dashboard is viewed from the Server user interface