Create interface with match source
After you select the main data object for your interface and click Create, you see the EDS Worksheet. The main Data Object you chose is at the left and the Taxonomy is at the right.
To add a match mashup to the current interface, click on the plus sign in the bottom of the screen, and select "Matched Source" from the dropdown.
This action will add two more steps before the Taxonomy Mapping: Matched Source and Source Designer.
Link the fields
In the Matching Source Tab, let's link the fields we want to match, by using drag-drop.
To easily find the fields you need start typing in the search box. The content of the grid will be filtered as you type.
Another useful option could be to use Mapped / Not mapped / Filtered tabs.
The keys are different for different mashups. For example, the key for the SMF mashup contains Security Alias, for Generic Entity it is Entity ID, and so on.
To remove the link for a field, delete corresponding expression from "Match With" column in the right grid.
Provide matching properties
To set matching parameters, expand the "properties" floating pane:
Matching key expressions are mandatory fields. They tell the application which records to compare.
In our example we will be comparing records which belong to the same entity_id and security_alias. Therefore Matching expression on both sides is |ENTITY_ID| + |SECURITY_ALIAS|
Autocomplete drop-down will list all the available variables as you start typing in the expression fields.
You may choose to include or exclude matched records from the resutl dataset by ticking corresponding checkbox.
Also you may provide the default tolerance for numeric fields In our case it is set to 0.02 = 2%
You can overwrite this default value by setting specific tolerances for each field in the "Tolerance Diff" column of the right trid.
The records in the result set, for which the difference is less than specified in the tolerance, will be treated as matched.
Please note, that the default name of the right data set is match_with. We are going to use it later, when we define filtering options for run time requests.
Mapping in Source Designer.
Source designer allows you to enrich your data with additional mashups, but for our example it is not necessary.
We are going to simply map all the fields to the Vocabulary
For that, use "Select All Rows" context menu and then drag them all at once to the destination grid.
Taxonomy Mapping
The taxonomy mapping will mostly be straightforward as well. We will just add one calculated fields to see actual absolute difference for the local market value.
The expression is abs(atof(|left_LOCAL_MARKET_VALUE|) - atof(|right_LOCAL_MARKET_VALUE|))
Notice, that atof() functions are necessary to convert the LOCAL_MARKET_VALUE to number representation before making any math operations with them. This is because by default all the values are assumed to be character strings.
Test run
In the Run Time Request (RTR) message we have to provide correct filtering options for left and right data sets.
For both sides we want to see values for same SN20 and same source - STARDIRECT, but we'll use different effective dates for the left and right sides.
Filtering parameters for right data set should be prefixed with data set name, which is match_with by default, while the parameters for left data set do not need any prefix.
After clicking Run button you can see the results:
M in the status fields means Match, and MIS means Mismatch