Sparx Systems Forum

Enterprise Architect => General Board => Topic started by: marku on October 20, 2018, 01:49:52 am

Title: Template- list Source & Target for Relations - only visible on the diagram
Post by: marku on October 20, 2018, 01:49:52 am

I have diagram with relations between some elements ( from different packages)
Usually I'm doing "deep copy" to generated document with full informations- which I want
But its too complicated.

In Document Templates-> Sections is:
Package
           -Diagram
                         Connector
In this section <connector> are "Source Columns" and "Target Columns". But when I try generate document - this pool ale empty (In document I see name, Notes , etc about relations, but not Source & Target)

Of Course - I can copy it from window "Relationships" - and paste to word document - but why can't do it in Template?

Title: Re: Template- list Source & Target for Relations - only visible on the diagram
Post by: marku on October 25, 2018, 12:27:10 am

Any Idea?: "How to build template witch Source & Target for relations?

Title: Re: Template- list Source & Target for Relations - only visible on the diagram
Post by: Geert Bellekens on October 25, 2018, 02:52:35 am

SourceColumns and TargetColumns is probably related to FK relations specifically, I'm not sure.

Anyway from the Diagram > Connector> you can't access the Source and Target Sections.
Only from Element > Connector>

Geert

Title: Re: Template- list Source & Target for Relations - only visible on the diagram
Post by: marku on October 31, 2018, 01:27:46 am

Geert - yes, it's only there
I'm thinking - Only I need this? :(

Title: Re: Template- list Source & Target for Relations - only visible on the diagram
Post by: Geert Bellekens on October 31, 2018, 06:30:49 am

No you are not the only one.

I usually use an SQL fragment for things like that.

Geert

Title: Re: Template- list Source & Target for Relations - only visible on the diagram
Post by: marku on November 07, 2018, 01:41:43 am

 >:(
If someone want easy do it in Sparx - better way is do it in SQL
So, for what use by  SPARX? ;)
Thanks for answer