x

To add an Instance entity:

1. Expand Logical Model and double-click Instance Layer to open the modeling canvas.
2. Click Instance Entity in the upper left corner of the canvas and then click on the canvas.

   A new entity is added, as shown in the following image. Take note of the validation errors.

   

3. Double-click the new_entity window to open the dialog screen, provide the name and description for the entity, and then add some attributes (Columns) and check what types (SRC, STD, CIO, SCO, and EXP) should be pre-generated for cleansing in the MDM Hub.

   You must specify the GUI label for each attribute as it will be used in the application for data browsing (if the label is empty, the attribute name is used instead). For more information on linking your Reference Data definitions to attributes you want to check, see Adding Reference Data.

   

4. To match and master this entity, click the Matching tab and select the Enable Matching and Enable Identify Web Service check boxes for the entity, then create the matching columns on the entity, as shown in the following image.

   

5. Click the Advanced Settings tab to define the following:
   • Special Columns. Used to create a specific column into a specific MDM Hub layer (Create into column).

     Note: Special columns allow you to add technical columns (not necessarily part of the data model) and are not influenced by model importing (in case of continuous or multiple iterations).

   • Previous Distinct Values. Keeps a distinct list of all previous values of any source column. These values are persisted in the MDM Hub.

     For example, if cio_last_name was [Johnson, Johnson, White] in the last three processing events, then the column defined for keeping previous values (for example, prev_last_name) will contain [Johnson, White]. You can define any separator for the values.

   • Old Value Columns. Not persisted in MDM and contains values that are computed dynamically on batch load and can be used for further processing. For example, you can get a previous value of an attribute.

     In contrast to Previous Distinct Values, Old Value Columns keep only the last previous value. Using the example above, the available value will be Johnson.

   

6. Click OK to save your changes and close the dialog window.

x

To add a relationship between Instance entities:

1. Click Relationship in the upper left corner of the canvas, then click on one entity and drag the relationship to another entity, as shown in the following image.

   

   The relationship configuration window appears.

2. Provide the required fields, as shown in the following image.

   

   The Parent Role and Child Role are used as aliases in web services for model traversing (instead of using the relationship name and its reverse name).

   The Parent Table field indicates the independent entity in the relationship. The relationship arrow points from the dependent entity (Child Table) towards the independent.

   The Relationship Type drop-down list has Same System selected because it is defined within the same connected system. You can use this option to separate the same records (same source_id) from different systems, which usually pertains to most cases.

   The Foreign Keys section allows you to define the relationship (content assist is available).

3. Define the attributes you wish to copy from one entity to another (for example, for matching or mastering reasons) by opening the Copy Columns from Parent -> Child and Copy Columns from Child -> Parent tabs to set up columns (use tooltips by moving the mouse over the attributes). Always consider filtering out records that match a given condition in order to reduce copied data volume.

   The following image shows the Copy Columns from Parent -> Child tab.

   

   The following image shows the Copy Columns from Child -> Parent tab.