Lost glossary when importing into repository?

[barikman]

Hi

I built a glossary for my project in version 14 of EA, which is installed on my personal laptop. My new team only uses version 13 of EA, installed on remote servers using a database repository. I copied the original project up to the team repository by the following process, IIRC:

• Converted the eapx project to an eap project by using "Save project as"
• Copied the project from the new eap file to the remote server containing the team's installation of EA, and performed a File to DBMS transfer

I now see that the Notes fields in the transferred project no longer contain valid hyperlinks to the appropriate definitions, and the glossary on the server repository does not contain my glossary definitions (although it does contain a small number of pre-existing definitions).

Does anyone know why this has happened, and perhaps more importantly, how I may rectify the problem? The project has not been maintained in the DBMS repository, so a re-import in some fashion is an available option.

Thanks,

Phil

[Geert Bellekens]

Phil,

With copy/paste you can get your glossary into a .csv format.
You can re-import those using my Excel importer: https://bellekens.com/product/simple-vba-excel-to-ea-importer/

Geert

[Modesto Vega]

Phil,

With copy/paste you can get your glossary into a .csv format.
You can re-import those using my Excel importer: https://bellekens.com/product/simple-vba-excel-to-ea-importer/

Geert

This would only work if Excel is installed side-by-side with Sparx EA and would not work if Excel is not installed side-by-side with Sparx EA.

[Geert Bellekens]

Phil,

With copy/paste you can get your glossary into a .csv format.
You can re-import those using my Excel importer: https://bellekens.com/product/simple-vba-excel-to-ea-importer/

Geert

This would only work if Excel is installed side-by-side with Sparx EA and would not work if Excel is not installed side-by-side with Sparx EA.

Yes, indeed.

Geert

[qwerty]

You could alternatively modify the VBA prototype for CSV import that comes with EAScriptingLib. Be aware that CSV has a RFC but Mickeysoft (and others as well) just don't read that and implement what they think it should be.

q.

[barikman]

Modesto is right, in that the servers that I use for remote desktop connection to our organisation's copies of EA do not have Excel (or any other MS Office product) installed.

So my thanks Geert, but I cannot use your suggestion directly.

Qwerty has suggested that I pick up sample code from the sample scripts provided with EA. I will look into that. Thank you for that suggestion.

Finally, to bring up the other point of my posting. How did this happen? Is it because of a bug in EA, or down to something that I did? I did mention that a small handful of glossary terms were already in place within the repository. Did they prevent the successful merging of the new terms into the repository? If so, I feel that I should declare that this is outcome is a bug. How do others feel abut this, please?

Regards,

Phil

[Geert Bellekens]

It is definitely a problem. A project transfer is supposed to copy the whole repository table by table.
The transfer log might give you some more info about what happened.

Geert