Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

Why are some requirements created with Import Factory being imported in the wrong hierarchy order?

Why are some requirements created with Import Factory being imported in the wrong hierarchy order?

Problem:

Why are some requirements created with Import Factory being imported in the wrong hierarchy order?

Resolution:

NOTE: Import Factory for CaliberRM is not an officially supported Borland utility. This article is provided to help guide you through a common problem observed with Import Factory.


Requirements created with Import Factory are being imported out of order. The requirements are defined in Excel as a .csv file and then converted into an importable text file by Import Factory. This text file is then imported into CaliberRM using RM Import.

One of the most common causes of requirements being imported out of order is due to a problem with the numbering scheme and sequence of the defined hierarchy. For example, Requirement number 48 is being inserted after requirement 18 and before 19. The following provides an example use case on how this would happen and what to look for to resolve this.


In the requirements.txt file, all of the requirements are in the correct order (numbers 1-50). However, the hierarchy on requirement 48 is incorrect.

Requirement #18 has a Hierarchy level of "1.6.1"
Requirement #19 has a Hierarchy level of "1.6.2"

.....

Requirement #47 has a Hierarchy level of "1.6.9.5"
Requirement #48 has a Hierarchy level of "1.6.1"
Requirement #49 has a Hierarchy level of "1.6.10.1"


As this example shows, Requirement 48 has the same hierarchy level as Requirement 18 (both 1.6.1), hence why it would be inserted out of order on the Import.


But looking a bit further into the hierarchy numbering sequence, it appears that Requirement 48 should actually be 1.6.10, not 1.6.1. By changing the 1 to a 10 for this requirement, it will be imported correctly with RMImport.

Additional Note: It is possible for this to occur with RM Export / RM Import if the requirements.txt file is modified. Borland does not support modifiying the requirements.txt file that is created with RM Export.

Old KB# 29967

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Version history
Revision #:
1 of 1
Last update:
‎2013-02-15 20:41
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.