Tableau Desktop 9.0.3

On Windows, when Tableau Desktop stores credentials for accessing Tableau Server through a proxy, the proxy credentials are stored in trusted storage.

With Tableau Desktop set to Japanese, Chinese, or Korean, when you tried to connect to a Vertica database with custom SQL, an error sometimes appeared.

When the user didn't have access to the Tableau temporary folder (for example, C:\Users\\AppData\Local\Temp\), Tableau sometimes stopped responding.

Tableau was closing unexpectedly when creating, editing, or viewing calculated fields if you had 3rd party accessibility tools installed.

When you attempted to refresh or re-open a workbook with a SAP BW connection that used a Single Value, Mandatory, No Default variable, an error resulted and the view didn't appear.

When you attempted to connect to an Excel workbook that contained a .gif image, an error resulted indicating communication with the Tableau Protocol Server had been lost.

Print to PDF on large workbooks was slow and omitted some columns of data from the output.

Aggregate filters were not showing updated results when you removed dimensions from a view.

Appending CSV file data to an extract sometimes produced an error like the following: "Tableau Data Engine Error: 4: SimpleDatabase::SelectMetadataName: expected found=1, actual found=0 (fk=18446744073709551615 name="Cache&"nameTable="SCHEMAS")"

No "Number of Records" value was generated when connecting to a database using ODBC.

With SAS Statistical File connections, numeric values were incorrectly rounded up by a count of 1.

Data source filters sometimes filtered results incorrectly when a workbook was opened in Tableau Desktop 9.0.

When you created a relative date filter while connected to an analytic view in SAP HANA, an error appeared: "[SAP AG][LIBODBCHDB DLL][HDBODBC] Syntax error or access violation;257 sql syntax error: incorrect syntax near ",": line 4 col 72 (at pos 286)".

When you changed a parameter in a workbook that used custom SQL queries, multiple query batches (each with a single query) were issued instead of parallel queries.