누구나 사용할 수 있는 분석 도구
누구나 사용할 수 있는 데이터 준비 도구
조직을 위한 분석
조직을 위한 클라우드 분석
Tableau 맵 프록시 변경 사항
맵 프록시 및 정적 방화벽 규칙을 사용하여 Tableau 맵에 액세스하는 경우 Tableau에서 지속적인 맵 프록시 사용을 위한 조치 필요 링크를 클릭하여 프록시 서비스의 중요한 변경 사항에 대해 알아보십시오. 조치 완료 기한: 2018년 6월 15일 금요일
Tableau 8.2 introduces many new capabilities that expand your ability to access and analyze data. The release includes the first-ever Mac OS version of Tableau Desktop, Story Points for interactive, data-driven storytelling, a more visual connection experience with data previews and improved experience in defining data table joins, and updated maps, in addition to enhancements to simplify administration and support of Tableau Server.
Tableau Desktop was not always respecting the Show Empty Rows/Show Empty Columns options. This resulted in views that included rows or columns for empty or missing data. This behavior can be toggled (empty rows or columns can be shown or hidden) by selecting Analysis > Table Layout > Show Empty Rows or Show Empty Columns as described in the Tableau Desktop Help topic Missing Values.
This release contains a critical security fix to Tableau Desktop, Tableau Server, and Tableau Reader that reduces exposure to man-in-the-middle and denial of service vulnerabilities. To address these vulnerabilities, the OpenSSL library used by the affected Tableau products has been upgraded to 1.0.1h.
REPLACE() is now supported for legacy Jet connections to Microsoft Excel, Access and plain text (CSV) data sources.
Depending on the calendar being used in a given locale, the first week of the year may fall into the previous year. For example, in ISO-8601 calendar, the first week of the year is the week containing January 4th. As a result, even December 29th of the previous year could be the start of the first week of the next calendar year. Prior to this fix in certain years, date fields using the format yyyy Www in iso-8601 or Urdu locales would appear incorrectly as week 1 of the previous year instead of the current year. This fix does not affect standard Gregorian calendars where first day of the year is January 1st.
Abbreviated dates were inconsistently formatted when a workbook's language locale was set to French (Canada). The abbreviations for months would end with a period for discrete dates but not for continuous dates.
Upgraded the version of Firebird provided in Tableau Desktop to 2.5.
When a view using a reference line was copied and pasted into Word or Excel as an EMF image file, the reference line label would be incorrectly aligned.
Subtotals were disabled or enabled based on whether grand totals were shown instead of remaining independent.
Editing a set that was based on a continuous dimension would sometimes result in an error stating that the Edit Set dialog could not be displayed. Meanwhile, the set could still be used.
Views that included maps with dual axes would not resize correctly.
In packed bubble charts, when a null value existed in the data, bubble marks were placed on top of one another.
An exported PDF or PNG did not accurately reflect filter-based highlighting on the dashboard. Sheets that should not have had any highlighting had highlighted marks in exported files, while the highlighting displayed correctly on the dashboard.
When formatting a week date or a fiscal week date to show as the truncated fiscal week (for example, Week 10 formatted as W10), the week numbers could be shifted so they did not match the actual week (for example, Week 11 could show as W10).
Including the previous_value() function in a table calculation was causing an error when refreshing a data extract.
Darker Circle and Shape marks were using dark labels that were difficult to read against the dark marks.
If a join field for a Teradata connection was deleted or renamed, the connection could not be edited without losing other valid tables and joins in the connection.
Dimensions included in a filter were automatically added to the Rows shelf when you updated a table calculation on the Filters shelf.
With a Microsoft Analysis Services data source, filtering with a time dimension that had a string data type could cause a view to stop responding.
When blending data, selecting in the secondary data source a field that contained geographic information mistakenly enabled the map view in Show Me.
Parameter controls for numeric or date fields did not behave as expected for non-US locales.
Uganda districts have been updated in maps.
Using aggregations on a poorly written parameter-based calculation caused an "ambiguous function call" error. Example: a spelling or case mismatch of parameter options, or parameter options missing from the view.
Closing a workbook without saving changes after you refreshed an extract caused an "Ignoring calculated field '[Number of Records]', field is already defined by data source" error.