8.0.3

Descargar ahora
This version is available from the Customer Account Center.

Fecha de la versión:
17 Jul, 2013
Número de versión de compilación de Tableau Desktop:
8000.13.0712.1936
Número de versión de compilación de Tableau Server:
8000.13.0712.1936
Tableau Desktop (Back to top)
Issue ID

The date and time format in parameter controls would not display correctly when the system date/time was set to a Russian locale.

Added support for the odbc-connect-string-extras TDC customization for Amazon Redshift This change allows SSL connections to Amazon Redshift data sources.

A no such column error can occur with a multi-pane visualization that blends data from two data sources, where one pane contains a table calculation that uses a simple aggregation (such as SUM, MIN, MAX, COUNT), and a user calculation in a different pane uses the same simple aggregation.

Added support for connecting to Cloudera Impala (CDH4u1).

When connected to DB2 data sources, calculated fields that return a string such as formulas that use the ATTR aggregation, were incorrect in published data sources.

In some cases, using a Window table calculation on a highlight table view would result in incorrect calculations. Tableau now provides a warning in these cases.

Some tick marks on logarithmic axes with fixed axis ranges disappear or display incorrectly. A workaround is to set the minimum on the fixed axis to be greater than zero.

The dashboard Size menu was not correctly localized for all languages.

Tableau Desktop may stop responding when publishing specific workbooks that use filter actions.

When connecting to Essbase databases, an Essbase database error 1013136: Invalid login id error could occur even when using known valid credentials.

Bins renamed in the Create Bins dialog will show the default bin name until the data is refreshed.

The Latitude (generated) and Longitude (generated) field names are not localized when editing a workbook on the web.

Printing a workbook to PDF in Tableau Desktop took longer than usual.

Several keyboard shortcuts were incorrect when using a Korean UI language.

Tableau Desktop may stop responding after connecting to a Google Analytics data source.

In a view that shows small multiples using a quantitative axis, selecting an individual axis in the view would select all of the axes instead.

Some marks in a page trail are not being displayed correctly when the mark type is shape and the size of the mark changes from page-to-page.

In Tableau Desktop, performing a table calculation when using IN/OUT mode results in a required field is missing error.

The application would stop responding when publishing a workbook that uses blended data sources that have custom relationships and context filters.

In Tableau Desktop, selecting Show Me can remove join override information.

Publishing dashboards that have filter actions could cause a Commit called on nested editor error.

When joining a table to itself in Salesforce, the list of possible join clauses that can be added is empty in the Add Table dialog.

The search box on the More Fields drop-down menu at the bottom of the Marks card would become unresponsive after interacting with marks in the view or fields in the Data window.

In Tableau Reader 8, opening packaged workbooks containing a local cube (.cub) file may result in the error message Unknown data source class 'msolap'.

When using an annotation mark, moving the annotation box will result in the ghost (previous) line pointing to the arrowhead rather than continuing to indicate where the mark is annotated. The ghost line will snap to the mark correctly when the mouse is released.

A parameter control can only have up to 1000 steps. Using a parameter that has more than that limit results in an incorrect step size. This limit has been increased to 2000.

Connecting to Vertica 6.1 using the native connector is slower than connecting using a generic ODBC connection.

When connected to DB2 databases, using a secondary dimension that is a calculated field can sometimes cause a no such column error message.

When using Google Analytics as either the primary or secondary data source in Tableau Desktop, all custom relationships are lost and need to be reconfigured after an extract refresh or after closing and reopening the workbook. Automatic relationships still work as intended.

Connecting to a Teradata database view using an account with no read access to DBC view objects can cause Tableau Desktop to stop responding with a Custom SQL validation error.

If no values were entered when a parameter was created, and Set Range to List was selected, Tableau Desktop sometimes stopped responding.

Added support for connecting to Teradata using the Teradata OLAP Connector 14.0 for drill through and named sets filtering.

Tableau Server (Back to top)
Issue ID

