Known Issues

The following is a list of some of the known issues with Tableau products. We include only issues we think are important or would potentially impact many customers. Use this information to decide when to upgrade to a new release, and to see if we know about issues that are affecting you.

This is a dynamic list: We are adding new issues as we discover them. When we release a new version that addresses an issue, we add a link to the release note for that issue in the Status column. After 45 days, we remove fixed issues from this list. Fixed issues are listed on the Release Notes page.

For help with any issues, contact Tableau Support.

Last Updated: Sep 27, 2016
Tableau Server
Issue ID Description Status
563630

When you clicked the Export Metadata File button in the SAML tab of the Configure Tableau Server dialog, the resultant XML file was malformed. A workaround was published at http://kb.tableau.com/articles/issue/saml-metadata-xml-file-exported-fro....

Open
562420

In some cases, viewing a workbook with very complex connection elements (very numerous connections, federated data sources, a large amount of renamed fields, or other factors that might result in a lot of workbook connection element XML) could result in a non-specific 'session ended by server' error.  The vizqlserver logs revealed an error that said 'Key discarded as its current size (size) exceeds the max 2097152'.

Open
548566

In Tableau Server 10.0 and Tableau Online, it was no longer possible to collapse and hide the upper navigation toolbar in the browser interface.

Open
537756

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

Fixed in 10.0.1
541260

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.

Fixed in 10.0.1
541258

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.

Fixed in 10.0.1
554632

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"

Fixed in 10.0.1
530793

On one-node Tableau Server installations, no notifications were sent when Postgres went up or down.

Fixed in 10.0.1
546704

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.

Fixed in 10.0.1
547197

Portions of the Background Tasks for Extracts administrative view in Tableau Server and Tableau Online were cut off, particularly at smaller screen resolutions.

Fixed in 10.0.1
547536

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

Fixed in 10.0.1
548092

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.

Fixed in 10.0.1
548936

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

Fixed in 10.0.1
550841

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.

Fixed in 10.0.1
552267

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

Fixed in 10.0.1
553651

After publishing to Tableau Server or Tableau Online, parameter slider controls were slightly offset from how they appeared in Tableau Desktop.

Fixed in 10.0.1
555241

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.

Fixed in 10.0.1
555381

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"

Fixed in 10.0.1
557752

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

Fixed in 10.0.1
509729

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.

Fixed in 10.0.1
520776

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.

Fixed in 10.0.1
527087

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.

Fixed in 10.0.1
528596

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.

Fixed in 10.0.1
530087

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.

Fixed in 10.0.1
531469

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.

Fixed in 10.0.1
539305

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

Fixed in 10.0.1
540182

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.

Fixed in 10.0.1
540405

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.

Fixed in 10.0.1
543083

Publishing a workbook to Tableau Server via REST API could sometimes fail with a bad request error.

Fixed in 10.0.1
545071

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

Fixed in 10.0.1
549090

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

Fixed in 10.0.1
524007

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.

Fixed in 10.0.1
548231

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

Fixed in 10.0.1
540405

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.

Fixed in 9.2.12
543083

Publishing a workbook to Tableau Server via REST API could sometimes fail with a bad request error.

Fixed in 9.2.12
545071

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

Fixed in 9.2.12
552620

In some cases, loading a view with an SAP HANA prompt in Tableau Server would result in a long spinner with an eventual HTTP 503 error or, sometimes, a "Session Ended by Server" error.

Fixed in 9.2.12
509729

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.

Fixed in 9.3.7
520776

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.

Fixed in 9.3.7
527087

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.

Fixed in 9.3.7
528596

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.

Fixed in 9.3.7
530087

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.

Fixed in 9.3.7
531469

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.

Fixed in 9.3.7
539305

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

Fixed in 9.3.7
540182

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.

Fixed in 9.3.7
543729

In some cases, workbooks connected to a Microsoft Excel data source would fail to load with an internal error.

Fixed in 9.3.7
549090

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

Fixed in 9.3.7
524007

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.

Fixed in 9.3.7
Tableau Online
Issue ID Description Status
548566

In Tableau Server 10.0 and Tableau Online, it was no longer possible to collapse and hide the upper navigation toolbar in the browser interface.

Open
546704

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.

Fixed in 10.0.1
547197

Portions of the Background Tasks for Extracts administrative view in Tableau Server and Tableau Online were cut off, particularly at smaller screen resolutions.

Fixed in 10.0.1
548092

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.

Fixed in 10.0.1
548936

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

Fixed in 10.0.1
550841

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.

Fixed in 10.0.1
552267

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

Fixed in 10.0.1
553651

After publishing to Tableau Server or Tableau Online, parameter slider controls were slightly offset from how they appeared in Tableau Desktop.

Fixed in 10.0.1
555894

Republishing and overwriting an existing workbook on Tableau Online would remove any previous extract refresh schedules for the workbook.

Fixed in 10.0.1
561162

The Tableau Online Sync Client failed to run scheduled extract refreshes for some data sources published to Tableau Online using Tableau Desktop 10.0. This primarily affected data sources that used username and password authentication to connect to underlying databases as well as data sources containing two or more file-based connections.

