Relation diagram in semantic layer

Would absolutely love to see this.  Would be useful from a developer standpoint, and even more useful from a documentation standpoint.  I've been looking for ways around not having this feature, and most of the available options have some substantial drawbacks. 

Yes, and I would be great to have in the product.

But drawing graphs quickly becomes quit complicated when applied to problems where things are not just a one way flow (Flow, Impact Analysis, Data lineage (1 or few) to 1 linked in a sequential order ) or 1-star diagram (1. level Relation).

Don't just take my word for it. Try looking at https://en.wikipedia.org/wiki/Graph_drawing. The Math geeks have been enjoying them self with this combinatorial problem for decads and found that the alogorims needs to optimize fluffy things like aesthetics and efficiency of convaying meaning.

We have been looking for good libaries to utillize for drawing the more complex models like a semantic model with more than one center piece. But they are just not there.

Then we have considered building our own editor but decided against it because that would go in the wrong direction of our core idea to automate.

In stead we would like to offer an export to other specialized tools that you guys are using - but we haven't seen a good format for export/import or a convergens to one/few good products that all of you are using. Most just resort to Power Point and drawing text boxes with connecting arrows.

So we are aware of the desire but just haven't found a good way to solve it for you yet.

Jan: what about Microsoft Visio? Maybe not "the best", maybe not "the most used", but at least part of the Microsoft stack. It used to have options to generate DB structure from diagrams iirc. I tend to use draw.io (free) these days, but I don't think it has the option to encapsulate meaning and metadata in the way Visio can.

Jan,
we really need some kind of relation diagram in the symantic model, and like Bas said, the same mechanism as for ODX, DSA and MDW would be sufficient to start with (and to show a 'normal' star-schema).  

Everything is better than maintaining documentation manually outside of TimeXtender.