Archi Forum

Archi => General Archi Discussion => Topic started by: cloudey88 on April 25, 2018, 14:45:31 PM

Title: Exporting Custom Properties
Post by: cloudey88 on April 25, 2018, 14:45:31 PM
Hello there. Relative newcomer here.

I am working as part of a team using various inter-operable tools with the bulk using Archi currently.

Within our Archi models, we have added custom properties to a subset of model element e.g. Adding a 'colour' property for which we populate with free text.

When exporting Archi models, there seems no way to export any extended properties and thus import these into other archi instances nor, importantly, other tools e.g. Bizz, Sparx. The XSD schemas developed upon exporting don't seem to reference any of the extended properties we're using.

Thanks for any suggestions!
Title: Re: Exporting Custom Properties
Post by: Phil Beauvoir on April 25, 2018, 14:55:38 PM
What do you mean by "custom properties"?

If you're using the ArchiMate Exchange File Format, all Archi properties are exported.
Title: Re: Exporting Custom Properties
Post by: cloudey88 on April 25, 2018, 15:08:32 PM
Hi Phil,

This isn't what I'm finding.

In Archi, we're creating a new property by clicking a blank cell then providing a new name. When using the 'Manage Property' function we can see that several elements (>100) are using this Property, with each element having different 'values'.

Perhaps this is a BizzDesign issue. the import appears to be fine with the exception of the missing properties. Do I need to modify the Metamodel e.g. add an attribute of the recipient model to accomodate the additional property?
Title: Re: Exporting Custom Properties
Post by: Phil Beauvoir on April 25, 2018, 15:12:40 PM
What's in the exported XML file? Can you see the properties?
Title: Re: Exporting Custom Properties
Post by: cloudey88 on April 25, 2018, 15:17:30 PM
Hmm...yes I can. They are clearly tagged to the correct objects also.
Title: Re: Exporting Custom Properties
Post by: Phil Beauvoir on April 25, 2018, 15:56:47 PM
So, I guess it must be the tool that imports that has the problem.