Tagged values are not printed but contain n/a…

[Ben Bock]

Hello eaDocX Support,

I have a problem when printing tagged values of an own stereotype extended from class use case via an own MDG file.
I have defined 8 tagged values for this stereotype via the mentioned MDG file.
The first 6 tagged values are printed by eaDocX without any problem; however, the last two tagged values are not printed (i.e. only “n/a” is printed for them). I read in this forum that “n/a” is an indicator for an eaDocX-specific problem. That is why I contact you.

So, can you help me and tell me, how I can get the last two tagged values printed, too?
Or is there a constraint that only 6 tagged values can be printed at a maximum per object?
Additionally, the mentioned two tagged values are named “End Fifth Year” and “End Third Year”. Is it possible, that these names are the source of the Problem (e.g. due to the character map german y to english z…)?

Thank you in advance and best regards,

Ben

[eadocX Support]

Hi Ben,
When eaDocX prints ‘n/a’ it just means that it looked for a tagged-value (of the name you provided), but could not find one for that element.
This is common when using MDGs, where you might have elements of your new stereotype, but they have not been given all the correct new tagged values by EA.
I think the way to fix this is either:
– Gte EA to synch the tagged values – see http://www.sparxsystems.com/enterprise_architect_user_guide/10/extending_uml_models/synchronizetagsandconstrain.html
AND/OR
– when eaDocX tries to print a TV which does not exist, have it print something else (i.e. not ‘n/a’) – see eaDocX, Options and Settings, Application Settings, General, Default Strings, No tagged value present. I like to keep the string as non-blank, because it reminds me that my model does NOT contain the tagged values I expect, which is something I need to fix.

[Ben Bock]

Hello eaDocX Support,

thanks for your quick answer! Unfortunately, this does not solve my problem.
I have already synchronized the stereotype as you have mentioned.
Additionally, the mentioned tagged values – which are not printed by eaDocX – definitely exist in my EA model, because they are listed when I query “select * from t_objectproperties” via the EA search functionality.

Is there a possibility to view some kind of an eaDocX execution log, when eaDocX tries to generate the document? Perhaps I can get a hint from such an execution log to get to know, why eaDocX does not print the tagged values.

Additionally, my company has eaDocX version 3.2.3.0 installed (I can’t update, since the Person who has registered EA has left the company and was the only one who had the possibility do download new Versions…). Was there a bug in this version that can be responsible for that error and I just need to update (In that case it would be great if you could give us a contact Person on your side to solve the account issue)?

Thank you in advance again and best regards,

Ben

[eadocX Support]

eadocX just uses the TV list from the API, not direct from the DB, and, in the case of TVs, these can be different in some circumstances: there are lots of posts on the EA forums about this. If you have a specific issue, please get the latest eaDocX version, and try with that, then if it’s still strange, send an XMI and a little test document to support@eadocx.com and I will investigate further.
There is a Trace function with eaDocX, but, in the interest of speed, we don’t log everything. Enable the trace from the main menu, extensions, eaDocX, Help, or from the Application settings. Make sure to log ‘All’.
We will contact you separately about obtaining login credentials to get new versions.

[Author]

Posts