Profile Import Behavior
Profile Import
You can standardize a profile and apply it to multiple projects, but also extend the profile in individual projects. The profile import feature allows you to apply revisions to a standard profile at any time, even if you extend the profile in individual projects.
Import Behavior
This explains the behavior when you import profile P2 into profile P1 of the project you are editing.
- The profile is updated to be the logical OR of profiles P1 and P2.
| Change operation | Behavior |
|---|---|
| Add in P2 | Add as is |
| Delete in P2 | Keep the contents of P1 |
| Change in P2 (with differences) (*1) | Overwrite with the contents of P2 |
| Unchanged in P2 (without differences) | Do not change |
*1 This also applies to the case where there is no change in P2 and P1 is changed.
- The identity of data in a profile is determined by the internally managed ID, not the name, and if it is identical, the presence or absence of changes is determined by the difference in the content.
- The identity of not only the entities and view definitions defined in the metamodel, but also the individual fields held by the entities is determined by the internally managed ID.
- Data moved between packages in the metamodel is also identified by the internally managed ID, and is moved according to the package configuration of P2.
- If the names of added data are duplicated, the name in P1 is automatically corrected and the name in P2 is maintained.
- The order in the metamodel follows the order in P2. Data from P1 deleted in P2 is moved behind the data in P2.