Imported requirements not recognizing MDG tags

[SparxUser19]

Hello,

I have created a MDG technology to add custom tags to my requirements. MDG imports fine and works as expected.
The issue is when I import requirements using the CSV import option - the requirements import fine, but do not recognize the tags.

I tried the ‘synchronize tags’ option, but that didn’t seem to help.

Any one encountered this?

Thank you in advance!

[qwerty]

I'd guess that the import will not create requirements with your MDG's stereotype but plain requirements. I'm not using the csv import. Maybe you could adapt the csv import script in the EAScriptLib. There you can assign the right stereotype programmatically.

q.

[Glassboy]

Do you have the base type and your stereotype defined in the csv import/export?

[Paolo F Cantoni]

Do you have the base type and your stereotype defined in the csv import/export?

+1
Paolo

[Nizam]

After bulk import, even if i set the stereotype and type, i have to (at times) run a script to set the FQStereo into SterotypeEx for EA to pick that up.
Especially with Connectors, even Synchronize Stereotype isn't resolving it.

PS - to double check you've done the right thing in import, just remove the stereotype (Save) and reapply the same stereotype, if the tags are picked up then its to do with StereotypeEx not set

[Geert Bellekens]

I have used the CSV export in the exact same way (importing my tagged values added in an UML profile wit an MDG) and it worked fine for us.

I'm not sure what you are doing differently, but it at least you know it should be possible.

Geert

[SparxUser19]

Thank you all for your responses.

My MDG technology was extending the base class of Requirement. The custom stereotypes that I created were for Requirement Types as well. So when I would import the requirements, even though I had the type and such defined, the MDG technology was not enabled because the requirements had the custome stereotypes and were no longer associated with a base ‘Requirement’ - as some of you suggested.

Thank you again for your prompt input.