We are trying to migrate our requirements from ReqPro (I can hear you say...how come this late:) ) to DNG.  Project consists of a lot of requirements with two Artifact types. Let us call them A and B.  Each A links to one or more of Type B.  We have a total of 17K requirements of A  linked to 7K of type B.  It could as simple as one of A links to just one of B, but generally each A links to about 15 type B.  There are a few As that links to 400 - 500 Bs.  So far our research indicates that we cannot import requirements from ReqPro to DNG preserving the links(Trace To in ReqPro).  May be possible to just import all of A, but the traces to B will not import.  Here is our plan - Import all type Bs initially into DNG via csv export/import process from ReqPro.  Create one requirement of type A in DNG.  After this in DNG create one link (using Link To)from  A in to each  type B artifact that was just imported.  This would give us the complete URL for each  type B "Link To"s  .  Repeat this step for all of the 7K of type B.  Take a csv extract of this(all type B artifacts) from DNG.  That will have the URL for each of the 7K "Link To"s for B.   Take a csv extract of all of the requirements from ReqPro (containing all of type A linked to type B ) and use a program to change the link information column that came out of ReqPro with the URL information mapping .  This updated file would be used to import all of the ReqPro data into DNG.

As you can see the maximum time would be spent in manually creating the "Link To" for each type B in DNG. If we can find a way to not associate a URL for Link To, then we save all that time.  And we do not see a need for URL info in our project.  If we must associate a URL, is there a way to obtain the URL without having to establish a "test" link?

Based on a quick reading about Link Types in the Knowledge Center, it appears there is a way to create custom  Links, not sure if we could do them without associating a URL. We do not have administrator privileges, so have not checked that possibility yet.  All we need is link between two artifact types within the same CLM, no need for linking to external projects. <o:p> </o:p>

Any new ideas/insights would be greatly appreciated. <o:p> </o:p>

Thanks <o:p> </o:p>