Sparx Systems Forum
Enterprise Architect => General Board => Topic started by: Mauricio Moya (Arquesoft) on November 22, 2025, 01:01:30 am
-
I am working with a custom MDG Profile that includes a stereotype extending PackagingComponent (essentially a Package that visualizes/behaves as a Component).
Creating these elements manually via the Toolbox works perfectly. Other stereotypes in the same MDG (extending Class, Component, Node, etc.) also work fine both manually and via CSV import.
However, I am facing issues specifically when trying to import the PackagingComponent elements via CSV:
Attempt 1: If I define the Type column in the CSV as PackagingComponent (and the Stereotype column as MyProfile::MyStereotype), the import fails with errors.
Attempt 2: If I define the Type column as Package, the elements are imported, but they result in standard Packages (not PackagingComponents). Consequently, the Tagged Values appear in the standard "Tags" tab rather than being mapped to the element's general properties/fields as defined by the MDG.
Has anyone successfully imported elements extending PackagingComponent via CSV? Is there a specific string I should use for the "Type" column, or is this a known limitation?
-
Hi Mauricio,
The PackingComponent is one of those elements I have previously described in the forum as having a dual personality - i.e., it is an element but it also a package. It exists twice in the repositories.
With previous version of Sparx EA (v13 to v16), we tried using it as a component, or to be more specific as a way to model an Information System Service or a complex application. We gave up because of a combination of issues importing and exporting data and limitations on how this element is rendered by Sparx EA when used in diagrams.
-
Thank you very much! That worked fine ;)