mapping to package as target

Discussions about data interchange products Cameo DataHub and Magic RQ functionalities

Moderator: Moderators

mapping to package as target

Postby matzy812@bigpond.com » Mon Mar 20, 2017 2:37 am

I have a DOORS heading of type object heading which i have mapped to name. The heading does not contain an number just the heading name. I have a separate attribute in DOORS that is the heading number. The datahub tool allows me to choose prefix against this at the magic draw end. However, when i look at the details in magic draw i only see the name. Is there away to show the prefix. I know requirement attributes have a specific attribute for this, but packages do not,
Ideally i want to include the number in the heading to maintain the correct structure. When looking at the datahub explorer the headings have both number and name.

Any ideas?
matzy812@bigpond.com
Forum Newbie
Forum Newbie
 
Posts: 18
Posts Rating:1
Joined: Tue Mar 14, 2017 4:42 am

Re: mapping to package as target

Postby supatp » Mon Mar 20, 2017 11:12 pm

Dear Matzy812,

If you are importing objects to Requirements in MagicDraw, you may map the object number with the "Id" attribute. The containment tree should show the ID numbering in front of the requirement name.

Normally, with default MagicDraw option, the requirement will get the auto-numbered when they are created. So, before the import with your customize ID, you may need to turn the auto-numbering option off. You can click the menu Options> Project... Then choose the General section, and make the option "Use Element Auto-numbering" false.

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

Re: mapping to package as target

Postby matzy812@bigpond.com » Wed Mar 22, 2017 4:17 am

understand how this works for an item of type requirement, but i want to use packages for requirement headings - i can select object heading as name and object number as prefix for the package stereo type, but the prefix mapping doesnt appear to do anything ideally for headings i want to have a package stereotype prefixed by the object number followed by object heading.
matzy812@bigpond.com
Forum Newbie
Forum Newbie
 
Posts: 18
Posts Rating:1
Joined: Tue Mar 14, 2017 4:42 am

Re: mapping to package as target

Postby erik.bjur@sncorp.com » Wed Nov 16, 2022 10:45 am

I wanted to check to see if there was any resolution to this issue. In doors, the heading number and heading name are both combined. During import only the Heading name is brought over. There doesn't seem to be a way to combine the number and heading name into one column during the import. Any help would be greatly appreciated.
erik.bjur@sncorp.com
Forum Newbie
Forum Newbie
 
Posts: 1
Posts Rating:0
Joined: Wed Nov 16, 2022 10:06 am

Re: mapping to package as target

Postby ed.raynor » Mon Sep 18, 2023 7:11 pm

Use a validation script to sync them on the cameo side
ed.raynor
Forum Newbie
Forum Newbie
 
Posts: 1
Posts Rating:0
Joined: Mon Sep 18, 2023 6:59 pm


Return to Cameo DataHub, Magic RQ

Who is online

Users browsing this forum: No registered users and 0 guests