Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

ReqIF Import error DOORS 9.6 to RRM 4.0.4

We are trying to import several modules from a Rational DOORS V. 9.6 database to a V. 4.0.4 Jazz RRM. We first had success importing a single module with a custom view from DOORS, and further success importing an edited version of the same module.

However, we ran into trouble when we tried to import two or more modules in one ReqIF file. We could successfully import a dual-module ReqIF file provided that both modules were in Standard View. In further tests, there was varied success as we played around with ReqIF’s that contained, for example, data from custom views without the view itself or combinations of Standard and custom view modules. Some were successfully imported but with errors, others were not imported at all.

One ReqIF in particular contained two Modules with custom views, and prompted the following Summary after import:

                Successfully imported 5 of 5 Data Types

                Successfully imported 25 of 25 Attribute Definitions

                Successfully imported 4 of 4 Artifact Types

                Successfully imported 4 of 4 Folders

                Successfully imported 325 of 325 Artifacts

                Errors importing Modules

                Successfully imported 0 of 0 Views.

Under the “Artifacts” heading, about half of the artifacts had the following error:

                Error importing artifacts. 403 CRRRS8657E An invalid value was specified for the attribute definition URL https://server.net\rm\types\_IDinformation

EDIT 1/8/2015:
The issue seems to be caused by data, not view. Any ReqIF import that uses only Standard View data has been successful, but any custom view data causes the import to fail--even if the custom view itself is not imported.

1

0 votes



One answer

Permanent link
After removing a custom enumeration attribute from the Legacy DOORS database, we were able to successfully import all of the modules and link modules into RM with a single ReqIF file.

The custom enumeration attribute URI was set in a similar way to the other attributes that were successfully imported, so we still do not know why it caused the issue.

0 votes

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Jan 07 '15, 1:29 p.m.

Question was seen: 3,801 times

Last updated: Jan 30 '15, 2:00 p.m.

Confirmation Cancel Confirm