1
Automation Interface, Add-Ins and Tools / Re: Import native XML by automation and merge (update/insert)
« on: June 24, 2022, 03:38:40 pm »
> I think the key point is the "no deletes".
> When you import a package from xmi (or native xml) it will delete anything that isn't defined in the file.
I can't comment on xmi, no experience.
However native xml package import (not project import) will not touch elements unless the elements are in the imported scope in model (package subtree) or have a guid match within the import file.
The experiments indicate that some of the connectors crossing the import boundary are removed and some are preserved. Somewhere in the documentation there is a rule based on a connector ownership.
For no deletes, agree, there are always sql deletes for things linked with elements (e.g. tagged values are always deleted and reinserted). But the actual elements are updated with sql update statements.
I also recall something about object sequence going one up because of extra placeholder element temporarily inserted into the model.
> When you import a package from xmi (or native xml) it will delete anything that isn't defined in the file.
I can't comment on xmi, no experience.
However native xml package import (not project import) will not touch elements unless the elements are in the imported scope in model (package subtree) or have a guid match within the import file.
The experiments indicate that some of the connectors crossing the import boundary are removed and some are preserved. Somewhere in the documentation there is a rule based on a connector ownership.
For no deletes, agree, there are always sql deletes for things linked with elements (e.g. tagged values are always deleted and reinserted). But the actual elements are updated with sql update statements.
I also recall something about object sequence going one up because of extra placeholder element temporarily inserted into the model.