Release Notes for Tableau 10.0.2
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.
Pre-10.0 data sources published to Tableau Online, that were downloaded and re-published after upgrading to Tableau 10.0 or higher, would fail with a username and password error when refreshed using the Tableau Online Sync Client.
Updated the geocoding database, with particular emphasis on updates to congressional districts.
In some workbooks connected to Oracle Essbase, row headers were not displayed after upgrading to Tableau 9.3 or higher.
In workbooks connected to Oracle Essbase, and created prior to Tableau 9.3, existing filter conditions would be removed when the workbook was opened in Tableau Desktop 9.3 or higher.
Workbooks connected to OLAP cube data sources would sometimes appear to hang when executing queries and fail to load.
Tableau Desktop would sometimes crash under certain network conditions that result in slow SSL root certificate lookups.
When you replaced references for a parameter in Tableau Desktop, some calculated field formulas did not correctly update with the new parameter.
In some cases, when the Tableau Online Sync Client is set to run continuously, pressing the 'Run Now' icon to trigger a refresh for a data source appeared to have no effect. This was especially the case when attempted immediately after logging into Windows.
Incrementally refreshing a Google Analytics extract daily would only add new data to the extract every other day.
In Tableau Desktop, it was not possible to enter Chinese, Japanese, or Korean text via IME into filter search boxes.
Tableau Desktop would often crash when you attempted to edit a large, complex data source.
When you connected to Progress OpenEdge in Tableau Desktop, joining tables would result in an internal error.
Some published extract data sources, created using the Other Databases (ODBC) connection option, would fail with a syntax error when refreshed from Tableau Desktop, the data extract command-line utility, or the Tableau Online Sync Client.
Loading certain workbooks, containing table calculations, could cause total consumption of system memory.
For published extract data sources based on R data files, refreshing an extract would fail with an error when you used the Tableau Data Extract Command-Line Utility: "There is no active connection to the data source"
When you were connected to Presto in Tableau Desktop, using a fixed level of detail calculation sometimes resulted in a query error.