Sparx Systems Forum

Enterprise Architect => Automation Interface, Add-Ins and Tools => Topic started by: BCGoitcwoodard on May 10, 2024, 04:33:23 am

Title: How does the EA repository represent a view column?
Post by: BCGoitcwoodard on May 10, 2024, 04:33:23 am
Trying to create a matrix mapping database view columns to database table columns.
How does the EA repository represent a view column?  What is the join condition for navigating from the view column to the parent view object? 

I see that I have created connectors from table columns to XSDElements, but I'm stuck trying to connect table columns to view columns.

Thank you,
CCW
Title: Re: How does the EA repository represent a view column?
Post by: Paolo F Cantoni on May 10, 2024, 10:36:52 am
Trying to create a matrix mapping database view columns to database table columns.
How does the EA repository represent a view column?  What is the join condition for navigating from the view column to the parent view object? 

I see that I have created connectors from table columns to XSDElements, but I'm stuck trying to connect table columns to view columns.

Thank you,
CCW
Have you considered using Dependencies between the tables and linking them to the Element Feature using the context menu option?  It is a bit cumbersome, but it works.

HTH,
Paolo
Title: Re: How does the EA repository represent a view column?
Post by: Sunshine on May 10, 2024, 10:52:05 am
To the best of my knowledge I don't think you can create a matrix down to attribute level. The approach I would have used to map tables and rows to other tables and rows has already been suggested by Paolo in previous post. That is using connectors such dependency or trace and linking them using the element feature at either end of the connector. It means a lot of connectors and it is a bit cumbersome.
Title: Re: How does the EA repository represent a view column?
Post by: Richard Freggi on May 10, 2024, 04:17:52 pm
If your EA model is generated by reverse engineering a database, the mapping is automatic only if the metadata is captured during the reverse engineering process.  Most databases don't provide this kind of metadata, so you would need to add it manually after reverse engineering.  I remember EA has a column to column dependency connector, I forget what it is but it can be done manually and you would need to write a custom query to generate the column to column dependency matrix.