Hello experts need help with the below query from ADMM Perspective
Do we have the secondary source concept to directly link the other tables and can be used in mapping instead of creating Manual rules?
Hello experts need help with the below query from ADMM Perspective
Do we have the secondary source concept to directly link the other tables and can be used in mapping instead of creating Manual rules?
yes - the Primary Source table creates a set of Mapping Opportunities and relates to a specific Working table. When you drill down into the mappings you will notice that Copy rules will default to that Primary table as the source table, but you can change it to be a copy from a different table (I.e. secondary table) or from a completely different Datasource / Table. So you don't "register" a secondary source table directly, you just choose it as the Mapping Source for one or more fields.
Note that in Snapshot Management you should see that the secondary table now has a "Reference" to that table. The "References" column is useful to identify which snapshot tables are actually being used somewhere in the Migration Process, either as a Dataset Table, Primary Source, Secondary Source, Check Table, etc.
While on the topic, please also notice that when mapping a RULE you have the option to choose one or more tables which are related to the rule. While this doesn't really do anything from an automation standpoint - it will update the "References" in Snapshot Management and provide direct lineage between the Mapping rule and the one or more Sources and Tables that are referenced by the rule.
Please sign in to leave a comment.
Comments
1 comment