Tableau Prep Builder 2020.2.1

Running certain flows resulted in an error "Failure evaluating to database: no such column".

Running flow in Prep 2020.1.4 results in the following error during pivot step: "Failure evaluating to database:[Microsoft][ODBC Driver 17 for SQL Server][invalid column name 'Pivot1 Names'".

Loading profile pane menu in super nodes is slow.

Rows in Output File are MORE than the result of last step (Join).

Joined and pivoted flow, built on a data set that is left joined on itself, does not output the expected number of rows.

When using Tableau Prep Builder 2020.1.1 in a workbook, the following error occurred during pivot steps: "System error: unable to execute input node: Failure evaluating to database. No such column [column name]".

Result in CSV output file does not match with the 'Row to Column Pivot' result displayed in Tableau Prep Builder 2019.4.2.

Tableau Prep Builder is only using a subset of the data for previews, when 'Use all Data' is selected in Version 2020.1.1. This is not the same as in 2019.3, where Prep reports it is using all 1.8 million rows in a data source.

Prep Builder fails to overwrite .hyper file due to Hyper exceptions.

When creating a left unmatched only join in Tableau Prep Builder 2019.4.2, the result contains the data which is matched. Version 2019.3.2 works fine.

After clicking the output node and selecting a valid local directory to store the output hyper file, the row count shows `0 Rows` even though the data grid clearly shows a lot of data.

When running a Tableau Prep flow containing a union step, joins and lastly a clean step in which several of the fields are renamed, an error occurs: Something went wrong and we were unable to process output step: Failure parsing AQL: Internal Error - An unexpected error occurred and the operation could not be completed.

Prep flows with a wildcard union in the Input step will not pull in new data from new files added in a network shared location when run in Prep Conductor. This is true for both full refresh and incremental refreshes. The same flow pulls in all the new data correctly when run in Prep Builder.

Users can save a subset of steps in a flow either locally or publish it to Tableau Server as "Saved Steps" to reuse in other flows across the organization. However, incremental refresh settings will be lost from Input and Output Steps when saved in this manner.

Users can copy and paste Steps between Prep instances and flows. However, incremental refresh settings will be lost in Input and Output Steps when copied and pasted.

When a user has Incremental refresh enabled in a flow AND the flow's output table has a different schema than the existing table it wants to append to, running this flow using the command line interface produces a blocking error, even when the user chooses to run a full refresh to create the table.