Sparx Systems Forum
Enterprise Architect => General Board => Topic started by: mse on March 27, 2024, 03:11:00 am
-
I would like to use CSV as an export medium but I had doubts on how relationships are exported. Suppose I want to export a series of classes that have relationships. It seems that I can only export standard EA properties or tagged values.
Suppose class A depends on class B and I have a dependency arrow drawn between them. I want to see this in the CSV export:
Name, GUID, dependency
A,{A8CB9E07-5A0E-4f7a-A9CE-3F2CE0BBB937}, B
C, {7BA75B87-E43F-49f9-8CC2-E51906CFB8A9}, D
Alternatively I have a profile where I have a tagged value to a RefGUID. This outputs the GUID but then I have no relationships in diagrams like dependency arrows.
-
Standard csv export only considers elements and not 2nd class connectors. You would need to write your own exporter. Though I doubt that csv would be a good idea in this case.
q.
-
I've extended the EA Excel Im-Exporter from Geert (https://bellekens.com/ea-excel-import-export/ (https://bellekens.com/ea-excel-import-export/)) to handle connectors.
Needs some more testing.
Send me a DM with your email and I'll send it to you.
-
It turns out since we are using Jama for requirements management, we might just be able to use Jama to link with the project in EA. That way I don't have to worry about GUIDs.
It seems that CSV imports and exports are best for initial work because there are no GUIDs in the beginning. The problem happens afterwards once GUIDs are assigned and I need to roundtrip things. I could store GUIDs in the jama database, but then I have add this information as an attribute in our project, and that is only just keep EA in the loop.
-
It might be true that CSV is only for first time use.
The EA Excel Im-Exporter from Geert however uses the GUID to identify elements.