Profile import behavior

Profile Import

Profiles can be standardized and applied to multiple projects, but individual projects can extend them. The profile import feature allows you to apply standard profile revisions at any time, even if you have extended profiles in individual projects.

import behavior

I will explain the behavior when I import profile P₂ into profile P₁ of the project I am editing.

• Profiles are updated to be the union of profiles P₁ and P₂.

  change operation	behavior
  Add with P2	Add as is
  Delete with P2	Keep contents of P1
  Changed by P2 (with differences)	Overwritten by contents of P2
  unchanged in P2 (no difference)	unchanged

• Identity of data in the profile is judged not by name but by internally managed ID.

• Not only the entities and view definitions defined in the metamodel, but also individual fields held by the entities are identified by internally managed IDs.

• Data moved between packages in the metamodel is also identified by internally managed IDs and moved according to the P₂ package structure.

• In case of duplication of additional data names, the name of P₁ is auto-corrected and the name of P₂ is kept.

• The order in the metamodel follows the order in P₂. The data of P₁ deleted by P₂ goes behind the data of P₂.