Cloud Bachelor Tableau to Quicksight Migration tool Release Notes Version 1.0.17

This is the 1.0.17 release of the Cloud Bachelor Tableau to Quicksight Migration tool. It enables automated translations of Tableau workbooks into AWS Quicksight DataSource, DataSet, Analysis and Dashboard records.

Please carefully review these release notes before purchasing to ensure your use case is supported.

This version allows users to convert Tableau workbooks hosted in Tableau Cloud to a Quicksight instance in the AWS Account for which the appropriate AWS IAM role is provided to the tool via the standard IAM role credential chain.

Video demo: https://d3rhxoxmrirmc1.cloudfront.net/v107_demo_1.mp4 

Please contact support@cloudbachelor.com  via email if you encounter any issues or have questions.

What's new: We've added support for quicksight cross datsource joins. In Tableau these are treated as a single datsource with multiple connections inside of it. They are added to SPICE automatically.

We've added a 'Miss Score' features which is a count of the times we find an incompatibility or unsupported feature. The miss score only factors in issues that we are aware.

Notes on the Analyzer:

The analyzer can analyze workbooks imported via the Tableau API or via file upload. It works by scanning the workbook XML for various components.

Notes on the Converter:

What is and is not supported for the Converter:

Tableau Versions: Tableau Cloud Tableau API version: 3.22 Tableau Document format version: 18.1

Workbooks .twb or .twbx

Supported authentication methods: IAM role Tableau cloud username/password PAT Tokens for login

Supported Datasource integrations: Redshift (must be embedded in the workbook, virtual connections are not supported in this release) Athena (Quicksight's default Athena permissions must be setup ahead of time) Microsoft SQL Server (username and password) Snowflake (username and password) Any DataSource can be selected if it already exists in your QuickSight environment.

Tableau Features:

Supported Marks:

Line Extra dimensions are added to small multiples and colors

Bar A single extra dimension can be added to colors

Pie A single dimension maps well. Using small multiples works poorly.

Text Depending on the combination of encodings, rows and columns in your Tableau Text mark we will map it to either a Quicksight KPI or a Quicksight Table.

Square Converted to HeatMap if it has text encodings

Circle Converted to Scatter Plot if it meets the minimum requirement of 2 or more measures for a Quicksight scatter plot.

Histogram Histograms with chart type of Automatic or Bar are automatically detected and converted to the Quicksight Histogram visual type. Specifically, we detect if a chart has one measure and one dimension and that dimension is a calculated bin field. Note: by default we set the bin width to 10 when converting. You can change this in the formatting options for the visual in quicksight.

Maps / Geospatial Charts We support area maps. Dot maps in tableau are categorized as 'Automatic' but we have the ability to identify many of those and convert them into Quicksight point maps.

Scatter Plots, Box and Whiskers, Bullet Graphs, Heat Maps We can detect some of these algorithmically, but will default to a line map if we can't identify the chart.

Automatic We have limited support for automatic marks. If our algorithm doesn't find which chart type it should be mapped to we fall back to a Quicksight line chart and mention it in the conversion comments.

Measures and Dimensions Numerical, Categorical, Date

Aggregations: AVG, COUNT, COUNTD, STDEV, STDEVP, MIN, MAX, VAR, VARP, MEDIAN, SUM Percentiles are not supported in this release Custom aggregations are not supported in this release

Currently, we support unlimited measures and up to three dimensions in a chart. Quicksight has different limitations on dimensions compared to Tableau for certain chart types.

Encoding support is limited at this time.

Datasource / DataSet limitations

Renaming If you have renamed fields in your workbook we should reflect the renaming in the Quicksight DataSet.

Retyping/casting If you have changed the type of fields in your workbook it should reflect that in the Quicksight DataSet.

Tableau Relationships (Same source only) Do be aware that Quicksight Joins are not exactly the same as Tableau Relationships. Quicksight joins act much like SQL joins. Where Tableau Relationships are more flexible. Also do note that Quicksight requires that cross datasource joins use SPICE which we don't support outside of S3 DataSources https://docs.thinkwithwp.com/quicksight/latest/user/joining-data.html  We only convert tableau relationships which use equality as a comparator.

Tableau Joins (Same source only) The tool can convert joins from tableau to Quicksight. The maximum is 32 same-datasource joins in Quicksight.

We have support for cross-datasource joins (Quicksight term). Do note that Quicksight requires these to be stored in SPICE. The tool will automatically convert your DataSet to use SPICE for cross-joins. In tableau you would have one Datasource with multiple connections inside it. Those would be treated as cross-datasource joins by Quicksight.

Calculated Fields We have basic support for calculated fields. Simple ones will work. Formulas that use tableau features that are named differently in Quicksight will fail.

Filters

Worksheet level filters We've added support for worksheet filters. Inclusive and exclusive sets, numerical ranges, relative dates and date ranges. We do not have support for Action filters. We do not have support for 'level-members' type filters. We do not support Top/Bottom filters For wildcard filters at the sheet level we do not have support for 'Does not end with' or 'Does not start with'. Note: We do not support filters which apply mathematical expressions to non-number types yet.

Datasource and extract level filters Lists, Wildcard comparisons, Conditions, inclusive and exclusive sets, numerical ranges and date ranges. Note: For wildcard filters at the Datasource or Extract level we do support 'Does not end with' or 'Does not start with'. How quicksight handles these works differently at the DataSet vs Analysis level. We do not have support for Action filters. We do not have support for 'level-members' type filters. We do not support Top/Bottom filters

Custom SQL Single source custom SQL works. If you have a datasource where you join tables in custom SQL that should work. We do not have support for multiple custom SQL queries from different datasource yet.

Initial SQL - not supported

Unsupported Features Tableau: initial SQL Actions Custom aggregations Oauth for authentication

Unsupported Features Quicksight: Assigning created resources to Quicksight Users (only Quicksight groups are supported in this version) Auto-discover Redshift (We only use Manual Connect)

Known Issues: If you run into issues with authentication credentials expiring, please try logging in again. That should overwrite any expired tokens held in memory.

Tableau allows you to create Parameters that are lists of strings and use them in calculated fields. Quicksight does not allow using that kind of Parameter in calculated fields. Quicksight unfortunately does not tell you when it crashes due to this issue.