Sparx Systems Forum
Enterprise Architect => Automation Interface, Add-Ins and Tools => Topic started by: btheldad on March 03, 2020, 03:40:40 pm
-
Hello,
I am facing following issues while I am importing visio diagrams to Sparx EA
1. Class and Activity diagrams : Objects are getting imported but connectors are not. All the connectors are glued to objects.
2. Getting key not found error while importing Sequence diagrams
EA version : 15.0
MDG version : Sparx Systems MDG for Microsoft Visio 2.0.1.2
Visio version : Visio Professional 2013
Any help is welcome
-
Here are some things to try;
1) Raise a priority bug with Sparx Systems and provide example visio and resultant sparx model.
2) If you are trying to import into a SQL or Oracle DB then try creating a Sparx eap file and importing into that. If that works then export xmi and import into the SQL/Oracle DB model. I've had situations where relationships imported in ok into an Sparx eap file but not the SQL DB.
3) Save the visio to an older version of the file type and try import that.
4) Try the other older version 1.8.0 of the Visio importer which is available via download. Its a separate download and it looks like the version you are trying is part of the office package with MS Word and Excel.
5) If all that fails then try older version of Visio like 2010
Hope that helps and provides some food for thought.
-
My experience is that it's better to just forget about the import and remake the models manually.
It will save you a lot of headaches, and it will probably be faster in the end anyway.
After importing a visio model you'll probably still have a lot of work to fix the diagram layouts, correct syntax mistakes, merge re-used objects, ...
Geert
-
My experience is that it's better to just forget about the import and remake the models manually.
It will save you a lot of headaches, and it will probably be faster in the end anyway.
After importing a Visio model you'll probably still have a lot of work to fix the diagram layouts, correct syntax mistakes, merge re-used objects, ...
Geert
Our experience is slightly different from Geert's, but the end result is the same. When we import a Visio diagram, we do a lot of work in the back-end with direct SQL processing to "fix things up". If you're NOT prepared to do that then Geert's advice is correct, especially for a small diagram.
Paolo