Changes were applied to improve security. See ADV-2018-023 in Security Bulletins for more details.
Tableau Prep output files (All formats: CSV, TDE, HYPER) show different data than inside the Tableau Prep Data Profile UI.
When you double-clicked a .tfl or .tflx, Tableau Prep opened, but the actual flow did not open.
After joining a .csv file with a MySQL table, the following error occurred, when publishing the .hyper file to Tableau Online/Tableau Server: "Collation mismatch, use COLLATE statements to resolve."
Data contained in Output is different from data contained when previewing Final Step, specifically, Output has some null values for fields that previewing Final Step does not.
If the pivot action is selected in the super-node, the pivoted fields cannot be renamed. Other fields seem fine.
Tableau Prep sometimes failed to launch with an "Uncaught Exception: Error: ENOENT: no such file or directory, mkdir" error when the repository was located in a shared drive.
Publishing a flow from the Command Prompt rather than from the Tableau Prep interface produces an error, “You don't have credentials for Tableau Server to publish extract for one or more output nodes in tfl/tflx file”, though publishing from the Tableau Prep interface using the same credentials works fine.
When creating a union that has at least two mismatched fields you cannot drag and drop last fields and an error appears "Something went wrong and the application needs to restart."
Inserting variables into the calculation editor improperly wipes out or replaces multiple lines of calculation text up through the subsequent variables in the calculation.
Using a "keep only" filter resulted in fewer rows in the output than seen in the preview pane.
Flow file connects to an Oracle database, creates local extract for output, and executes successfully in Tableau prep, but it fails to run in command.
Sometimes, Tableau Prep output preview data was different from the actual output data.
When port number is not specified in the tfl flow file, command line refresh is not able to match the connection. Error will read: “could not find match for [server name]”