Home › Forums › eaDocX queries › Project Glossary- eaDocX does not generate content
Home › Forums › eaDocX queries › Project Glossary- eaDocX does not generate content
- This topic has 16 replies, 3 voices, and was last updated 7 years, 2 months ago by eadocX Support.
-
AuthorPosts
-
17 January 2017 at 8:49 am #8698René van der LindenParticipant
Message ‘No element of type: Project Glossary in this repository.’
I am using EA v12.1.1230 Corporate Edition in combination with eaDocX v3.9.1.1 Corporate Edition.
Project Glossary is filled with multiple terms/types.
eaDocX document contains terms. Repository content contains terms.
eaDocX document has a Glossary Section inserted via the Insert menu-Project Glossary
Both Generate Full of Generate this section(draft only) do not lead to any content.Any hints 🙂 ?
17 January 2017 at 9:04 am #8699eadocX SupportParticipantDo you have a Profile for ‘Term’ in your document? If not, create one.
Also, how did you create the ‘Glossary’ section? Best way is to use the insert/glossary option, and that will do everything for you.
Also, don’t rename the Section called ‘Glossary’ – the name is a special one which eaDocX looks for when it comes to creating the glossary – any other name, and it won’t work.17 January 2017 at 9:23 am #8700René van der LindenParticipantProfile for Term is present (containing Term and Definition)
Glossary section was created by menu option insert, project glossary
I did not rename the sectionMore hints 🙂 ?
17 January 2017 at 10:23 am #8701eadocX SupportParticipantPlease can you send the Word document to support@eadocx.com, and I’ll take a look. Also the contents of your EA glossary (Export Reference Data / Project / Project Glossary).
28 August 2017 at 6:51 pm #8702Mike FlewellParticipantDid this issue ever get resolved? I’m having the same issue so if it has been resolved could you please post the resolution.
Thanks
29 August 2017 at 5:53 am #8703René van der LindenParticipantHi,
We gave eaDocX a sample of our repository and mentioned our EA, eDocX version. At their site this did work correctly. At our site we checked this issue with our other repositories and the problem did not occur there. The problem is not structural reproducible with EA, eaDocx in combination with PostgreSQL. What and who caused it, it is not determined.
Perhaps you can try this with the latest eaDocX version?Brgds René
29 August 2017 at 8:43 am #8704eadocX SupportParticipantI’ve just re-run the test cases for this, as well as creating some new ones, and it all seems to work for me, which is annoying.
What I did was:
(all done on PostgreSQL running under Windows 10)- Started the database and EA
- Connected EA to PG using ODBC. Using PGAdmin v1.22
- Don’t know which PG version I’m using – where to find this ?
- Found some Glossary entries in EA (EA v13)
- created a Quick Document from the test EA Package. This package just has some text in the description field, which uses some of the terms in the glossary
- Added a new ‘Glossary’ section to the new document
- re-generated – glossary looks ok
- Added new term to the glossary, and added the test o the description. Re-generated OK
Probably not a SQL error, because we use the Sparx API to fetch terms from the database.
29 August 2017 at 11:46 am #8705Mike FlewellParticipantThis doesn’t work. I am using both a SQL server database connected with ODBC and a non-SQL database using just the EA .ldb. Also tried multiple documents. Any other suggestions?
29 August 2017 at 12:51 pm #8706eadocX SupportParticipantIs there a Profile for ‘Term’ in your document ? If not, create one.
Please can you tell me the exact configuration you are running, and the step you are doing, so I can try to reproduce the issue.29 August 2017 at 1:51 pm #8707Mike FlewellParticipantYes there is a Profile for Term. The columns are in this order: Term, Term Type, Definition, and I even added in Name. As well I’ve tried multiple variations of the column order as well as deleted both Term Type and Name with just the Term and Definition as the columns but same issue.
The configuration is pretty standard with Sparx EA Ultimate 13.5.1351.
Repository is Local EAP file
Database version 7.0eaDocX Professional Edition Full Version 3.9.3.17
What else do you need?
29 August 2017 at 1:55 pm #8708eadocX SupportParticipantplease can you download the latest eaDocX version, and re-check that the issue is still there.
29 August 2017 at 4:20 pm #8709Mike FlewellParticipantI have downloaded and installed version 3.9.5.3 and I still have the same issue. Any other thoughts or suggestions?
29 August 2017 at 4:43 pm #8710eadocX SupportParticipantMysterious.
How did you add the Glossary?29 August 2017 at 4:52 pm #8711Mike FlewellParticipantIf you mean how did I add the Glossary to the document in eaDocX I selected Insert–>Project Glossary at the place in the document where I wanted it.
If you are referring to how I added terms to the EA Glossary I mostly did it through the Notes by selecting the context menu for the word(s) that I wanted to add as a term and then Create–>Glossary Definition.
29 August 2017 at 5:30 pm #8712eadocX SupportParticipantSo we’re using the same eaDocX version, adding the glossary in the same way, and both have a ‘Term’ profile. And both creating glossary entries in the same way.
So what’s different?
Is this a new .EAp file, or are there any restrictions on it due to EA security? -
AuthorPosts
- You must be logged in to reply to this topic.
Download a free trial
Download eaTeamWorks today for several free for life features, plus no obligation, 30-day trials of all the products: eaDocX, ea Revision Manager, eaSheets, Model Expert and PortfolioManager. Discover for yourself why we sell the world’s best-selling Enterprise Architect extension.
Download