In the Output step of your Prep flow, do not select “Publish as a data source”, but instead choose “Save to File”.
Below is a walk-through of how to avoid that behavior.īefore we go any further, it’s worth noting that this workflow will probably be streamlined at some point, but that for now, this is the easiest way of allowing creating a Datasource with data from Prep and. tds file with a generic one and losing all of your calculations in the process. If you want to add aggregate calculations, you can do so in Desktop, but when Conductor runs your flow, it will overwrite your entire Datasource, replacing your. Tableau Prep, however, doesn’t allow for the customization of. tdsx file is the combination of the raw data (.hyper file) and the associated logic (.tds file). This file contains the logic for level of detail calculations, aggregate calculations (such as ratios), and the username-based calculations often used for row level security. Calculations which can’t be materialized on individual rows, however, aren’t stored in a. It contains the results of the data from the datasources as well as any calculations which can be materialized at the individual row level (calculations like string manipulations, differences between two columns, etc.). One current limitation, however, is that Tableau Prep outputs a. With version 18.1 it added Tableau Prep and the ability to build ETL flows, and 19.1 added Prep Conductor, which comes with the ability to automate workflows to run on a schedule. Though Tableau originated as a visualization tool, it has added significant ETL processes over the last couple versions.
NOTE: Tableau went and fixed this in 19.3.1, so if you’re using that or a newer version, stop reading here and just accept that it all works!