Show Child and Parent Attribute in a Relationship



  • Avatar
    Jeremy Schofield

    There are a couple ways of doing it:

    1) Display rolenames in Entity Display Options

    In the model you'll see the rolenamed attribute followed by it's original name.

    2) View the Role Name in the Relationship Editor

    Double clicking on a relationship will display the Relationship Editor. If a migrated attribute has been rolenamed then you will see the Role Name here. 

    If a migrated attribute has NOT been rolenamed then the Role Name will be empty.

    Click on the Key Group dropdown list to reveal a "hidden" button that will display the key group members.

    HTH but I'm not convinced it will because the screenshot you provided seems to indicate there were no migrated attributes... Perhaps if you changed the display level to keys (under View menu) and took a screenshot of those entities we'd be able to see what the issue might be.

  • Avatar
    Paul Hernandez

    Hi Jeremy, thanks for the support.

    I changed the display level to keys as suggested:

    As it can be seen there is a relationship between VISITOR LOGON SYSTEM and ONLINE APPLICATION ACCESS. But the child attribute has another name (Online Application Visitor User Name). 

    I discovered using your first suggestion --> display rolename

    The weird thing is, when I open the relationship properties there is no migrated attribute:

    This is a model that we bought and it was created using erwin 9.6

    I am using erwin 9.7 and the model seems to be partially corrupted. What could be wrong?

    Many thanks in advance.




  • Avatar
    Jeremy Schofield

    One way to fix model corruption is to save the model in XML Min format and then opening up the resulting XML file.

    If that doesn't work there are a couple of other options you might try (on a backup copy of the model!!!) to locate the problem:

    1. Changing relationship R/02811 to a non-identifying relationship and then back to an identifying relationship.
    2. Moving Visitor Logon System User Name out of the PK of VISITOR LOGON SYSTEM and then back in.

    The problem with those two (2) options though is that it will change the order of the FK attributes in ONLINE APPLICATION ACCESS (+ child entites) not to mention what it does do your physical model (if you have one).


    Have you tried adding another relationship between VISITOR LOGON SYSTEM and ONLINE APPLICATION ACCESS to see if it properly shows the Migrated Attribute?


    You could also delete relationship R/02811 and add a new relationship between VISITOR LOGON SYSTEM and ONLINE APPLICATION ACCESS to see that it properly shows the Migrated Attribute.


    Let's start with that and see what you find!

  • Avatar
    Garry Gramm

    Great answer Jeremy.

    Just as a further suggestion should one of the suggestions other than the XML rebuild (which is the best first thing to attempt), where the action results in the column orders being messed up in the child entity "ONLINE APPLICATION ACCESS", and all its children affected,  you can use Complete compare to resync the column order and physical column orders to the database.


  • Avatar
    Paul Hernandez

    Hi everyone, 

    I tried to make changes in the relationships like Jeremy proposed, i.e. changing the relationship type, to see if the errors are fixed, but no luck.

    I verified also with the model provider, which uses an older erwin version (9.6) and it behaves exactly in the same way. As we bought the model, the development team of the model provider has to take care of it and give us an explanation/solution. I haven’t received any response yet but I will share any relevant information with you.

    Kind regards,


Please sign in to leave a comment.

Powered by Zendesk