Importing glossary terms

[GTuckwell]

This is a question I have never quite got around to asking for months. Is there a way (a simple, non scripting way) to import a list of glossary items. CSV import is only for real project content, so I can't find a way to use that.

[qwerty]

You can use Import Reference Data. That on the other hand means you need to provide the XML format that EA wants.

q.

[GTuckwell]

Yes, I know a client who tried that! Its just text manipulation, but messing about in XML isn't for everyone.
This seems like an obvious (and easily filled) gap in the tool.

[Geert Bellekens]

You can use my Excel Importer to import glossary tools.

Geert

[Nabil]

MDG OFFICE is an alternate https://sparxsystems.com.au/products/mdg/int/office/office-integration.html it comes with ultimate license. You can avail a trial version
BR
Nabil

[David Rains (bioform)]

Having an issue in 4.2 but it might be something simple: I have an instance of an EA model open - assume this would be a precondition to import , open the Importer Spreadsheet, navigate to the Glossary Tab, then "Add-In" tab to find the "Import Glossary" button. Using the existing glossary terms that are predefined I press the button: "MS VBA; Compile error: Object Library feature not supported" popup in "addOrUpdateTerm" function, for myTerm (Set myTerm = getTermByName(name); MS Excel "Application-defined or object-defined error"

I looked under Developer/COM Add-Ins and noticed "Team Foundation Add-in" was selected and this is being loaded...

Is there something that is missing in my installation or am I just missing something obvious?

[Geert Bellekens]

David,

Probably one of the used references that is not available on your PC.
If you go to the VBA development environment (Alt-F11) and choose Tools | References you should see something like this:
https://imgur.com/gf3K0LS

Geert

[David Rains (bioform)]

Nope, have all of those references 1:1 match. Any other ideas? Should/Could I try an earlier version?
I verified that the importing of a class works... seems to be specific to EA.Term, throws error BEFORE getTermByName I believe... as the breakpoint does not go into that function...

Thanks... been fun looking at VBA code again

[qwerty]

Can't really help, but I'd break it down to single units and see to get them work one by one.

q.

[Geert Bellekens]

I just tried it again to be sure and the import works just fine here.

I'm a bit puzzled as to what could be the cause of the problem here.

I'm using EA version 14.1.1427, but that particular piece of code was written in 2013, so it must  be compatible with earlier versions of EA (version 10?)

Geert

[David Rains (bioform)]

Okay, sorry for the delay. I am running EA 13.1 due to work environment. Will swap my build to 14.1 and give it a try and post back to here. also will try install on my backup Win 10 HP vs. Dell and see how things work out there... Thanks Querty and Geert!

BTW having SO much fun at my new job - helping an gov. org implement MBSE using EA (don't ask why 13.1, but will be moving to 14 soon...) Right now I am working on moving them OFF DOORS 9.5 for ReqMan to EA...

Model On!

[Arshad]

Hi David

If you had MDG Integration for Microsoft office installed then you can directly import and also update glossary into EA from an excel spreadsheet.  It comes with ultimate license and you can avail a trial version here

To Import Glossary using MDG refer here .




HTH
Arshad

[Markus Gruendler]

@Geert: Excel importer is a simple but very useful tool, thank you.

- Markus

[Geert Bellekens]

@Geert: Excel importer is a simple but very useful tool, thank you.

- Markus

You're welcome

Geert