Importing Nested Data Mapped to Multiple Repositories

Provide information regarding the join keys on the data source to determine the relationship while importing multiple repository and multiple data sources that have multilevel joins.

You can do this by creating a property file which has information about the joins on the staging tables.

Procedure

  1. Identify the relationship for which you need additional joins to determine the relationship.
  2. Next, identify the parent InputMap and get the ID from the database. Review the staging table with STG_<inputmapid>.
  3. These additional join keys should be part of both parent and child repositories and if they are not, create one. Make sure their Database Column names match.
  4. Ensure you map these attributes to the correct attributes in the data source, so that the join is correct.
  5. Create a folder COMMONDIR\<enterprise internal name>\inputmap
  6. Create 'import.prop' under the 'inputmap' folder which is created in the previous step.
  7. Edit the property file and provide additional join keys for all your inputmaps where additional joins are needed.
    • The properties file is a name value pair.
    • Name part - Syntax - JOINKEY_<CATALOG NAME>_<INPUTMAP 
    • <NAME>_<RELATIONSHIP NAME>
    • Value part - Database Column name from stg_inputmap table. Additional join keys (multiple columns can be specified separated by comma [','])

      For example:

      Repository Name - B

      Inputmap Name - BParentChild

      Relationship - B2C

      Additional keys - CDIVISIONID,CA 

      JOINKEY_B_BPARENTCHILD_B2C=CDIVISIONID,CA
      Note: The property name has to be specified in upper case.