DHLink under another Parent Element

Discussions about data interchange products Cameo DataHub and Magic RQ functionalities

Moderator: Moderators

DHLink under another Parent Element

Postby carey.pedde@baesystems.com » Mon Aug 13, 2018 2:31 pm

When I used datahub to import DOORS req, I received an error "already got a DHLink under another parent element." Not sure why I am receiving this, but I am unable to sync this particular req to MagicDraw.
You do not have the required permissions to view the files attached to this post.
carey.pedde@baesystems.com
Forum Newbie
Forum Newbie
 
Posts: 4
Posts Rating:0
Joined: Thu Nov 30, 2017 3:19 pm

Re: DHLink under another Parent Element

Postby supatp » Mon Aug 13, 2018 11:35 pm

Hello Carey,

Basically, DataHub does not allow to import the same requirement twice into the same MagicDraw project.
Does the requirement that you tried to import already has an 's' on the icon?

Best Regards,
Supat P.
supatp
Customer Support
Customer Support
 
Posts: 165
Posts Rating:10
Joined: Mon Feb 08, 2010 2:45 am

Re: DHLink under another Parent Element

Postby carey.pedde@baesystems.com » Tue Aug 14, 2018 5:45 am

I was trying to add section 3.1.1.2 to MagicDraw when I receive the error. There is no 'S' icon on this section number.
carey.pedde@baesystems.com
Forum Newbie
Forum Newbie
 
Posts: 4
Posts Rating:0
Joined: Thu Nov 30, 2017 3:19 pm

Re: DHLink under another Parent Element

Postby carey.pedde@baesystems.com » Wed Aug 15, 2018 10:20 am

I tried starting over to see if I received the same error ... and I did. The reason I received the error is "conflict with the existing Class !" Is that something that anyone knows how to resolve?
You do not have the required permissions to view the files attached to this post.
carey.pedde@baesystems.com
Forum Newbie
Forum Newbie
 
Posts: 4
Posts Rating:0
Joined: Thu Nov 30, 2017 3:19 pm

Re: DHLink under another Parent Element

Postby carey.pedde@baesystems.com » Thu Aug 16, 2018 6:03 am

I figured out what was happening. In our DOORS Module we have a space in the object heading to that allows DOORS to show the numbering scheme for each requirement. The MagicDraw schema was pulling the object heading for the name and so would not allow the same name (i.e., a blank space) to be used more than once under its parent requirement. By changing MagicDraw schema to not pull the object heading into the name, I was able to sync the requirements.
carey.pedde@baesystems.com
Forum Newbie
Forum Newbie
 
Posts: 4
Posts Rating:0
Joined: Thu Nov 30, 2017 3:19 pm


Return to Cameo DataHub, Magic RQ

Who is online

Users browsing this forum: No registered users and 0 guests