Page Comparison

Add a Matched 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 :

1. At the bottom of the

Image Removed

1. window, click Image Added Add Step Before, and then click Matched Source.
   Image Added
   This action adds two more steps before the Taxonomy Mapping: Matched Source and Source Designer. In the Matched Sources Step box, you see a message asking if you want to continue to enable the Matched Source.
2. Click Yes to continue. 
   You see the Match With Source grid on the right. And you see the options at the bottom of the window change to Matched Source > Source Designer > Taxaonomy Mapping, where Matched Source is underlined.

Link the

Fields

In the Matching Match With Source Tab, let's grid, you can now link the fields we you want to match , by using a drag-and-drop operation to drag a field from the main Data Object grid to a Match With Source grid field. 

To easily find the fields, you need can start typing the field name in the search box. The system filters the content of the grid will be filtered as you type.Another  Another useful option could be is to use the Mapped / Not mapped / , Not Mapped, and Filtered tabs.

Image Modified

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, in the right Match With Source grid, delete the corresponding expression from "the Match With " column in the right grid. 

Provide

To set matching parameters, expand the "properties" floating pane:

Image Removed

Matching Properties

Matching key expressions are mandatory fields. They tell the application which records to compare. 

In our example we will be this example, you are comparing records which belong to the same entity_id and security_alias. Therefore the Matching expression on both sides is |ENTITY_ID| + |SECURITY_ALIAS|Autocomplete drop-down will list all the available variables as .

To set matching parameters: 

1. At the right side of the window, click Properties to expand the Properties floating pane.
   Image Added
2. Specify the value for the Left Key Expression and the Right Key Expression.
   As you start typing in the expression fields, the autocomplete drop-down lists all the available variables.

1. In this example, the Matching expression on both sides is |ENTITY_ID| + |SECURITY_ALIAS|
2. In the Include Matches to Result check box, you can include matched records from the result dataset by selecting the corresponding check box.
   Otherwise, you can exclude matched records from the

1. result dataset by

1. clearing the corresponding

1. check box.

1. In the Common Float Tolerance box, you can provide the default tolerance for numeric fields

1. .
   In this example, it is set to 0.02 = 2%.
2. You can overwrite this default value by setting specific tolerances for each field in the

1. Tolerance Diff

1. column of the

1. Match With Source grid.
   The records in the result set, for which the difference is less than specified in the tolerance, will be treated as matched.

Please note, Note that the default name of the right data set is match_with. We You are going to use it later , when we you define filtering options for run time requests.

Map in Source Designer

The Source designer Designer mode allows you to enrich your data with additional mashups, but for our example it is not necessary. In this example, you simply map all the fields to the Vocabulary.

We are going to simply To map all the fields to the VocabularyFor that, use "Select All Rows" context menu and then drag them :

1. At the bottom of the window, click Source Designer.
   You see the CompositeSource base grid and the Vocabulary grid. 
2. In the CompositeSource base grid, right-click and then click Select All Rows.
3. Drag the fields all at once to the destination grid.

Map the Taxonomy

The taxonomy mapping will for this example is mostly be straightforward as well. We will You just add one calculated fields field to see actual absolute difference for the local market value.

The expression is absis:  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.Image Removed

Run a Test

In the Run Time Request (RTR) message we , you have to provide the correct filtering options for the left and right data sets.

For both sides we in this example, you want to see values for same SN20 and same source - STARDIRECT, but we'll use different effective but you use dfferent 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.

Image Added

In this screen you can switch to Raw RTR tab and see how Run Time Request message should look like.

You will need this information when you are ready to run the interface from outside of EDS GUI.

After clicking Run button you can see the results:

M in the status fields means Match, and MIS means Mismatch