Book a Demo

Author Topic: Expected Behaviour of CSV Import  (Read 4358 times)

AndyJ

  • EA User
  • **
  • Posts: 337
  • Karma: +5/-3
  • It's only a model
    • View Profile
Expected Behaviour of CSV Import
« on: July 26, 2012, 10:01:26 am »
Hi people,

I'm not sure if I'm seeing a problem or not.

I've just imported a set of updated requirements into EA.
These requirements have GUID defined from EA.

What I'm seeing is that the requirements now appear in two locations in EA, the original package, and the "Import" package.

If I try to search for a requirement, only one of the locations is returned in the search.

The requirements contain the same information in both locations, but I'm worried that there may be consequences of having the same GUID in two different locations in the Project Browser.

Clearly search is not expecting this, and other parts of the tool may not.

Can anyone advise?

Andy
Sun Tzu: "If you sit by the river long enough, eventually the body of MS Visio floats past."

AndyJ

  • EA User
  • **
  • Posts: 337
  • Karma: +5/-3
  • It's only a model
    • View Profile
Re: Expected Behaviour of CSV Import
« Reply #1 on: July 26, 2012, 10:20:48 am »
Worse than I was expecting!

Deleting the requirement from either location in the project browser deletes the requirement from the model.
Sun Tzu: "If you sit by the river long enough, eventually the body of MS Visio floats past."

AndyJ

  • EA User
  • **
  • Posts: 337
  • Karma: +5/-3
  • It's only a model
    • View Profile
Re: Expected Behaviour of CSV Import
« Reply #2 on: July 26, 2012, 11:54:39 am »
Whoo Hoo! Spax to the rescue.

The browser was not updating correctly after the import.

Selecting (in the project browser) Contents, Reload Current Package, causes the requirements to jump out of their old packages, and reappear, updated, in the new import package.

Phew!

Andy
Sun Tzu: "If you sit by the river long enough, eventually the body of MS Visio floats past."