Tableau 10.2.1 – New Capabilities and Corrected Issues in TABLEAU

You can make extremely powerful data visualizations utilizing any data with Tableau Desktop easily and quickly. Tableau Desktop works with hundreds of data sources. You can share data and dashboards and collaborate with governance using the Tableau Server. You can keep the data secure on the Tableau Server. Tableau Online is nothing but a hosted Tableau Server.

Tableau 10.2.1 is the latest version of Tableau and it has been released on April 5, 2017. The customers of the Tableau Desktop in the environments with the authorized Product Updates will be elicited to Upgrade some days after a maintenance release is made available. The desktop Build Number is 10200.17.0328.0755 and the Server Build Number is 10200.17.0328.0755.

Tableau 10.2.1 New Capabilities

The calculations that contain the DATETRUNC function created wrong queries that would return unexpected results when linked to Hive data sources.

Tableau 10.2.1 Corrected Issues

The following issues that were reported in the previous releases have been corrected in addition to the brand new capabilities. There are 19 updates for Tableau Desktop and 14 updates for Tableau Server.

Tableau Desktop

1. When you utilized a text file union data source utilizing a FIXED level of the detailed expression subdivided by the linking of another field and table name wouldn’t return any data.
2. For the discrete fields, the editing aliases would result in an internal error sometimes.
3. When you try to link a SAP HANA table with an Excel data source, an internal error would occur sometimes.
4. From the View Data dialog, exporting entire data did not respect the existing selections for Show all fields and Show Aliases checkboxes.
5. When joined to the data sources based on files, the data update time dynamic showed the last time the data source was refreshed without the file being updated itself.
6. It would take a lot of time for the Tableau Desktop to launch on few Mac systems. To eliminate .local from machine hostname was the workaround.
7. Few custom WMS maps would be provided with huge white gaps in the map titles.
8. When the discrete and continuous instances of the same field were being utilised in some cases, the Tableau Desktop would crash if you attempt to append a field from a secondary data source.
9. If the size of application window was made smaller or when utilising the Tableau Desktop on a low resolution, the washout slider wouldn’t be displayed while editing the map layers.
10. When editing the axis for an area mark chart, the Include Zero checkbox has no effect.
11. While signing in, the Tableau Online Sync Client will crash or display error sometimes.
12. The Tableau Desktop wouldn’t be responsive implicating a huge number of marks in few authoring scenarios.
13. On the unsupported Windows Server 2008 (non-R2) and Windows Vista, an issue with generating extracts has been mitigated.
14. Changing a string field to date would return the null values when linked to a Hive data source.
15. Opening few workbooks would fail and an error would be returned which is “element ‘tuple’ is not allowed for content model ‘(value).’”
16. When the tables consisting of fields with data types that are unsupported are joined, an internal error is returned.
17. If the initial SQL consists of an inner select statement that returned the zero rows, an initial SQL would arise when joined to Amazon Redshift.
18. When re-opening, closing and saving certain workbooks, the assigned color palettes would alter.
19. In the Tableau Desktop for Mac, the Emoji characters were not displayed properly.

                                                                                                    (Related Page: Tableau Desktop Tutorials)

Tableau Server

1. Because of the process(tabsrvlic.exe) crashing, the Manage Product Keys for Tableau Server would fail to launch in few environments.
2. This error occurs after Saving the Workbook: Cannot read property ‘get_width’ of undefined while web authoring a workbook that depends on a SAP HANA data source with variables and input parameter.
3. With a TableauException or a server error that is unknown: opening the packaged workbook. Error results in the occurrence of an unexpected error, few huge workbooks would fail to load.
4. Due to the issues related to data caching, incorrect data would be displayed while loading a published view utilising the URL parameters in few cases.
5. When the Allow publishers used to insert the credentials in a data source or workbook was rendered inoperative, it became visible that the non-admin publishers were able to edit connections to change the credentials of the database and save changes successfully though they weren’t saved actually. The dialog now accurately throws an error when a publisher tries to save the changes.
6. Workbooks linked to SAP HANA utilising single sign-on authentication were slower to load in some cases after upgrading to Tableau Server 10.0 or higher.
7. When you web authored a workbook linked to SAP HANA utilising single sign-on authentication, you wouldn’t be able to link to data source, with the database credentials that are valid, if you were not the owner of data source or published workbook.
8. After changing or applying a read-only user password that started with some special characters, the 9. Tableau Server would fail to begin.
10. The Published data sources based on SAP HANA consisting of custom SQL, would fail with a syntax error when you tried to link to them after upgrading from the of Tableau Server’s older versions.
11. An error occurs after loading the published views intermittently: Unexpected Server Error – 12. TableauException: Unable to open file FILE: No such directory or file.
12. In few instances, the formatted borders didn’t extend round the scroll bars.
13. In Tableau Server and Tableau Online, loading the views would fail at irregular intervals with a Failed to copy file error.
14. In the workbooks with a filter applied to numerous worksheets, calling the filtereventClass.getWorksheet().getName() Javascript API function would result in returning the same worksheet name for each worksheet that is subjected to filter.
15. Pacified an issue with creating the extracts on the Windows Server 2008 (non-R2) and Windows Vista operating systems that are unsupported. Starting with Tableau 10.3, we will start obstructing the installations on these OS’s.

                                                                                                                 (Related Page: Tableau Server Tutorial)

List Of Tableau Courses: