Book a Demo

Author Topic: Imported elements are not "autonamed"  (Read 5362 times)

Wopke

  • EA Novice
  • *
  • Posts: 7
  • Karma: +0/-0
    • View Profile
Imported elements are not "autonamed"
« on: June 30, 2009, 11:13:20 pm »
Hi,

I have set up EA to use auto name counters for requirements and checked the Active box. When I create a new requirement in EA, it is autonamed. However, when I import requirements, they are not autonumbered. Is there some way of accomplishing this?

Cheers,

Wopke

Paul Lotz

  • EA User
  • **
  • Posts: 248
  • Karma: +1/-0
    • View Profile
Re: Imported elements are not "autonamed"
« Reply #1 on: July 02, 2009, 08:13:17 am »
From what source are you importing the requirements?

Wopke

  • EA Novice
  • *
  • Posts: 7
  • Karma: +0/-0
    • View Profile
Re: Imported elements are not "autonamed"
« Reply #2 on: July 02, 2009, 05:56:44 pm »
Hi Paul,

Thanks for your reply. I am importing from a CSV-file.

Regards,

Wopke

Paul Lotz

  • EA User
  • **
  • Posts: 248
  • Karma: +1/-0
    • View Profile
Re: Imported elements are not "autonamed"
« Reply #3 on: July 03, 2009, 02:59:28 am »
OK, well, I have only imported requirements from DOORS.  In that case, DOORS assigns a unique ID to each requirement, and I map that to an alias field in EA.

I see ("Requirements Management with Enterprise Architect" paper) that when one imports requirements from a CSV file EA can preserve existing requirements IDs in the source document and hence EA does not normally need to autonumber the requirements.  (There could be a way to change this.)

I'm not sure this helps at all or even if it's correct in your case, but it might help to think that we want to preserve the IDs in the source file, which in these cases is outside EA.

Paul