Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Insert excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
|
Info | ||||
---|---|---|---|---|
| ||||
Combine data from 2 sources into 1 set of data. For each record in each data set, you get one record. |
Info | ||||
---|---|---|---|---|
| ||||
You have a set of customers stored in one system. You have a set of customers in another system. There are no overlaps. You want all your customers in one list. |
The below screenshots shows how you can combine 2 data sets to create a single data set containing all records from both. (i.e. the equivalent of a union in SQL). To do this have the 2 calculate tables pipe into a single merge table. The same principal applies if you are also combining more than 2 tables.
If you refer to an attribute without a pipe name prefix, i.e. Attribute1, rather than in1.Attribute1, then PhixFlow expects that attribute to exist in all source pipes.
If you do not put an attribute expression, then PhixFlow expects to find an attribute with exactly the same name as itself in all source pipes.
If your attribute is called something different in each source table, then you will need to check the pipe name to work out which attribute to use. This is shown in Attribute3 in the screenshot. _pipeName is an internal variable that stores the pipe name of the current record.
hidden | true |
---|