Feature Request

Entity Attribute / Fact Mapping

Corey Kaylor — 2006-10-02T15:49:59Z

At least from what I can see, there is no way to know which fact a particular column originates from. It would be very useful if this could be added. I am currently writing a transform that will attempt to generate MS_Description extended properties from the exported xml. This way there will be a description on each column and table in the database describing where it originated from in the conceptual model. In addition, some code generation utilites will read those descriptions and expose them as C# xml comments.

Custom Attributes?

chris — 2005-12-06T03:33:44Z

Any idea on when the custom properties might be included?

A shame on the open source, although I understand the hesitation. I just thought it might be a good way promote ORM and sites like this within the community.

Notes of objects

Scot — 2005-11-23T12:28:08Z

By "object" do you mean ORM Object Types? If so, their notes are exported as are the notes of all ORM constructs. The notes in ER models, however, are not exported. This is due to a lack of functionality in Visio's API itself; if they expose the notes I'll adjust the toolbox code to export them.

Kind Regards,
Scot.

to add info/warning messageboxes to XML export file creation/overwriting, resp.

g_vanine — 2005-06-11T16:42:45Z

I propose that "XML export" would give the warning message about succes of creating or warning message on overwriting existing file
(as well as possibility to remember previously used dir or redefining default one).

to add Error Log or Warning MessageBoxes?

Scot — 2005-06-07T00:52:05Z

What do you mean by "incorrect"? Object types can exist without fact types referring to them (yet).

The toolbox will look at a line with no predicate text and just create the object types <i>with no predicate</i>. In other words, it is impossible to even enter a fact type with no predicate text via the toolbox.

Scot.

previously used, default or VEA path

g_vanine — 2005-06-06T23:15:51Z

It would have been convenient to have possibility to:
- define default path for import
- that import remembered previously used path
- use the same path as VEA?
Now it always starts from "c.\". This is also different from VEA's working dir

Fact Types examples import with rules to ORM source model

g_vanine — 2005-06-03T21:21:08Z

Thanks a lot for the answer!
It would cost me a lot of time and employment to bump over it

Welcome

Scot — 2005-03-22T13:12:08Z

Welcome to the ObjectRoleModeling.com Orthogonal Toolbox Feature Request Discussion forum. Any (logged in) member of the site is welcome to post here. If your topic is related to a non-feature request topic for which there is a specific forum (e.g. ORM, Visio, Orthogonal Toolbox Support, General Discussion), please post in that forum instead.