In some cases, running a batch script to publish multiple workbooks using tabcmd could fail with errors, execution expired and Update Error.

Tooltips for the Server and Activity administrative view did not work correctly if the language is not set to English.

The Tableau Server service, tablicsrv, contained an unquoted string with a blank space in the service path.

When using quick filters on a mobile device, the scroll position was not saved and would jump back to the top of the list after each selection.

A workbook published to Tableau Server via tabcmd that later had its data connection updated would not retain the updates. Instead, it would use its original data connection information.

A workbook edited on Tableau Server that connected to a large Tableau Server data source (TDE file) sometimes took a long time to save, and occasionally failed to save.

Views with size legends sometimes had text labels but not legend marks when published to Tableau Server.

When using Tableau for iPad or Android, tapping the favorites star would not always add the workbook or view to favorites.

Scientific numbers were sometimes not formatted correctly in Tableau Server tooltips when the server was performing client-side rendering.

An Unexpected Server Error could occur after clicking a mark that runs a filter action and then clicking the Exclude option in the tooltip.

Importing users to Active Directory with an email address as the username fails with an invalid account error.

The error messages DataSourceException: The protocol is disconnected! or Communication link failure sometimes appeared when opening a Tableau Server workbook when the workbook met the following criteria: it had action filters, it was connected to an IBM Netezza database, and it was being simultaneously accessed by multiple users.

In the Tableau for Android application, switching between landscape and portrait orientations would not consistently resize to fit the width.

It was possible to view statistics about other customers visualizations even though permissions in Tableau Server were not set to do so.

With web editing on mobile devices, the zoom level on views may be higher after choosing revert to exit edit mode. Part of the view may also be rendered beneath the shelves area.

Publishing workbooks that use some extended ASCII characters could cause an invalid JSON error.

When setting the start page for all users, a translation missing error message was shown. This occurred because a localized string was incorrectly removed

Exporting a PDF from Tableau Server using the landscape page orientation would instead export with a portrait orientation.

The Language and Locale settings for Tableau Server would be overwritten by the Language preference set in the browser.

The version of Apache Tomcat used by Tableau Server was upgraded to v7.0.41.

Temporary files created on Tableau Server during extract refreshes, image exports, and subscription email creation were not being deleted when they should have been. These files were eventually deleted by a background task.

Clearing a mark selection in a Tableau Server view by clicking the mark a second time may cause the application to stop responding.

Publishing workbooks using the Tableau Server command tabcmd publish with the --timeout option can generate a Proxy Error 502 error.

A Session Ended by Server error could occur when opening workbooks that connect to Essbase databases where the services are recycled on a regular schedule.

When embedding a customized view, the name of the view would not update and instead would show the original name of the view.

In Tableau Server, viewing certain complex dashboards that filter data and highlight totals may cause the application to stop responding.

For workbooks that contain more than one extract, refreshing the extract on a server running multiple background processes could result in unintentionally deleting the extract. A workaround for this issue is to set extract.reaper.holdoff to a value longer than the longest extract time.

Due to a worksheet being incorrectly flagged as invalid, an Invalid JSON error sometimes appeared when a workbook was opened on Tableau Server.

When formatting legends using a background shading, some legends would display with the wrong height when viewed in a web browser.

In some specific workbooks, modifying a quick filter on a dashboard that has multiple filters would cause the dashboard to become unresponsive.

Using a comma to separate tags in a list includes the comma as part of the tag rather than treating it as a separator. A workaround is to use a space to separate tags and enclose tags that have multiple words in quotes.

Scheduled tasks were not running and new tasks could not be scheduled on servers running on Windows Server R2 when the time zone was set to (GMT, UTC).

When automatic updates are paused on a worksheet and its corresponding dashboard, making a change to the view and then switching to a new sheet tab would cause missing images to display in the dashboard.

It was possible for a large number of Server started tasks to be listed as pending in the background tasks list. In these cases, the backgrounder could become unresponsive.

This version is available from the Alternate Download Site.