Book a Demo

Author Topic: CSV Import Does not recognise MDG Technology  (Read 3031 times)

Eddie

  • EA Novice
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
CSV Import Does not recognise MDG Technology
« on: August 19, 2009, 12:06:01 pm »
Hi,
I've created my own set of UML profiles and deployed it through an MDG technology. It contains elements that have shapescripts, tagged values toolboxes, custom diagrams and so on.  It works a treat! :)

However...

I've tried to import (Using CSV format) a large amount of elements that have been stereotyped as an "Activity" that when made composite should create my own version of an activity diagram that contains the relevant elements in the tool box.  It only creates a standard Activity diagram though.  

The import recognises the Shape Script definition, but seems to ignore any other aspects of the element.  

The Activity Element works perfectly without using the import, but I'd rather not have to key in everything manually!

Has anyone else encountered this?  Is there some way that I can get around it?  I've tried the Sync Stereotype, but that's not working either....   :-/

Hope someone can help!

Cheers,

Eddie

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: CSV Import Does not recognise MDG Technology
« Reply #1 on: August 19, 2009, 08:51:14 pm »
Just a guess...

Try exporting some work you've done by hand (but using your MDG Technology). See if the stereotypes (or anything else) have their names prefixed with your Technology ID. Something like <myTech>::myStereotype.] If so, this might be something you need to tweak before you do the import.
No, you can't have it!

Eddie

  • EA Novice
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
Re: CSV Import Does not recognise MDG Technology
« Reply #2 on: August 20, 2009, 09:44:04 am »
Thanks Midnight.

I tried that, but still no good.  I thought I may be able to trick it by creating some of the elements manually, epoxt them, and the new ones and import them back into the model...  EA was too smart for its own good!   :)

I think I may have to just enter it in manually at this stage.  

I'll keep trying to sort it and let you kow if I manage to get around it.

Cheers!