Reference: Union Stages
You can include 2 datasets (dataset pipelines) in a Union stage, and add additional Union
stages in the pipeline if you need to combine multiple datasets. If you're familiar
with SQL, the Union stage is the equivalent of a UNION ALL operator.
Define at least 1 set of matched fields (field mapping) in a Union stage before saving it. If
you don't specify a field in an input dataset for a field mapping, Workday will use
a NULL value in that field from that input dataset.
Union Stage Option | Description |
|---|---|
Union Pipeline | Select a dataset pipeline to combine with the primary pipeline. If there aren't any
pipelines available, select Add Another Pipeline
to create a pipeline by importing a dataset. |
Match Fields—Union Output | The name of the field that will be output from the Union stage for each field
mapping. |
Match Fields—Primary Pipeline | The field from the primary pipeline to match with a field from the union
pipeline. |
Match Fields— Union pipeline name
| The field from the union pipeline to match with a field from the primary
pipeline. |
Rematch | Click this button if you want to discard all field mappings and return to the default
field mappings that Workday detects and configures. |
Clear All | Click this button to discard all field mappings. Then define at least 1 field mapping
in the Union stage before saving it. |
Include All | Click this button to create a field mapping for each field in the
input dataset pipeline. Then you can select which fields to match from
the other input dataset pipeline. |
Preparing Fields from Input Datasets
The datasets you want to combine in a Union stage might not have the same schema. Example: One
dataset might have first name and last name information in a single field, and the
other has that information in 2 fields. When this is the case, you can create Prism
calculated fields for each input dataset so that you can combine them in a Union
stage.
You can create Prism calculated fields for input datasets in these locations:
- In the original dataset. Any Prism calculated field you create in a dataset is available to both that dataset and any derived dataset that imports it as an input dataset.
- In the dataset pipeline of the derived dataset. Any Prism calculated field you create in a pipeline stage of a derived dataset is available only to that derived dataset. It doesn't get pushed back to the original input dataset. You might want to create a Prism calculated field in the pipeline of an imported dataset if you need a field to use a different field type, but you don't want to change the field type of the original dataset. Example: You could create a Prism calculated field to change a zip code field from Integer to Text to match it with a Text zip code field in another input dataset.