After you have loaded data into an entity and applied all of your compliance checks, you can copy this information, including business rules, to a new, dynamic entity.
If you plan to copy metadata from more than one entity that includes joins, you may get undesired results. As a best practice to avoid generating unnecessary joins, group the entities into a Baseline Analysis project and copy the metadata for the entire project.
|
Scenario |
Permanent Joins |
Entities in Repository |
Joins owned by Entities |
|---|---|---|---|
| 1. Assume that you have two entities named A and B and a permanent join on A and B. | A-B |
A B |
A owns A-B B owns A-B |
| 2. Next, assume that you copy metadata from entity A (including all permanent joins) to entity X and import data into X. |
A-B X-B |
A B X |
A owns A-B B owns A-B and X-B X owns X-B |
| 3. Next, assume that you copy metadata from entity B (including all permanent joins) to entity Z and import data into Z. |
A-B A-Z X-B X-Z |
A B X Z |
A owns A-B and A-Z B owns A-B and X-B X owns X-B and X-Z Z owns A-Z and X-Z |
To copy metadata to a new entity
-
Select Copy metadata to a new entity. Use the following table to decide which option to select:
Choose...
To Copy...
Self Joins
Only permanent self joins.
All Joins
All permanent joins.
No Join
No joins.
A new entity is created with the same name and a different reference number. The entity icon
indicates that this is a dynamic entity and does not contain data, only metadata.