Samsung Magician

What's new in this version:

Fixed:
- An intermittent error: "Unable to complete action. Internal Error - An unepected error occurred and the operation could not be completed. Error Code: 0E1EAFA4" could occur when editing a view.
- When attempting to refresh or open a workbook with multiple data source, the error could display stating, "ERROR: no such field '[Calculation_:ok]', datasource='(name).
- "Error: Unable to complete action. Internal Error - An unepected error occurred and the operation could not be completed. Error Code: 6EA18A9E" could occur when publishing or opening a workbook on Tableau Server when there is a table calculation, a parameter, and data blending in one worksheet
- Error code 6ea18a9e could display when performing an incremental refresh of an etract that uses custom SQL
- OData V3 could fail to refresh using 2020.3+
- A workbook could generate a "collation mismatch" error when trying to view full data with Ecel and etract data sources
- An etract could repeatedly be created when switching between the sheet and the data source tab even after the etract had been created successfully
- The Impala data connector would fail to connect via the HTTP transport protocol
- With PostgreSQL data, a timezone set by the initial SQL command when connected via JDBC would fail to apply
- When opening and closing workbooks, aliases and sorts were sometimes not saved when connected live to Microsoft Access
- Some users were not able to log into Tableau Online from Tableau Desktop when using a Gmail email account
- "Error code 2F0F5E42" could display when a workbook was connected to a live data source with joined tables
- Error Code: F5328B32, "Tableau cannot evaluate the query that results from this calculation" could result when more than one spatial calculated field is added to the view
- In Tableau Reader, a workbook would fail to open when custom geocoding was contained
- A "Driver not found" error message would sometimes result and the sign-button was unavailable when opening a workbook connected to an Impala data source
- Presto data queries could fail with the error, "Value is not a number: java.lan.String", when converting custom SQL to decimal using the DECIMAL() function to cast the data type
- When generating the forecast for a Measure, an "Internal error" could occur