누구나 사용할 수 있는 분석 도구
누구나 사용할 수 있는 데이터 준비 도구
조직을 위한 분석
조직을 위한 클라우드 분석
Tableau 맵 프록시 변경 사항
맵 프록시 및 정적 방화벽 규칙을 사용하여 Tableau 맵에 액세스하는 경우 Tableau에서 지속적인 맵 프록시 사용을 위한 조치 필요 링크를 클릭하여 프록시 서비스의 중요한 변경 사항에 대해 알아보십시오. 조치 완료 기한: 2018년 6월 15일 금요일
When opening a Tableau Desktop 8.0.x workbook in Tableau Desktop 8.1.x, an error "ColumnTable: Schema/DataTable Mismatch" occurred if the workbook contained a calculated field that used the modulo (%) operator.
Tableau Desktop was not deleting temporary tables created during an Amazon Redshift connection after the Redshift session ended. Logs showed “drop table failed” messages.
When connecting to an Amazon Redshift data source, the tabprotosrv process stopped responding, logging a "collision with existing protocol when creating new protocol" error.
When working in a proxy environment with NTLM authentication, map tiles did not load.
When connected to a DataStax data source, dragging a field with a name of 128 or more characters to the view resulted in the error: "Query returned non-zero code" appeared when you.
Publishing a workbook with an Amazon Redshift data source and table names more than 64-character long, resulted in an error.
When connected to IBM DB2 databases, database passwords appeared in Tableau logs.
When connecting to multiple tables in a Cloudera Hadoop Impala database, querying for the tables did not allow selecting the schema. Only tables from the default schema were shown.
After connecting to a SQL Server database with a period in the name, Tableau Desktop could not initiate bulk inserts into SQL Server temp tables and was unable to connect to a stored procedure.
Refreshing an SAP BW extract caused workbooks to lose color, shape, and sort assignments for instances of columns.
Subtotals did not appear in crosstabs exported to Excel if dimension members associated with subtotals were hidden.
Duplicating a dashboard produced an "Invalid numberless marker in format string" error message. The error occurred if there was a percent (%) symbol in the name of a dashboard action.
Selecting values from a multiple value list in a workbook published to Tableau Server and connected to an extract of an EMC Greenplum data source sometimes resulted in the error: "unexpected error".
Tableau Desktop did not recognize synonyms in a SQL Server database.
With a cube data source connection, typing in the search box on a quick filter displayed a matching string, but after it was selected, nothing would appear in the view.
When publishing a workbook to Tableau Server, selecting the Name drop-down menu to show existing workbooks did not display the workbooks in alphabetical order.
Incremental extract refreshes, with a data source filter applied, did not update the value in titles, captions, or annotations. Full extract refreshes with the same data source filter applied successfully updated the value.
If a worksheet contained no dimension from a primary data source and a dimension from a secondary data source on the Filters shelf, or if it contained only a dimension from a secondary data source and a measure from a primary data source on the Filters shelf, clicking View Underlying Data resulted in an "Invalid set function" error.
Using MySQL in calculations sometimes resulted in an “illegal mix of collations” error.
A data extract would be deleted from the computer after that data extract replaced another data source in a workbook.
Switching between customized views sometimes resulted in the wrong view displaying, especially if they were part of the same dashboard.
When connecting to SAP NetWeaver Business Warehouse databases, only the Key aliases were available for dimensions despite other properties being available in the BEx Analyzer.
When refreshing dashboard views, Tableau Desktop sometimes stopped responding.