From a single collection of datasets, you may need to generate multiple outputs for downstream purposes. Examples:
If your next step is to add any of the following transformations and you wish to preserve the existing data for other uses, you should consider adding these steps in a separate dedicated recipe.
A union appends one or more datasets to your current one. To preserve the original, you may need to create a branching output. See Union Page.
A join combines two datasets based on common values in specified columns in both datasets. These types of transformations can greatly change the shape of your data. See Join Window.
Similarly, a lookup uses values from a column in your source data to pull in corresponding rows of data from a reference dataset. These transformations add columns to your dataset. See Add Lookup Data.
|Deduplicate||This transformation removes identical rows from your dataset. However, there may be a set of steps required to standardize values in various columns before applying the de-duplication. You may choose to manage this process in a branching recipe.|
|Delete columns||When a column is removed, it is no longer available for use in any downstream output. See Remove Data.|
|Filter||Rows can be filtered from your dataset to render different perspectives. These changes may be best moved to a secondary, branching recipe. See Filter Data.|
|Pivot data||When you create a pivot table, all source data that is not explicitly specified in the pivot is dropped from the dataset. For more information, see Pivot Data.|
|Group by||You can perform aggregation calculations within a table, which may force column data to be dropped. See Create Aggregations.|
Whenever you are applying a transformation that destroys data or otherwise reshapes your dataset and you wish to preserve the current state of the dataset, you should do the following:
Pivot-SalesPerProductPerStorerecipe. Click Edit recipe.
When ready, run the job. The output should be generated in the appropriate format and location.
Multiple pivot tables sourced from output of a primary recipe for the flow. POS-r01-Part2 can be used for continued wrangling of primary recipe.