Book a Demo

Author Topic: Missing Cross References  (Read 3202 times)

Doug Blake

  • EA User
  • **
  • Posts: 102
  • Karma: +0/-0
    • View Profile
Missing Cross References
« on: May 04, 2012, 05:58:45 pm »
When I check my model into our version control system (TFS), I sometimes get a dialogue informing me that the latest revision of this controlled package contains the following cross package references which are missing from the XMI file I am currently exporting.

Then it lists some missing items, nearly always a connector or 2. This list is not specific, so I dont know what connector(s) the system thinks is missing.

What should I do here? My instinct is to say that I want to export what I currently have in the model so if there is a connector missing, I must have removed it on purpose, hence dont restore it(them) to the XMI. :-?

Is this connector in the TFS repository and not in the model or vice versa?

TIA DGB
Using 9.3.930/TFS/W7
DGB Using 12.0.1214 / eaDocX 3.6.2.1 / MSSQL / TFS / Windows 7 / IE11

ngong

  • EA User
  • **
  • Posts: 275
  • Karma: +2/-2
    • View Profile
Re: Missing Cross References
« Reply #1 on: August 01, 2018, 05:23:50 pm »
This is still true for EA14.
If you ignore those messages it is likely that you violate your model - silently. You may notice only after printout or so.
One cause is that "Get All Latest" - for any reason - is not able to satisfy all inter-package references of controlled packages in all cases. I have not found out yet, in what cases external references get lost. It is seldom the case, but if I got it, I did not find a way to repair the situation. (Checking "For all packages, create placeholders for external references" is mandatory but does not hinder missing references.)
To be on the safe site in professional projects producing production software you may consider not using EA integration of Version Control at all. Define your own - tested - XMI based process.
Rolf