Note: To post to a thread, you must be logged in.
It would have been gr8 to have opportunity to import Fact Types examples (since they are just many times more numerous than all the rest of model)Off-topic: Are they forward engineered to ER source model?
I agree and really want that functionality myself.
Unfortunately, VEA's API does not expose the fact type examples and as such they cannot be imported nor exported. If that ever changes, you can be sure I'll adjust the toolbox accordingly.
No, the examples are not forward engineered (one of the reasons why I would like them to be exportable as you could then create the insert statements from that export).
Scot.
I have lost, due to my "experiences" with mixing stencils/notations, the Orthogonal Toolbox icon/add-in.So I want to ask, somewhat off-topic:Is it possible to use combination of XML export/import features both in VEA and in toolbox for more full round-trips between models?This is just newbie question (and due to the lack of exp and the need to quick-start practical use) on the better mode of tools use
Visio's XML import/export functionality is, I think, just shape related. From an ORM perspective, this is stuff like the page it is one, the X-Y coordinates, etc.
Much of the meta-data in the ORM model is not saved in the Visio XML. Further, I'm not sure you can import it and actually store the meta-data that is exported (mainly, object type names and predicate readings) into the VEA ORM engine. I suspect you would just get a "dumb" drawing.
If the toolbox were to support round-tripping, I'd likely include the (positional) data in Visio's XML in the toolbox XML as well and put it all in one place and with one import function. However, it isn't there yet.