참고: 제품 업데이트가 지원되는 환경의 Tableau Desktop 고객에게는 유지 관리 버전이 출시되고 며칠 후에 제품을 업그레이드하라는 메시지가 표시됩니다. 자세한 내용은 Tableau 기술 자료를 참조하십시오.
보안을 강화하기 위해 다양한 변경이 적용되었습니다. 자세한 내용은 보안 게시판을 참조하십시오.
In some environments with higher than expected network latency, Tableau Desktop would crash when connecting to a database.
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.
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.
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.
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.
In Tableau Desktop, connecting to SAP BW would fail with an "Authorization failed" error if your password contained special characters.
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 some cases, grand total values would disappear when navigating between sheets using actions.
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.'
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.
In Tableau Desktop, when you filtered using a top computed set and an INDEX() calculation a no such column error would occur.
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.
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.
Joining a web data connector data source with another data source would sometimes fail to return valid data.