v15.2 - Missing Diagram Links - Package Import

[Paolo F Cantoni]

In a separate post (Quo Vadis Connector Proxies (ProxyConnector)?), I detail how we intend to handle the problem of Connector Proxies (t_object.Object_Type="ProxyConnector") during package transfers between repositories.

We've developed a working prototype as discussed therein.  The Connector Proxies seem to NOW be transported correctly.  However, we've discovered another anomaly.

In one of the diagrams, there are 75 arcs (most visible, some not).  In the imported version, there are only 72.  The diagram has the same number of vertices (51).

The missing arcs are NOT connected to any Connector Proxies.

Does anyone have any suggestions as to why these three (visible) arcs didn't get imported? They're present in the XML, I checked the transformed GUIDs.

TIA,
Paolo

[qwerty]

Project integrity (as usual)?

q.

[Paolo F Cantoni]

Project integrity (as usual)?

q.

No issues.  First thing I checked...

Paolo

[Paolo F Cantoni]

We created a Clone of the Diagram only package and tried some fairly extensive testing.  We learned a lot about how EA treats diagram vertices and arcs what are not in the transported package.

As far as we can tell, it is all working properly. We now think the problem is a form of user error.  Whenever you import more than one package with cross-links you need to import BOTH packages twice to ensure that any cross-links are not "dropped" due to reference timings ("Catch-22").  This has been our pattern in the past but may have been missed on this occasion.  Consequently, the 3 arcs were lost and therefore not available for the diagram in the target repository.

However, we did notice some differences between export/import of a package versus save/load of a Controlled Package. I'll address those in a separate thread.

Paolo