![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Migration problems Topic Summary: Created On: 6-Jan-2005 07:05 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Hi Dave, One possibility for 1 is that your layout DXL may contain hard-coded references to the unique identifier of other module(s). After migration, if the unique identifier of a module has changed, any layout DXL referencing it will be broken. I haven't done a migration myself, but I would expect the unique identifiers to be maintained after migration. I have only encountered this problem when restoring a project archive with traceablility columns on a different DOORS database. To check if this is a problem, look for code like the following as the first line in your layout DXL: string limitModules[4] = {"00003202", "00003202", "00003202", "00003202"} Here, the layout DXL is filtering on the module with id 00003202. In the DOORS explorer, select the module that the layout DXL is meant to reference and run the following code in a DXL window (Tools->Edit DXL...) print uniqueID(getSelectedItem) If the identifier printed is different, the layout DXL will need to be edited to use the new identifier. However, I would contact Telelogic, as the unique IDs shouldn't change after migration. Cheers, Antonio. | |
![]() |
|
We have migrated a Doors 5.2 database to Dorrs 7.1 (via 6).
All the data and links appear OK however we have a couple of minor problems:- 1. any column that uses layout DXL to display link analysis data is now empty!!!. (The links are still there and can be followed by the navigation arrow!!) 2. One of our modules used carriage returns at the end of Object Tex to provide spacing in a printed version, these appear to have been removed. Does anyone know the cause of the problems, or better still any fixes? |
|
![]() |
|
![]() |
|
Hi Dave,
One possibility for 1 is that your layout DXL may contain hard-coded references to the unique identifier of other module(s). After migration, if the unique identifier of a module has changed, any layout DXL referencing it will be broken. I haven't done a migration myself, but I would expect the unique identifiers to be maintained after migration. I have only encountered this problem when restoring a project archive with traceablility columns on a different DOORS database. To check if this is a problem, look for code like the following as the first line in your layout DXL: string limitModules[4] = {"00003202", "00003202", "00003202", "00003202"} Here, the layout DXL is filtering on the module with id 00003202. In the DOORS explorer, select the module that the layout DXL is meant to reference and run the following code in a DXL window (Tools->Edit DXL...) print uniqueID(getSelectedItem) If the identifier printed is different, the layout DXL will need to be edited to use the new identifier. However, I would contact Telelogic, as the unique IDs shouldn't change after migration. Cheers, Antonio. |
|
![]() |
Telelogic DOORS
» Administration
»
Migration problems
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.