Products

Home Forums Neil Burt

Forum Replies Created

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • in reply to: Related Element Tagged Values Return error #8746
    Neil Burt
    Participant

    so in your example, “look for a TV of the right name” in the looking bit it doesn’t give you the TVs of the target element, only the source ( TVs being different in each stereotype)
    I’ve worked around the issue by using a non profiled element, with no TVs itself, linked to a profiled stereotype and I can return the TVs I need.
    To resolve TVs for non-profiled element, I’ve inherited from a class. Bit of a faf and relies on me on ever needing non-profile to profiles relationships.

    in reply to: Related Element Tagged Values Return error #8744
    Neil Burt
    Participant

    Hmmmm,

    I’ve stripped back the fancy TV’s and still get the problem.

    The TVs can be returned on the profiled stereotypes themselves, so they can be “read”, but they cant be accessed over a relationship link, if the relationship contains profile stereotyped at both ends.

    If a non-profiled stereotype is linked to a profiled stereotype I can get the TV’s I need, so that doesn’t suggest its the TV’s themselves does it?

    in reply to: Related Element Tagged Values Return error #8742
    Neil Burt
    Participant

    hopefully you have them now

    in reply to: Related Element Tagged Values Return error #8740
    Neil Burt
    Participant

    Hi,

    Played around a bit and have a clearer view of what’s not working.
    Have attached a dummy project and test profile.
    Essentially I need the tag value of equipments located in (dependent link) in compartments.
    Both compartment and equipment are profiled.
    In EADocx I set up the compartment stereotype to show a dependent equipment tag, but only get the tag value range from the source ( ie compartment)as options.

    However, if I use a non-profiled class element as a pseudo compartment, and try the same I get the intended equipment tags as options.

    So the hiccup seems to be profile stereotype to profile stereotype.

    Any help appreciated.

    in reply to: Related Element Tagged Values Return error #8739
    Neil Burt
    Participant

    Morning,

    Nothing! and as I said I have had this working (and multi-hops)in another model.

    Just loaded latest ea build as well.

    Tried on a similar element, and again the TV options I get in “specify what to print” are those for the source equipment not target.

    As I mentioned the only difference with this model and the last ( working one) was use of set tagged values in the UML profile for the stereotypes ( set up using attributes for enum values)
    These TV can be recalled by EAdocx in a table on the stereotype.

    in reply to: Project Glossary – no element of type found #8653
    Neil Burt
    Participant

    Term is in the profile, used insert/project glossary option.
    will update version, although process isn’t quick here.

Viewing 6 posts - 1 through 6 (of 6 total)

Compare licence prices

Choose the licence that’s right for you and your team

Prices

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