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.
