Cross references missing

[cecD]

We are facing an issue due which is linked to the loss of cross references.

The context of our project is the following
     - EA (v12.0.1215 or v13.0.1305) is used for 1 UML project, with about 5 users at the same location.
     - Following the “best practices for version control” requirements:
     o   We have selected the configuration for  “centralized team”
     o   We have installed a DMBS (MySQL 5.1) on a dedicated windows server
     o   We use SVN for configuration management (with corporate SVN
repository and tortoiseSVN on client PC)

Actually, we lose of cross references when we perform the folowing actions :
     - The schemas are displayed correctly in EA.
     - We run a "Check Out Branch ..." on a package A.
     - After the check out branch, we run a "Check In Branch ..." on this pachage A without none modification.
     - During the "check in branch", several messages "Missing Cross-References" display
     - After this "check in branch", the schemas are always displayed correctly in EA.
     - We run a "Check Out" on the package A and in this case, the display of schemas is wrong (loss of cross references).

The package A is constituted of following way :
A package can mix classes and sub-packages and diagrams
Package A
    Package A.1
        Diagram A.1 : displays Classes from Packages A and B and relations between Classes
    Package A.2
        Diagram A.2: displays Classes from Packages A, B and C and relations between Classes
        ClassN
    Class1
    Class2
Package B
    ...
Package C
    ...

Could you explain us how to solve these problems ?

Thanks a lot for your support.

[Helmut Ortmann]

Hi,

as far as I know there are issues with lost references when using controlled packages. Mostly they are related to embedded elements. If you search the forum you should find some threads.

I usually select the options in Package Control Options:
- For all packages, create placeholders for external references.

I haven't used Controlled Packages in the last few years. Therefore the behavior may have changed.

If the issue still exists after changing the options consider filing an official bug report.

Kind regards,

Helmut

[cecD]

Hi Helmut,

In our project, the option "For all packages, create placeholders for external references" is indeed selected.
The problem is not related to this option.

Thanks for your response.
Francky