Populate attributes with key values using the '_key[n]'notation
In this exercise you will repeat the comparison you did in the previous exercise, of the full channel list in your model against the list in the inventory database – but this time using a merge:
Add a new merge table to your Channel Package Check model, by dragging in Merge Table from the analysis toolbar.
Set this table NameChannel List Reconciliation 2
Add a pipe from Latest Package All Channels, with Namesales
Drag the following attributes from Latest Package All Channels to Channel List Reconciliation 2:
CustomerRef
Channel
Add a pipe from the database collector SOURCE_ALL_CHANNELS_LIST to Channel List Reconciliation 2
Call this pipe inv
Set up the grouping attributes on the pipe:
Double click on the pipe sales
Go to the Sort/Group section.
Press Show Attributes and drag in the attributes CustomerRef and Channel.
Press Apply and Close to save your changes.
Double-click on the pipe inv
Go to the Sort/Group section.
Press .
In the new grouping attribute form that pops up:
Select the attribute CustomerRef from the drop down list.
Tick the Group flag
Press Apply and Close.
Add the grouping attribute Channel in the same way.
Back in the main pipe configuration form, press Apply and Close.
Now you will complete the configuration of the merge table, using the _key internal variable to write key values into the table:
Double click on Channel List Reconciliation 2 to open the Properties.
Double click the attribute CustomerRef.
In the attribute details form that pops up, update Expression to: _key[1]
This writes the first key value into this attribute.
Press Apply and Close
Double click the attribute Channel
In the attribute details form that pops up, update Expression to: _key[2]
This writes the second key value into this attribute.
Press Apply and Close.
Add an attribute SalesCheck, and set the Expression to
if (countElements(sales) == 1,
"YES"
,
"NO"
)
3. Add an attribute InvCheck, and set the Expression to:
if (countElements(inv) == 1,
"YES"
,
"NO"
)
4. Press Apply and Close in the main table configuration form to save your changes.
5. Update the query in the SOURCE_ALL_CHANNELS_LIST database collector to:
select * from SOURCE_ALL_CHANNELS_LIST
order by CustomerRef, Channel
6. Toggle Enabled on the database collector
The ordering (order by) is needed to support the merge.
When merging directly from database tables – you have to repeat the ordering of data across the query and the pipe; that is, the ordering of data in the database collector query must match the grouping on the pipe from the database collector
6. Run Analysis on Channel List Reconciliation 2
7. In your results you should see an additional 3 records that were not included in the reconciliation you did in the previous exercise – channels that are recorded in the inventory, but not in the channels list, are included in your output.
This is because a merge will generate an output record for every key value it finds across all input pipes, whereas if you do a data enrichment using a lookup pipe – you will only get an output record for every record from the input pipe.
Filter unmatched rows
To help you find unmatched rows in your output data, you will now add a filter:
Open the recordset you have just generated in Channel List Reconciliation 2.
Create a filter:
Where ANY of the following are true
SalesCheckequals NO
InvCheck equals NO
Press Apply to apply the filter without saving.
You will get a list of all non-matched records, that is, all records where the SalesCheck value is NO or the InvCheck value is NO.