Fixed in 10.0.1
Tableau Desktop
Issue ID Description Status
555638

Joining a web data connector data source with another data source would sometimes fail to return valid data.

Fixed in 10.0.1
561162

The Tableau Online Sync Client failed to run scheduled extract refreshes for some data sources published to Tableau Online using Tableau Desktop 10.0. This primarily affected data sources that used username and password authentication to connect to underlying databases as well as data sources containing two or more file-based connections.

Fixed in 10.0.1
509733

When connected to a Microsoft Analysis Services data source in Tableau Desktop, using a non-English client locale, thousands separators would sometimes be incorrectly interpreted resulting in numbers that were displayed incorrectly.

Fixed in 10.0.1
516451

When you blended two data sources on a date field and exported a view as a crosstab to Excel, the results in Excel sometimes did not match the values displayed in Tableau Desktop.

Fixed in 10.0.1
519983

In some cases, when connected to a Progress OpenEdge data source in Tableau Desktop and using a boolean field as a data source filter, a no such function error would occur when loading a view or describing a field.

Fixed in 10.0.1
527572

In certain cases, connections to Microsoft SQL Server would fail when opening a workbook in Tableau Desktop and an unreasonable number of attempts would be made to reconnect before you were prompted to edit the connection.

Fixed in 10.0.1
527616

In Tableau Desktop, connecting to SAP BW would fail with an "Authorization failed" error if your password contained special characters.

Fixed in 10.0.1
528596

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.

Fixed in 10.0.1
538967

In some cases, grand total values would disappear when navigating between sheets using actions.

Fixed in 10.0.1
543892

Refreshing an IBM Big SQL-based extract using the Tableau Data Extract Command-Line Utility would fail with an error: '[IBM][CLI Driver] SQL30082N Security processing failed with reason "17" ("UNSUPPORTED FUNCTION"). SQLSTATE=08001 Invalid username or password.'

Fixed in 10.0.1
551038

In some cases, a 'no such function: STR' error would occur when you were connected to an SAP HANA data source in Tableau Desktop and attempted to use a calculated field that cast an integer to a string.

Fixed in 10.0.1
527398

In Tableau Desktop, when you filtered using a top computed set and an INDEX() calculation a no such column error would occur.

Fixed in 10.0.1
530781

Creating an extract in Tableau Desktop would fail with a "mismatched row counts" error if you had a group in a view and the group was based on a field that was also being used as a data source filter.

Fixed in 10.0.1
552434

In some environments with higher than expected network latency, Tableau Desktop would crash when connecting to a database.

Fixed in 10.0.1
509733

When connected to a Microsoft Analysis Services data source in Tableau Desktop, using a non-English client locale, thousands separators would sometimes be incorrectly interpreted resulting in numbers that were displayed incorrectly.

Fixed in 9.0.17
527572

In certain cases, connections to Microsoft SQL Server would fail when opening a workbook in Tableau Desktop and an unreasonable number of attempts would be made to reconnect before you were prompted to edit the connection.

Fixed in 9.1.13
551038

In some cases, a 'no such function: STR' error would occur when you were connected to an SAP HANA data source in Tableau Desktop and attempted to use a calculated field that cast an integer to a string.

Fixed in 9.1.13
422334

When you printed a workbook to PDF from Tableau Desktop, with an unspecified paper size, the first page would not have properly sized margins.

Fixed in 9.2.12
517597

In Tableau Desktop, you could not connect to a single row text or Excel file with no column headers.

Fixed in 9.2.12
519983

In some cases, when connected to a Progress OpenEdge data source in Tableau Desktop and using a boolean field as a data source filter, a no such function error would occur when loading a view or describing a field.

Fixed in 9.2.12
543892

Refreshing an IBM Big SQL-based extract using the Tableau Data Extract Command-Line Utility would fail with an error: '[IBM][CLI Driver] SQL30082N Security processing failed with reason "17" ("UNSUPPORTED FUNCTION"). SQLSTATE=08001 Invalid username or password.'

Fixed in 9.2.12
516451

When you blended two data sources on a date field and exported a view as a crosstab to Excel, the results in Excel sometimes did not match the values displayed in Tableau Desktop.

Fixed in 9.3.7
527616

In Tableau Desktop, connecting to SAP BW would fail with an "Authorization failed" error if your password contained special characters.

Fixed in 9.3.7
528596

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.

Fixed in 9.3.7
538967

In some cases, grand total values would disappear when navigating between sheets using actions.

Fixed in 9.3.7
542500

In some cases in Tableau Desktop, opening a workbook containing level of detail calculations resulted in an error: "Tableau Data Engine Error: 49035: join expressions must have same data type"

Fixed in 9.3.7
543729

In some cases, workbooks connected to a Microsoft Excel data source would fail to load with an internal error.

Fixed in 9.3.7
544596

When connecting to SAP HANA, Tableau Desktop would allow you to specify multiple values for input parameters that accept multiple entries but only one value would actually be used.

Fixed in 9.3.7
422334

When you printed a workbook to PDF from Tableau Desktop, with an unspecified paper size, the first page would not have properly sized margins.

Fixed in 9.3.7
non-humans click here